Reproducing Cityscapes results

Thanks for providing the code for Panoptic FCN, I think it’s a very interesting method!
As this repo only provides the training/evaluation code for COCO, I adapted the code to work for Cityscapes. In this fork, I added a data pipeline for Cityscapes, changed the configs as mentioned in the CVPR paper, and made some other minor necessary changes in the code.
However, when I run with the mentioned config, I cannot reproduce the results on Cityscapes as reported in the paper. Especially for the things classes, the difference is quite large. Specifically, this is the difference in performance:

Method
Backbone
PQ
PQ_th
PQ_st

Panoptic FCN (reported in paper)
R-50
59.6
52.1
65.1

Panoptic FCN (reproduced in our fork)
R-50
58.1
49.3
64.6

To be more specific, the following changes are made to the config yaml:
MODEL:
  LOSS_WEIGHT:
    SEGMENT: 4.0
  POSITION_HEAD:
    THING:
      NUM_CLASSES: 8
    STUFF:
      NUM_CLASSES: 12
      WITH_THING: True
  SEM_SEG_HEAD:
    NUM_CLASSES: 12
  KERNEL_HEAD:
    INSTANCE_SCALES: ((1, 128), (64, 256), (128, 512), (256, 1024), (512, 2048),)
  TENSOR_DIM: 150  # Adapted because max inst. per img > 100

SOLVER:
  BASE_LR: 0.02
  IMS_PER_BATCH: 32
  MAX_ITER: 65000

INPUT:
  MIN_SIZE_TRAIN: (512, 2048)
  MIN_SIZE_TRAIN_SAMPLING: "range"
  MIN_SIZE_TEST: 1024
  MAX_SIZE_TRAIN: 4096
  MAX_SIZE_TEST: 2048
  CROP:
    ENABLED: True
    TYPE: "absolute"
    SIZE: (512, 1024)

Is there something that I am missing? Are there further changes that need to be made to the code/config to be able to reproduce the Cityscapes result?
In issue #20 I read that you mention that the SEM_SEG_HEAD should be trained on all 19 classes instead of just the 12 classes (11 stuff + 1 for all things). Is this how you train it to produce the results you report in the paper? Did you notice a difference in performance for both versions?
Looking forward to your response. Thanks!

Hi, thanks for your interest in our work! The differences with your config are given below. Most of them are adjusted according to the data properties in the cityscapes dataset. And we use 19 classes for stuff training, which would bring some performance gain.
MODEL:
  POSITION_HEAD:
    THING:
      NUM_CLASSES: 19
      THRES: 0.01
      TOP_NUM: 200
    STUFF:
      THRES: 0.1
  INFERENCE:
    INST_THRES=0.5
    SIMILAR_THRES=0.97
    COMBINE:
       STUFF_AREA_LIMIT=2048

INPUT:
  MIN_SIZE_TRAIN: (512, 768, 1024, 1152, 1216, 1344, 1408, 1536, 1664, 1728, 1856, 1920, 2048)
  MIN_SIZE_TRAIN_SAMPLING: "choice"
  MIN_SIZE_TEST: 1024
  MAX_SIZE_TRAIN: 4096
  MAX_SIZE_TEST: 2048
  CROP:
    ENABLED: True
    TYPE: "with_instance" # implemented by ourself to ensure some instances in the crops
    SIZE: (512, 1024)

Maybe you can try this for the result. Hope this could help you.

@DdeGeus Have you reproduced the results?

Thanks for the quick response, and for providing the more detailed hyperparameters! I will apply the changes and check the performance.
@ShihuaHuang95 I will train the network in the next days and report the results here.

@DdeGeus Look forward to it!

I applied the changes to the config as you indicated, except for the with_instance crop type. The performance improved, but I'm still not able to reproduce the results as reported in the paper. The things PQ has increased signficantly, but the stuff PQ has decreased.
More specifically:

Method
Backbone
PQ
PQ_th
PQ_st

Panoptic FCN (reported in paper)
R-50
59.6
52.1
65.1

Panoptic FCN (reproduced v1)
R-50
58.1
49.3
64.6

Panoptic FCN (reproduced new)
R-50
58.8
51.5
64.1

Could you think of a reason why this is the case? I guess the things PQ could be improved slightly if I implement the with_instance crop data augmentation, but I suppose this will not impact the performance on stuff classes.
In an attempt to find the potential issue, I visualize the predictions. Below I show an example with a typical result, and the corresponding GT (image is frankfurt_000000_015676). In the prediction, the boundaries of individual things instances are shown in white. Especially for things classes, the network often groups objects that are close to each other, and belong to the same class (on the right side). Additionally, it sometimes predicts weird mask shapes (see object near the center). For stuff, I cannot find such clear trends.
Do you have an idea how to improve the performance so that the PQ matches the reported scores? If it helps, the most recent code is in this fork.

Hi, the only difference I can find is the gradient value, which is set to 15.0 in my own config. Actually, the segmentation result in Cityscapes dataset could be unstable, that's why we use COCO for ablation study. Whatever, I'll try to train your repo on my machine and reply if have the result.

Okay that is good to know. Thanks for trying to train my repo! In the meantime, I will try to implement the "with_instance" cropping method, set the gradient clipping value to 15.0, and try some more runs.

Hi, I have tried your repo with gradient clipping value 15.0. And the result is reported below. As presented in the table, PQ_st is close to the reported result. And the PQ_th could be attributed to the lack of instance annotation (different crop manner).

PQ
SQ
RQ
#categories

All
59.233
79.738
73.089
19

Things
51.550
78.339
65.546
8

Stuff
64.820
80.755
78.574
11

Over the past weeks, I tried various configs, and I also implemented the "with_instance" cropping method. However, I could still not achieve the reported performance, especially for things. I did manage to boost the stuff performance, by doubling the learning rate and using a batch size of 16. However, this hurt the performance on things classes.
The results:

Method
Backbone
PQ
PQ_th
PQ_st

Panoptic FCN (reported in paper)
R-50
59.6
52.1
65.1

Panoptic FCN (with orig config)
R-50
59.0
51.3
64.6

Panoptic FCN (130k steps, batch size 16)
R-50
59.4
50.9
65.5

As you can see, when compared with the previous best result I got (51.5 PQ for things), the cropping method has not resulted in a better performance. Currently, I have implemented it as follows: a crop should contain at least 1 pixel of a things instance. I also tried different thresholds (100 or 1000), but this did not give better results. Is this also how you implement this, or is it different? And would it perhaps be possible to share your code for this cropping method?
I also noticed that, like you mentioned, the performance on Cityscapes is very unstable. I haven't found a solution for this yet. Have you tried lower learning rates/longer warmup/better normalization or other methods to fix this?

Hi, thanks for your effort! I'll try to convert the "with_instance" cropping method to Detectron2 and give the response in several days. And I'll also try to reproduce the reported result in Detectron2 with the modified config.

Hi, I have implement with_instance to Detectron2 as given in the attachment. However, I found that the performance on Detectron2 is 59.4 PQ [model] [metrics] (CLIP_VALUE=5.0). I'm not sure if it is the reason for the difference in the platform. Whatever, I'll change the performance with R50 to 59.4 PQ in the revision.
# please add and declare this function to detectron2/data/transforms/augmentation_impl.py
# use this augmentation in your own dataset_mapper
class RandomCropWithInstance(RandomCrop):
    """
    Make sure the cropping region contains the center of a random instance from annotations.
    """
    def get_transform(self, image, boxes=None):
        # boxes: list of boxes with mode BoxMode.XYXY_ABS
        h, w = image.shape[:2]
        croph, cropw = self.get_crop_size((h, w))

        assert h >= croph and w >= cropw, "Shape computation in {} has bugs.".format(self)
        offset_range_h = max(h - croph, 0)
        offset_range_w = max(w - cropw, 0)
        # Make sure there is always at least one instance in the image
        assert boxes is not None, "Can not get annotations infos."
        if len(boxes) == 0:
            h0 = np.random.randint(h - croph + 1)
            w0 = np.random.randint(w - cropw + 1)
        else:
            rand_idx = np.random.randint(0, high=len(boxes))
            bbox = torch.tensor(boxes[rand_idx])
            center_xy = (bbox[:2] + bbox[2:]) / 2.0
            offset_range_h_min = max(center_xy[1] - croph, 0)
            offset_range_w_min = max(center_xy[0] - cropw, 0)
            offset_range_h_max = max(min(offset_range_h, center_xy[1] - 1), offset_range_h_min)
            offset_range_w_max = max(min(offset_range_w, center_xy[0] - 1), offset_range_w_min)

            h0 = np.random.randint(offset_range_h_min, offset_range_h_max + 1)
            w0 = np.random.randint(offset_range_w_min, offset_range_w_max + 1)
        return CropTransform(w0, h0, cropw, croph)

HI @DdeGeus , thank you for the Cityscapes fork you have done. I have trained Panoptic FCN using your work here. I tried to use the demo.py from detectron2 to infer the results on new images but I got the following errors described here. Can you tell me please what should I change to be able to use the demo.py from detectron2 for your work?  I saw that in this thread you already uploaded images on which the inference process was run.


Handle reorg

Detect and handle chain reorganization.  This requires disconnect block handling.

would be useful to show data such as the orphan rate. (and, partially related, time elapsed between blocks)

Closed by https://github.com/dcrdata/dcrdata/pull/43, and https://github.com/dcrdata/dcrdata/pull/44


Limit str. length of optuna user attributes

see here https://github.com/optuna/optuna/blob/a88dd6da90900cdf15c3f3de79f30e394fae2b74/optuna/storages/_rdb/alembic/versions/v1.3.0.a.py#L25

fixed with https://github.com/PhilipMay/mltb/commit/bd505c25a4051fabc6974d4743783a44e1d13748


Blockchain category

Hello!
Can you add chat for Blockchain Developers to your list?
https://t.me/dev_hyperledger

Of course, send a PR and I will merge it.


US SD Brule

Closes: https://github.com/openaddresses/openaddresses/issues/4347

# us-sd-brule-1546442188388.geojson.gz
ok - 10110/23779 (42.5%) valid addresses
ok - 0 outside of boundary (dropped)
ok - 13643 have an unsupported number format
ok - 0 are missing street names
ok - 0 could not be parsed
ok - 26 suffered misc failures


N position in Pam filter

I think N for now is ok, we can keep brainstorming about the others but not a main priority. thanks!


Move header and reset button to sidebar

Short description:

Current state:

Can't see reset button due to size
Header takes up room

Desired state:

Reset button visible, closer to top or within the sidebar
move header items to sidebar

Tasks:

[ ] Move reset button to sidebar, rename [reset zoom]
[ ] Move header logo / link to source to sidebar

Possibly remove some of the white space above the version as well.

Implemented in #241 .   We moved the logo to the top of the sidebar, the source code link to the bottom right of the footer, and removed the header.


Latest keybase_amd64 on Ubuntu 16.04 fails run_keybase

Hello!
It looks like keybase_2.11.0-20181121142914.6c100090f3_amd64.deb has a regression where run_keybase fails to complete on ubuntu 16.04. The error I get is:
▶ ERROR dial unix /run/user/1000/keybase/keybased.sock: connect: no such file or directory

Downgrading to keybase_2.10.0-20181112152732.f71edc2808_amd64.deb worked.

@yorinasub17 Sorry about that, could you try installing the latest version?

Thanks @heronhaye and @strib ! I have tried the latest version and it worked. Thanks for the quick turnaround!


CLIF log fix and calculation optimization

Approved without comments on commits.
Are we going to optimize the calculation?


get_account_transactions looping infinitely over the same transaction

Hi @tducret ,
First of all, thanks for the great library! :-)
I was using your library to load historical transactions from last 2 years, when I noticed that get_account_transactions is getting stuck in a specific case.
In my example:

first run of the loop

from 2019-03-01 to 2019-03-15, returned 47 transactions
algorithm takes startedDate from the oldest transactions and sets it as a new to parameter

second run of the loop

from 2019-03-01 to 2019-03-01 09:29:38, returned 1 transaction - the same transaction which was present in first run
algorithm takes startedDate from the oldest transactions - which is the same as before

step #2 is repeated endlessly

I worked around it by manually subtracting 1 second from the timestamp, as below.
    def get_account_transactions(self, from_date=None, to_date=None):
        """Get the account transactions."""
        raw_transactions = []
        params = {}
        if to_date:
            params['to'] = int(to_date.timestamp()) * 1000
        if from_date:
            params['from'] = int(from_date.timestamp()) * 1000

        while True:
            ret = self.client._get(_URL_GET_TRANSACTIONS_LAST, params=params)
            ret_transactions = ret.json()
            if not ret_transactions:
                break
            params['to'] = ret_transactions[-1]['startedDate']-1000 # fixed, because this loop was endlessly fetching the same transaction
            raw_transactions.extend(ret_transactions)

        return AccountTransactions(raw_transactions)

I'm not sure if it is possible to have more than one transaction with the same startedDate, but if yes, then this is not a proper solution.
Did you encounter case like that with your account?
Regards,

Hey, @dequire. This is a valid point. Please see https://github.com/tducret/revolut-python/issues/34#issuecomment-756612503. PRs are welcomed

Hey, @dequire. This is a valid point. Please see https://github.com/tducret/revolut-python/issues/34#issuecomment-756612503. PRs are welcomed


feat: add query endpoints for balances of specific runes

fixes: #3667
The logic will fetch balances of specific rune in each outpoint. Not loading the whole balances map.
Logic

add endpoint "/rune/:rune/balances" which allows specifying rune to fetch balances
add rune_specific_balances() to Server
add get_rune_specific_balances() to Index: use OUTPOINT_TO_RUNE_BALANCES, and then filter specific rune balances

Testing

get_rune_specific_balances(): querying balances from specific rune 0, 1, 2

@raphjaph hi, this is my first PR, I hope to explore more into the codebase. Any constructive feedbacks are welcome!

@casey Hi, can you check if this one satisfies your requirement enough?
https://github.com/ordinals/ord/pull/3069#issuecomment-1925038948

This PR has a good form, you have a good description and also added a test. Unfortunately we need another table to make this an efficient call. You can try your hand at this, or, if you want, I could show how to add another table into the database in the next Ordinals Coding Club. Let me know what you prefer :)

I can try adding it to table, thanks for your feedback

@raphjaph I have added a new table: RUNE_ID_TO_OUTPOINTS_BALANCE which tracks rune id to bytes array of (outpoints, balance)
Logic

Add table RUNE_ID_TO_OUTPOINTS_BALANCE update in index/rune_updater.rs
Add encode, decode scheme for bytes array of (outpoints, balance)
Update get_rune_specific_balances(): get exactly a map of (outpoints, balance) from rune id

Test

test_encode_decode_rune_to_outpoints_balance()
past test get_rune_specific_balances() works as intended

Runes can be in multiple outpoints so this the table should be a multi map. Also we already have the table OUTPOINT_TO_RUNE_BALANCES so we don't have to store the balance inside the new table.

The query needs a mapping from a rune id to a byte array of multiple n outpoints.
OUTPOINT_TO_RUNE_BALANCES maps an outpoint to a byte array of multiple m (rune, balances) so I would still have to go through the whole byte array to extract the balance of that specific rune, thus O(n*m)
So, I think why not also include balance of such specific rune in each out point (out point, balance of specific rune) as well, one less iteration. Thus, RUNE_ID_TO_OUTPOINTS_BALANCE, the cost of querying is greatly reduced to O(n)

@raphjaph can you check this one again,cargo test are passing on my local mac

@nghuyenthevinh2000 Have you run an index with this and compared it to the size without this table? This might be a big table and take longer to index so I'm inclined to put it behind a flag like --index-rune-utxos or --index-rune-balances.
Also what is the reason to make a the table RUNE_ID_TO_OUTPOINTS_BALANCE instead of just doing RUNE_ID_TO_OUTPOINTS and then get the balance from the OUTPOINT_TO_RUNE_BALANCES table? I think this could save you some decoding logic and database size.


Muesli recipe

Hello here is my pull request for my muesli recipe

Thanks @miriamrabels, looks great! Ready to merge! 🚀

@allcontributors please add @miriamrabels  for bug, content, code


bugfix: 服务实例包含IP情况下表达式匹配错误的问题(#14)

Codecov Report

Merging #15 (dd92e20) into master (a36a02d) will increase coverage by 0.11%.
The diff coverage is 97.82%.

@@            Coverage Diff             @@
##           master      #15      +/-   ##
==========================================
+ Coverage   53.07%   53.19%   +0.11%
==========================================
  Files         177      177
  Lines        8656     8682      +26
==========================================
+ Hits         4594     4618      +24
- Misses       4062     4064       +2

Impacted Files
Coverage Δ

apps/gsekit/cmdb/views/cmdb.py
96.61% <ø> (+3.38%)
:arrow_up:

apps/gsekit/process/handlers/process.py
18.85% <90.00%> (+0.42%)
:arrow_up:

apps/gsekit/cmdb/handlers/cmdb.py
56.27% <100.00%> (+1.95%)
:arrow_up:

apps/gsekit/cmdb/mock_data.py
100.00% <100.00%> (ø)

apps/gsekit/cmdb/serializers/cmdb.py
97.40% <100.00%> (+0.43%)
:arrow_up:

apps/gsekit/cmdb/views/tests.py
84.93% <100.00%> (+0.20%)
:arrow_up:

apps/gsekit/constants.py
100.00% <100.00%> (ø)

apps/gsekit/job/tests.py
100.00% <100.00%> (ø)

apps/gsekit/process/mock_data.py
100.00% <100.00%> (ø)

apps/gsekit/utils/expression_utils/match.py
72.22% <100.00%> (+8.33%)
:arrow_up:

... and 9 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 a36a02d...dd92e20. Read the comment docs.


(in progress) pk root directory 20230209

still needs work to make wikilinks work: config[root_directory] needs to be injected into mwb_build_wikilink().


Urgent Help: How to use tableManager API out of the component by using useRef?

I with to access tableManager API out of the gridTable component to programatically update table. How can I do that by using useRef??
Help would be much appreciated.
Also, best react table by far used. Thanks for tthis

Hi...
Thanks for your interest...
To get the tableManager instance you can use the onLoad prop which will
give it to you once it's initialized, no need for ref.
Once it's ready, pass it to the highest component state that you want to
use it and from there you can use it from the state or pass it to
its children.
onLoad={tableManger => setTableManger(tableManger)}
or just:
onLoad={setTableManger}
Hope it helps.
Let me know how it goes... :)
On Mon, 22 Feb 2021, 18:06 Chinmay Atrawalkar<EMAIL_ADDRESS>wrote:

I with to access tableManager API out of the gridTable component to
programatically update table. How can I do that by using useRef??
Help would be much appreciated.
Also, best react table by far used. Thanks for tthis
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NadavShaar/react-grid-table/issues/61, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB5ITFXKLPEBFSZT54DHZ5LTAJ6JXANCNFSM4YAZEEJQ
.

Hi, this was really helpful. Sorry, got busy in project so didn't reply but it was really helpful

Glad to hear it.


Create a slice - allPuzzlesSlice

Import into Redux store
needs to make an async AJAX call to backend to receive the product data (asyncThunk)
create selector method to be able to select state

Creating "store" folder and index.js inside store folder


Update iam-credentials.mdx

Tried running "npx sst dev" and got following error:

operation error S3: PutBucketNotificationConfiguration, https response error StatusCode: 403, RequestID: , HostID: , api error AccessDenied: User: arn:aws:iam:::user/sst-user is not authorized to perform: s3:PutBucketNotification on resource: "arn:aws:s3:::sst-asset-**" because no identity-based policy allows the s3:PutBucketNotification action

EDIT: updated 2 other ones that were missing as well. Now its working fine.

Thanks!


Can not deploy Kubernetes artifacts with Apple M1

Description
Getting the following error while trying to deploy Kubernetes artifacts for APIM 4.1.0 and APIM 4.2.0 with Mac m1.

Steps to Reproduce
For APIM 4.1.0

Clone [1] and checkout to 4.1.x branch
Get the prerequisites as in [2]
Start minikube
Navigate to <kubernetes-apim-dir>/simple/am-single in a terminal
Use the following commands to deploy Kubernetes artifacts

helm dependency build
helm install am-single .

Check Kubernetes pods

kubectl get pods
kubectl describe pod <wso2am-mysql-db-service-pod-name>

For APIM 4.2.0

Checkout to 4.2.x branch
Change <kubernetes-apim-dir>/simple/am-single/requirements.yaml as follows

dependencies:
  - name: mysql-am
    version: "4.2.0-1"
    repository: "file://../../advanced/mysql-am"
    condition: wso2.deployment.dependencies.cluster_mysql
  - name: nfs-server-provisioner
    version: "1.1.0"
    repository: "https://helm.wso2.com"
    condition: wso2.deployment.dependencies.nfsServerProvisioner

Follow the rest of the steps as in 4.1.0

[1] - https://github.com/wso2/kubernetes-apim/
[2] - https://github.com/wso2/kubernetes-apim/blob/4.1.x/simple/am-single/README.md
Affected Component
APIM
Version
4.1.0, 4.2.0
Environment Details (with versions)
macOS (Apple M1 Pro)
Relevant Log Output
No response
Related Issues
No response
Suggested Labels
No response

This issue was fixed by PR [1].
[1] - https://github.com/wso2/kubernetes-apim/pull/576


test_engine_image_not_fully_deployed related cases and functions

test_engine_image_not_fully_deployed related cases and functions

prepare_engine_not_fully_deployed_evnironment_with_volumes
prepare_engine_not_fully_deployed_evnironment
reset_nodes_taint
taint_non_current_node
restart_and_wait_ready_engine_count
test_engine_image_miss_scheduled_perform_volume_operations
test_engine_image_not_fully_deployed_perform_volume_operations
test_engine_image_not_fully_deployed_perform_engine_upgrade
test_engine_image_not_fully_deployed_perform_replica_scheduling
test_engine_image_not_fully_deployed_perform_auto_upgrade_engine

ref: longhorn 5014
Signed-off-by: Chris Chien<EMAIL_ADDRESS>

Updated and here was the test result

Updated and here is test result, thank you

Rebase to master and here is pipeline test result

@c3y1huang Could you please help in taking a final look?

@c3y1huang, @khushboo-rancher , updated and test_ha.py result here, thanks

@Mergifyio backport v1.4.x v1.3.x


[4.0Xpt] Create UI pages

motorcycle details page
sign-up and login page
reservation page (test drive)


DevKitSDK  v1.6.1+ (state code = 400)

Hi,
I'd like to report a weird behavior.
I was recently trying to upgrade our DevKitState workshop, and I stumbled upon an issue. After investigations, it turns out the DevKitSDK versions 1.6.1 and 1.6.2 are triggering the following issue, making the device unable to sync with the IoT Hub:

Switching back to v1.6.0 fixed those errors.
DevKitSDK version: 1.6.0
Mico version: 31620002.049
mbed-os version: 5.2.1
mbed TLS version: 2.4.2
WIFI version: wl0: Sep 10 2014 11:28:46 version <IP_ADDRESS>

How to reproduce

flash the MX chip with firmeware v1.6.2 (https://aka.ms/devkit/prod/firmware/latest)
dl the MX chip package for Arduino v1.6.2
compile and upload the DevKitState.ino file to the MX chip

Here is the current version log from the board
DevKitSDK version: 1.6.2
Mico version: 31620002.049
mbed-os version: 5.4.3
mbed TLS version: 2.15.0
WIFI version: wl0: Sep 10 2014 11:28:46 version <IP_ADDRESS>

and the error message:
2019-06-25 14:47:42 INFO:  Iothub Version: 1.2.14

2019-06-25 14:47:45 INFO:  >>>Connection status: connected
2019-06-25 14:47:45 INFO:  >>>IoTHubClient_LL_SendReportedState accepted state for transmission to IoT Hub.
2019-06-25 14:47:45 INFO:  >>>Confirmation[0] received for state tracking id = 0 with state code = 400
2019-06-25 14:47:45 ERROR: DevKitMQTTClient.cpp (ln 337): Report confirmation failed with state code 400
2019-06-25 14:47:55 ERROR: DevKitMQTTClient.cpp (ln 409): Waiting for send confirmation, time is up 10044
2019-06-25 14:47:55 INFO:  >>>Re-connect.

Cheers.

Try working outside of your office, mobile hot-spot for instance, might be firewall issue, happened to me...

Try working outside of your office, mobile hot-spot for instance, might be firewall issue, happened to me...

I'm having this exact same issue as well, I've tested on my mobile hot-spot and I've worked from home today to test on my home connection.
I haven't tested with an older version of the SDK to build an API but @manekinekko had and he confirmed that the problem appeared in v1.6.1 and v1.6.2 of the SDK which would tend to indicate it's not a network issue.
I've had other messages being sent to the Azure Hub (the get started project sends messages that I can monitor on the Hub) but what wasn't working was the Device Twin functionality with the temperatureAlert property, it seems like the report state to the Device Twin functionality in the SDK is failing.

Same here, not a network issue,

If anybody else comes across this issue, i tried looking at other files and use some newer methods, following seems to work and state updates are successfully sent.
`//  Old Code - Does not work
//  char state[500];
//  snprintf(state, 500, "{"firmwareVersion":"%s","wifiSSID":"%s","wifiRSSI":%d,"wifiIP":"%s","wifiMask":"%s","macAddress":"%s","sensorMotion":%d,"sensorPressure":%d,"sensorMagnetometer":%d,"sensorHumidityAndTemperature":%d,"sensorIrda":%d}", firmwareVersion, wifiSSID, wifiRSSI, wifiIP, wifiMask, macAddress, sensorMotion, sensorPressure, sensorMagnetometer, sensorHumidityAndTemperature, sensorIrda);
//  DevKitMQTTClient_ReportState(state);
//  delay(600000);
// New Code, Does work
char* state;
JSON_Value* root_value = json_value_init_object();
JSON_Object* root_object = json_value_get_object(root_value);
// Only reported properties:
(void)json_object_set_string(root_object, "firmwareVersion", firmwareVersion);
(void)json_object_dotset_string(root_object, "wifi.wifiSSID", wifiSSID);
(void)json_object_dotset_number(root_object, "wifi.wifiRSSI", wifiRSSI);
(void)json_object_dotset_string(root_object, "wifi.wifiIP", wifiIP);
(void)json_object_dotset_string(root_object, "wifi.wifiMask", wifiMask);
(void)json_object_dotset_string(root_object, "wifi.macAddress", macAddress);
(void)json_object_dotset_number(root_object, "sensor.sensorMotion", sensorMotion);
(void)json_object_dotset_number(root_object, "sensor.sensorHumidityAndTemperature", sensorHumidityAndTemperature);
(void)json_object_dotset_number(root_object, "sensor.sensorMagnetometer", sensorMagnetometer);
(void)json_object_dotset_number(root_object, "sensor.sensorPressure", sensorPressure);
(void)json_object_dotset_number(root_object, "sensor.sensorIrda", sensorIrda);
state = json_serialize_to_string(root_value);
json_value_free(root_value);
DevKitMQTTClient_ReportState(state);
delay(600000); //adjust according to your preferences.`

Hi, we have released workbench 0.10.15 and fixed the bug. You can create a new sample project and check it.


qt6.qtbase: don't retain cmake as a runtime dependency

Description of changes
Currently, cmake is a runtime dependency of qt6.qtbase:
$ nix-store -q --references $(nix-build -A qt6.qtbase) | grep cmake
/nix/store/4878vn5amhb888da986clb3sbc4dczr5-cmake-3.24.3

Adding qt-cmake etc. to the dev output fixes that.
Remaining binaries in the qtbase output: androiddeployqt  androidtestrunner  qt-configure-module  qtpaths  qtpaths6
I didn't attempt to rebuild qtwebengine, otherwise nixpkgs-review shows no failures.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

nixpkgs-review reveals no new failures, macos 10.15


doc update for https://github.com/trailblazer/cells/pull/448

Doc update for https://github.com/trailblazer/cells/pull/448, if that PR is approved.

My documentation ninja is back! :boom: :hamburger:


Error. Registration form keeps popping for a registered user after token has expired

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Using this version of ASP.NET Core '...'
Run this code '....'
With these arguments '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Include the output of dotnet --info

I have implemented the WSFederation successfully on Asp.net core. When the idle time of 20 mins lapses, the application re-authenticates by calling the ADFS page. However, the application takes the registered user back to the registration page. I will then either recycle the application pool or restart the website to make it work again. How do I resolve the issue ? The console is showing error 401

@jgathairu can you share what your Startup.cs code looks like? Any other interesting settings or configuration that might be relevant here?

@Eilon thank you for your interest on my issue. on start up
services.AddAuthentication()
.AddWsFederation(WsFederationDefaults.AuthenticationScheme, "Login Using Office Account",
options =>
{
options.MetadataAddress = "https://xxxxxxxxxxxx/FederationMetadata/2007-06/FederationMetadata.xml";
//options.Wtrealm = "https://localhost:44306/";
options.Wtrealm = "https://xxxxxxxxxxxx.org/";
}).AddCookie();
        services.ConfigureApplicationCookie(options =>
            {
                options.LoginPath = "/Identity/Account/LogIn";
            }
        );
        services.ConfigureApplicationCookie(options => options.LogoutPath = "/Home/Index");

and on logout
//delete all cookies first
foreach (var key in HttpContext.Request.Cookies.Keys)
{
HttpContext.Response.Cookies.Delete(key);
}
        await _signInManager.SignOutAsync();
        _logger.LogInformation("User logged out.");
        return SignOut(new AuthenticationProperties { RedirectUri = "/Home/Index" },
            CookieAuthenticationDefaults.AuthenticationScheme,
            WsFederationDefaults.AuthenticationScheme);

The solution I found that works were to increase the application pool idle time from default 20 minutes to any minutes of choice. The user can then work and logout of the application without issues. You can also review the code I have and suggest some improvements if needed

Calling Cookies.Delete should not be necessary.


New example: multimodal.py, to test PTSampler evidence estimation

It's just the example in the docs, plus a little evidence check. Here's the result:
Estimated log evidence =  -16.9586413385 +/- 7.29507626509
Analytic log evidence =  -6.67931612501

which means that there is at least one bug in this code! But it runs to completion, and the docs are up to date. What more could one want?

Hi Phil, David, all,
Sorry for taking so very loooooooooong to get back to this.  I think I understand what the problem is, and it's not a bug in the code.  Instead, it's a bug in the "test."  The example from the docs has a flat, improper prior (log_prior = 0.0 everywhere), so the TI integral does not converge:
\int d\beta <\log L>_\beta = \int d\beta -1/(2 \beta)
is, in fact, infinite---it diverges like log(x) as x --> 0.  The evidence is well-defined---it is just the integration method that fails.
Embarrassingly I was bitten by this same bug when writing the PT Sampler tests (note that there is---or at least was---an evidence check in the test() routine for PT Sampler), but didn't recognise it again here.  The solution would be to put in a prior that is wide (maybe flat between +/- 10-sigma?), and ensure that the highest temperature ladder can sample from it.

@farr Your suggestion explains my correct result with PTSampler that i cited here above - i have used proper prior. I think that issue with evidence estimation must be explained in docs or even print a warning message when calling PTSampler.thermodynamic_integration_log_evidence:)

I've added the suggested changes to the docs in #154 ; Dan, if you pull
those changes into emcee, you can close this issue, too.
On Fri, May 22, 2015 at 8:44 AM Ilya<EMAIL_ADDRESS>wrote:

@farr https://github.com/farr Your suggestion explains my correct
result with PTSampler that i cited here above - i have used proper prior.
I think that issue with evidence estimation must be explained in docs or
even print a warning message when calling
PTSampler.thermodynamic_integration_log_evidence:)
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104553734.

An improper prior error! That's a rare treat :-) What does the
multimodal.py test return now, for the evidence values?
On Fri, May 22, 2015 at 9:17 AM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

I've added the suggested changes to the docs in #154 ; Dan, if you pull
those changes into emcee, you can close this issue, too.
On Fri, May 22, 2015 at 8:44 AM Ilya<EMAIL_ADDRESS>wrote:

@farr https://github.com/farr Your suggestion explains my correct

result with PTSampler that i cited here above - i have used proper prior.
I think that issue with evidence estimation must be explained in docs or
even print a warning message when calling
PTSampler.thermodynamic_integration_log_evidence:)
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104553734.

—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104561337.

I haven't tried it on the multimodal.py, but it passes with flying colours
the evidence computation and sampling on a unimodal Gaussian in
check_pt_sampler (line 123 of tests.py).  If you want to give it a go, you
can have a look at the code there---it took me forever to pass that test
because I originally used an improper prior, and couldn't understand why I
was failing.  As I said, it's a bit embarrassing that I forgot all about
that experience when thinking about your bug report.
On Fri, May 22, 2015 at 9:24 AM Phil Marshall<EMAIL_ADDRESS>wrote:

An improper prior error! That's a rare treat :-) What does the
multimodal.py test return now, for the evidence values?
On Fri, May 22, 2015 at 9:17 AM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

I've added the suggested changes to the docs in #154 ; Dan, if you pull
those changes into emcee, you can close this issue, too.
On Fri, May 22, 2015 at 8:44 AM Ilya<EMAIL_ADDRESS>wrote:

@farr https://github.com/farr Your suggestion explains my correct

result with PTSampler that i cited here above - i have used proper
prior.
I think that issue with evidence estimation must be explained in docs
or
even print a warning message when calling
PTSampler.thermodynamic_integration_log_evidence:)
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104553734.

—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104561337.

—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104564027.

Hmm. examples/multimodal.py does already have a proper prior, it turns out:
# Use a 2D uniform prior, correctly normalized:
def logp(x):
    xmax = 5.0
    if (abs(x).any() > xmax):
        logp = -np.inf
    else:
        logp = -2.0*np.log(2.0*xmax)
    return logp

What could be wrong with this?

I think the line
if (abs(x).any() > xmax):

is a mistake.  It should be written
if np.any(np.abs(x) > xmax):

For example:
x = array([1.0, 2.0])
if x.any() > 1:
    print 'Yep'
else:
    print 'Nope'

prints 'Nope', while
if np.any(abs(x) > 1):
    print 'Yep'
else:
    print 'Nope'

prints 'Yep'.  So, the prior is, in fact, unnormalised.  I fixed that line, and increased the temperature density in multimodal.py (after examining a plot of the TI integrand versus beta, and seeing a lot of jagged structure), and now it works:
Estimated log evidence =  -6.89598100431 +/- 0.0546850237424
 Analytic log evidence =  -6.67931612501

These changes are pushed to the tip of the fix-pt-docs branch referred to in pull request #154, so pulling that branch should also resolve this issue.

@farr Will, could you please add some potential diagnostics tools for better temperature settings somewhere in docs? You wrote that you have examined a plot of the TI integrand versus beta... As far as i understand there's no universal temperature setting.

@ipashchenko Eventually, yes.  That's a bit of a long-term project.
You're right that there is no universal temperature setting.  One attempt to address this issue for sampling is http://arxiv.org/abs/1501.05823 .  For TI, just looking at the plot of the integrand is usually enough to diagnose problems, but the uncertainty reported by the TI method can help, too (i.e. if it's large, then you probably need a denser T spacing).
Anyway, this is a bit like universal methods for determining burnin: there are none, and the topic is very broad.

Great, thanks Will! Sorry about the crap coding - although I am glad that
my bug was in use of numpy rather than understanding of how to apply
probability theory.
On Fri, May 22, 2015 at 2:12 PM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

@ipashchenko https://github.com/ipashchenko Eventually, yes. That's a
bit of a long-term project.
You're right that there is no universal temperature setting. One attempt
to address this issue for sampling is http://arxiv.org/abs/1501.05823 .
For TI, just looking at the plot of the integrand is usually enough to
diagnose problems, but the uncertainty reported by the TI method can help,
too (i.e. if it's large, then you probably need a denser T spacing).
Anyway, this is a bit like universal methods for determining burnin: there
are none, and the topic is very broad.
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104656158.

No worries re: coding---I'm just glad to have (finally!) tracked down and
resolved the issue!
On Fri, May 22, 2015 at 2:42 PM Phil Marshall<EMAIL_ADDRESS>wrote:

Great, thanks Will! Sorry about the crap coding - although I am glad that
my bug was in use of numpy rather than understanding of how to apply
probability theory.
On Fri, May 22, 2015 at 2:12 PM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

@ipashchenko https://github.com/ipashchenko Eventually, yes. That's a
bit of a long-term project.
You're right that there is no universal temperature setting. One attempt
to address this issue for sampling is http://arxiv.org/abs/1501.05823 .
For TI, just looking at the plot of the integrand is usually enough to
diagnose problems, but the uncertainty reported by the TI method can
help,
too (i.e. if it's large, then you probably need a denser T spacing).
Anyway, this is a bit like universal methods for determining burnin:
there
are none, and the topic is very broad.
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104656158.

—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104663694.

Yeah! Also: fantastic to see evidence values coming out of the PTSampler!
:-)
@kbarbary, your dreams are being fulfilled here.
On Fri, May 22, 2015 at 2:43 PM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

No worries re: coding---I'm just glad to have (finally!) tracked down and
resolved the issue!
On Fri, May 22, 2015 at 2:42 PM Phil Marshall<EMAIL_ADDRESS>wrote:

Great, thanks Will! Sorry about the crap coding - although I am glad that
my bug was in use of numpy rather than understanding of how to apply
probability theory.
On Fri, May 22, 2015 at 2:12 PM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

@ipashchenko https://github.com/ipashchenko Eventually, yes. That's
a
bit of a long-term project.
You're right that there is no universal temperature setting. One
attempt
to address this issue for sampling is http://arxiv.org/abs/1501.05823
.
For TI, just looking at the plot of the integrand is usually enough to
diagnose problems, but the uncertainty reported by the TI method can
help,
too (i.e. if it's large, then you probably need a denser T spacing).
Anyway, this is a bit like universal methods for determining burnin:
there
are none, and the topic is very broad.
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104656158.

—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104663694.

—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104663877.

OK, something's weird here: I pulled down @farr's fix-pt-docs branch into a fix-pt-docs branch of my own, and tried to make multimodal.py work. I get:
Estimated log evidence =  7.26355058317 +/- 1.32035266078
Estimated log evidence =  7.26947875152 +/- 1.3040628331
Analytic log evidence =  -6.67931612501

in two runs of the code. The np.any() lines is there, and I'm using @farr's cooling schedule...

There was some confusion on my part with a "-" sign in the integral earlier
today when I transitioned to using trapz. Can you check that you have
commit 81782de? If you do, I'm not sure what is going on....
On Fri, May 22, 2015 at 9:35 PM Phil Marshall<EMAIL_ADDRESS>wrote:

OK, something's weird here: I pulled down @farr https://github.com/farr's
fix-pt-docs branch into a fix-pt-docs branch of my own, and tried to make
multimodal.py work. I get:
Estimated log evidence =  7.26355058317 +/- 1.32035266078
Estimated log evidence =  7.26947875152 +/- 1.3040628331
Analytic log evidence =  -6.67931612501
in two runs of the code. The np.any() lines is there, and I'm using @farr
https://github.com/farr's cooling schedule...
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104761118.

Yep, I've got that commit. Here's my branch if you want to check it out.

Hmm.
PT sampling for 1000 iterations...
Temperature swap acceptance rates are
T =  1000000.0  accept =  0.99983
T =<PHONE_NUMBER>92  accept =  0.999745
T =<PHONE_NUMBER>16  accept =  0.99966
T =<PHONE_NUMBER>99  accept =  0.99949
T =<PHONE_NUMBER>29  accept =  0.999145
T =  92367.0857187  accept =  0.998615
T =  57361.5251045  accept =  0.9978
T =  35622.4789026  accept =  0.996665
T =  22122.1629107  accept =  0.99468
T =  13738.2379588  accept =  0.990925
T =  8531.67852417  accept =  0.985705
T =  5298.31690628  accept =  0.977805
T =  3290.34456231  accept =  0.96518
T =  2043.35971786  accept =  0.94696
T =  1268.96100317  accept =  0.922105
T =<PHONE_NUMBER>67  accept =  0.88864
T =<PHONE_NUMBER>48  accept =  0.85261
T =<PHONE_NUMBER>31  accept =  0.821315
T =<PHONE_NUMBER>14  accept =  0.801945
T =<PHONE_NUMBER>53  accept =  0.79432
T =  72.7895384398  accept =  0.78735
T =  45.2035365636  accept =  0.780655
T =  28.0721620394  accept =  0.772305
T =  17.433288222  accept =  0.765715
T =  10.8263673387  accept =  0.765155
T =  6.7233575365  accept =  0.766605
T =  4.17531893656  accept =  0.76775
T =  2.5929437974  accept =  0.766465
T =  1.61026202756  accept =  0.76507
T =  1.0  accept =  0.76491

Estimated log evidence =  -6.87513567321 +/- 0.085128437244
 Analytic log evidence =  -6.67931612501

Did yours print all the temperature and swap acceptance info?  If not, could it be that you were running of an older commit because you didn't install?  I'm sort of at a loss here to explain the different behaviour....

Beats me. Feel free to close this, and I'll just pull from the base repo
master branch once it all gets merged in properly. Thanks!
On Fri, May 22, 2015 at 10:41 PM, Will Meierjurgen Farr <
<EMAIL_ADDRESS>wrote:

Hmm.
PT sampling for 1000 iterations...
Temperature swap acceptance rates are
T =  1000000.0  accept =  0.99983
T =<PHONE_NUMBER>92  accept =  0.999745
T =<PHONE_NUMBER>16  accept =  0.99966
T =<PHONE_NUMBER>99  accept =  0.99949
T =<PHONE_NUMBER>29  accept =  0.999145
T =  92367.0857187  accept =  0.998615
T =  57361.5251045  accept =  0.9978
T =  35622.4789026  accept =  0.996665
T =  22122.1629107  accept =  0.99468
T =  13738.2379588  accept =  0.990925
T =  8531.67852417  accept =  0.985705
T =  5298.31690628  accept =  0.977805
T =  3290.34456231  accept =  0.96518
T =  2043.35971786  accept =  0.94696
T =  1268.96100317  accept =  0.922105
T =<PHONE_NUMBER>67  accept =  0.88864
T =<PHONE_NUMBER>48  accept =  0.85261
T =<PHONE_NUMBER>31  accept =  0.821315
T =<PHONE_NUMBER>14  accept =  0.801945
T =<PHONE_NUMBER>53  accept =  0.79432
T =  72.7895384398  accept =  0.78735
T =  45.2035365636  accept =  0.780655
T =  28.0721620394  accept =  0.772305
T =  17.433288222  accept =  0.765715
T =  10.8263673387  accept =  0.765155
T =  6.7233575365  accept =  0.766605
T =  4.17531893656  accept =  0.76775
T =  2.5929437974  accept =  0.766465
T =  1.61026202756  accept =  0.76507
T =  1.0  accept =  0.76491
Estimated log evidence =  -6.87513567321 +/- 0.085128437244
Analytic log evidence =  -6.67931612501
Did yours print all the temperature and swap acceptance info? If not,
could it be that you were running of an older commit because you didn't
install? I'm sort of at a loss here to explain the different behaviour....
—
Reply to this email directly or view it on GitHub
https://github.com/dfm/emcee/pull/131#issuecomment-104783042.


add description alteration and roll options to Oracle Spellshape feats

Also cleaned up Ley Line Conduit Feats item alteration description.

Closing to redo


Apps disappear from ClusterManager when cluster is reimported

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Create a new vanilla cluster (in my case k3s v1.19.5+k3s2)
Import the new cluster (in ClusterManager Add cluster -> Other cluster)
In the default project on the new cluster launch any catalog app, example Redis (Apps -> Launch)
Delete the cluster from Rancher
Import the cluster again (repeat step 2)
Add the namespace (redis) back to the default project

Result:
Click on the apps tab in clustermanager and the deployed app is no longer visible. The app is still visible on the "installed apps" section in the new cluster explorer and can still be viewed using the helm CLI - it can even be deleted via helm or cluster explorer.
Environment information

Rancher 2.5.5, k3s v1.19.5+k3s2
Installed via Docker as a single node
Docker version 19.03.11

Additional Info
Docker writes error logs:
2021/01/18 15:16:01 [ERROR] error getting app redis apps.project.cattle.io "p-zq6m8/redis" not found
2021/01/18 15:16:20 [ERROR] error getting app redis apps.project.cattle.io "p-zq6m8/redis" not found

Apps in Manager are a Rancher type stored in the management ("local") cluster.  They get deleted when you delete that cluster and are gone now.
These exist because Helm 2 with Tiller lacked adequate controls to limit who can do what in a multi-tenant system.  It ultimately still calls Helm to do the actual install though, which stores its own state inside the target cluster.
Then Helm 3 was released, which stores it in a different, incompatible places.  In Manager we added support for 3 but otherwise left the apps type in place.
But Helm 3 also addressed their multi-tenant problems, so the newer "Apps & Marketplace" in Explorer just uses Helm 3 and its state in the cluster directly. Our own "Apps" type is not needed in between anymore.  This also means if you install something with Helm 3 in the old Apps or the CLI, it becomes also visible in the new one.

Apps in Manager are a Rancher type stored in the management ("local") cluster.  They get deleted when you delete that cluster and are gone now.
These exist because Helm 2 with Tiller lacked adequate controls to limit who can do what in a multi-tenant system.  It ultimately still calls Helm to do the actual install though, which stores its own state inside the target cluster.
Then Helm 3 was released, which stores it in a different, incompatible places.  In Manager we added support for 3 but otherwise left the apps type in place.
But Helm 3 also addressed their multi-tenant problems, so the newer "Apps & Marketplace" in Explorer just uses Helm 3 and its state in the cluster directly. Our own "Apps" type is not needed in between anymore.  This also means if you install something with Helm 3 in the old Apps or the CLI, it becomes also visible in the new one.

Thanks for that - makes things a lot clearer. So would the way forward then be to use Helm 3 and the Explorer "Apps & Marketplace?"

Thanks for that - makes things a lot clearer. So would the way forward then be to use Helm 3 and the Explorer "Apps & Marketplace?"

Yes; the older apps will eventually be deprecated.

Yes; the older apps will eventually be deprecated.

Tried the Explorer way:

added a private repository using Explorer
deployed a new chart
Removed cluster
Added cluster back

In Explorer the repository as well as the deployed charts survive cluster delete / add. In the charts view it complained about 2 configmaps missing:
configmaps "rancher-partner-charts-dlj9f" not found
configmaps "rancher-charts-5bngr" not found

However using the Explorer charts definitely appears to be more robust. I'll deploy all new charts this way.
One other point about the UI; we are using private repositories - I was able to add ours using the format https://user:pass@url ; cluster manager style support for private repositories would be good (fields for credential input)

Tried the Explorer way:

added a private repository using Explorer
deployed a new chart
Removed cluster
Added cluster back

In Explorer the repository as well as the deployed charts survive cluster delete / add. In the charts view it complained about 2 configmaps missing:
configmaps "rancher-partner-charts-dlj9f" not found
configmaps "rancher-charts-5bngr" not found

However using the Explorer charts definitely appears to be more robust. I'll deploy all new charts this way.
One other point about the UI; we are using private repositories - I was able to add ours using the format https://user:pass@url ; cluster manager style support for private repositories would be good (fields for credential input)


Use 'system' attribute when adding consul user & group

Since consul is a system service, it's probably better to specify 'system' attribute to group and user resources: https://github.com/johnbellone/consul-cookbook/blob/master/recipes/default.rb#L35-L36
This can help distinguish them from those able to login. Also, since we have login shell provided, would be nice to specify existing $HOME location, e.g. /var/lib/consul.

The system attribute has been added to master and will be released as 2.0.


initialState warns a lot

The combineReducers call has validation that ensures that the initialState passed aligns with the reducer structure. This means that it logs warnings when initialState is used.

@lelandrichardson


Shading in offscreen render

Is it also possible to render a scene offscreen with the same shading?

Add this before the renderer.render call:
renderer.autoenablesDefaultLighting = true


Consider adopting Red Hat Upstream First approach with tektoncd-operator

It appears this repo gets much more activity than its upstream github.com/tektoncd/operator repo. In addition, this repo already has a release on OperatorHub.io while its upstream does not. In light of the Red Hat "Upstream First" approach described in this article, https://opensource.com/article/16/12/why-red-hat-takes-upstream-first-approach, consider adopting such an upstream first approach with the tektoncd operator.

@ron1 thanks for the issue, and you are right on point, we are working towards that goal.
This repository was initiated before tektoncd/operator while we were making it adopt by upstream.
It is on our roadmap to sync up both of the repository in the relative shortterm (aka ~2month), but the past few months the focus was put more on the rest of the upstream tekton projects (pipeline, triggers, …) and on driving towards having beta (supported) APIs.
/kind feature

/kind question

@vdemeester thanks for the update. Glad to hear a repo sync is on the near-term roadmap.
How usable is the tektoncd/operator in its current form? Would you recommend folks use this operator until the sync occurs? Also, would you expect this operator to work on OCP 3.11 or is it dependent upon OCP 4.x features.

@ron1 the next release of tekton (0.11 and beta, …) will require 1.15, so in terms of OpenShift, 4.3 will be the minimum supported version.

@vdemeester Any plans to support tekton 0.10 running on older ocp/k8s versions for some period of time?


Fix typo in file path

Proposed changes

Unreleased project version (optional)

Related issues (optional)

Deploy preview for docsdocker ready!
Built with commit 90dbbc6faf5db565274f477d29b3d451c1155840
https://deploy-preview-9820--docsdocker.netlify.com


master is out of sync with 9.2.5 branch

The 'master' branch now contains the changes for MQ 9.2.5.  Note that these changes are rarely needed for you to use the sample, and you can still build (say) an MQ 9.2.5 image with code from years ago, by setting MQ_VERSION environment variable for use by the Makefile.


uninstall removes the configuration file

uninstall removes the configuration file (salt/conf/minion)

I assume the config file is part of the instllation.
uninstall removes all parts of the installation.
I need to specify, that salt/conf/minion must not be removed.

Do I use "<file id"?
salt-windows-msi\wix\MinionMSI\dist-amd64.wxs
is the only file with "<file id" in it
Who creates it?
Why has each file its own component?
Does this slow down uninstall?

Remove the GUID of the component.

Need optional removal

Opening another issue


fix: render border colors in Avatar with placeholder initials

Description
This PR fixes an issue with the Avatar component where the color prop is ignored when using placeholder initials.
Partially Fixes #451
Type of change

[X] Bug fix (non-breaking change which fixes an issue)

Breaking changes
None
How Has This Been Tested?

[X] Added a new unit test to verify expected classnames are applied in the appropriate scenario

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

Thanks for merging! Any idea when this change will be released?

@adamgruber I think the next release will be the 0.4.0, which should be done when #443 and #465 is done. You can help to finish this task as well, I have a PR pending for review #500 and we have some other components that need to allow per-component theme overwriting.


Iss35 ks

TS to review + on Tuesday (12/10) with LB we will add to dropbox

issue to fix: missing dates appear to be represented by "1/1/0001", we should replace these with missing/blank in the csv.
should include a dropbox dl step.


make dgraph catch SIGTERM

Can you please send me an email @tullo. I have a couple questions.

Sent you a short email.


Additional support for factur-x (PDF-A3)

The factur-x (ZUGFeRD) standard needs the attached files listed in the AF-tag.
Furthermore, additional metadata is necessary for the embedded files.
Easy solution: Allow users to supply additionalParams.
To access the attached files of factur-x invoices, access to the PDFRawStream is needed.

Hello @DkDavid!
I'm not familiar with the details of the ZUGFeRD standard. I don't know anything about the AF entry and the PDF spec doesn't seem to list it in the table of catalog entries. Can you please point me to some documentation about this? I'd like to understand it better before merging this.

Hi Hopding,
sorry for my late reply.
The standard is used to attach invoice meta-data to PDF/A3 documents (Germany: ZUGFeRD, France: Factur-X, since version 2.1 the name is Factur-X and a European standard exists). Most additions can easily be made using the existing API. I can add a minimal example to get the conformance with the standard, if desired. However, additional params for the embedded file as well as the AF entry are necessary.
The specification can be downloaded here: https://www.ferd-net.de/standards/zugferd-versionsarchiv/zugferd-2.1.html
The additional AF entry is mentioned in "ZUGFeRD-2.1.0 - Spezifikation_TA_Anlage-A" - page 8 (diagram) for example.

@DkDavid Would it be possible to add specific options to the embedded file options? I would prefer that approach as it is easier to document and use than allowing users to pass arbitrary values. Note that I haven't had a chance to familiarize myself with the ZUGFeRD specification, so just let me know if there's a specific reason this wouldn't work.

@Hopding Yes, that would be possible. The "additional param" needed for factur-x is: additionalParams: {'AFRelationship': 'Alternative'} for the xml attachment.
I just thought it would be more flexible for future standards. However, the optional param "AFRelationship" would be sufficient for factur-x.
This as well as the proposed change in PDFEmbeddedFile.ts, and the addition of the CIDToGIDMap would be necessary to fulfill compliance. Everything else is easily possible with the current api.
For CIDToGIDMap see https://github.com/Hopding/pdf-lib/issues/230#issuecomment-705460408

@Hopding I digged into the Factur-X (european harmonized name of ZugFERD) and the PDF-A3 specification. Nearly all of the changes can be led back to the PDF-A3 specification. Therefore I changed the references accordingly and implemented your comments.
To reach PDF-A3 compliance three additional things have to be done by the user. All of them are reachable by the current API.
`const hash =   crypto.createHash('sha256').update(DOCUMENTID + new Date().toISOString ).digest(); //crypto.subtle.digest('SHA-512', data);
const hashArray = Array.from(new Uint8Array(hash));
const hashHex = hashArray.map((b) => b.toString(16).padStart(2, '0')).join('');
const permanentDocumentId = PDFHexString.of(hashHex);
const changingDocumentID = permanentDocumentId; // updated when document is changed
doc.context.trailerInfo.ID = doc.context.obj([permanentDocumentId, changing]);
   // MarkInfo specifies if the document is a tagged pdf file. => 9.7 https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/pdf_reference_archives/PDFReference.pdf
    const rootref = doc.context.obj({Marked: true})
    doc.catalog.set(PDFName.of('MarkInfo'), rootref);

   // => 14.7.2 https://www.adobe.com/content/dam/acom/en/devnet/pdf/pdfs/PDF32000_2008.pdf
    const structTreedata = doc.context.obj({Type: PDFName.of('StructTreeRoot')})
    const structTreeref = doc.context.register(structTreedata);
    doc.catalog.set(PDFName.of('StructTreeRoot'), structTreeref);`

The changes in this PR were just released in v1.13.0.

Hello everyone.
First of all, I apologize for commenting on a closed issue.
I wanted to ask if it is possible to provide us with a working example to generate a PDF with the Factur-X (european harmonized name of ZugFERD) and the PDF-A3 specification.
Thanks in advance and sorry for the inconvenience.

Hello everyone. First of all, I apologize for commenting on a closed issue. I wanted to ask if it is possible to provide us with a working example to generate a PDF with the Factur-X (european harmonized name of ZugFERD) and the PDF-A3 specification. Thanks in advance and sorry for the inconvenience.

for PDF-A3 follow this #230


model_to_dot (vis_utils.py) includes activation fn

The name of the activation function applied to a layer's output is now included in the output label for that layer for images created by the model_to_dot() function in vis_utils.py.

Thanks for the PR! However, I don't believe this would be a widely useful feature. We won't be merging it.

OK. I was finding it useful for examining networks generated algorithmically, but that is probably not a common usage.


Fix disable encryption

Fix disable encryption bug caused by the new OSCrypt async DPAPI key provider
Fixes ungoogled-software/ungoogled-chromium#2751

Hmm I compiled with this patch, but the issue still persists.


Adding global css documentation, take 2

Adding global css documentation per https://github.com/mxstbr/react-boilerplate/issues/741
Update: Trying this again.  I deleted some extraneous commits that somehow made their way into my fork and now the merge seems to be happy.  Please let me know if I need to do anything else.

Coverage remained the same at 98.346% when pulling e023a4599c3b7dcf301a5dd2f1ce314666eb02cc on bobkocisko:master into da3e502f3233a682b85f4d1227ebcb5f6581cadb on mxstbr:master.

Coverage remained the same at 98.346% when pulling e023a4599c3b7dcf301a5dd2f1ce314666eb02cc on bobkocisko:master into da3e502f3233a682b85f4d1227ebcb5f6581cadb on mxstbr:master.

Coverage remained the same at 98.346% when pulling 2a1fef6be3c7224e0aaa2f08213d979f38eb199e on bobkocisko:master into da3e502f3233a682b85f4d1227ebcb5f6581cadb on mxstbr:master.

@bobkocisko It's looking great 😃
I hope to get time to try it out in a few hrs...

Thanks Glen!  You know what, I just realized that I probably missed something in the setup part of the docs.  If you don't mind waiting till Monday I can verify at work and update this one last time.
Sent from my iPhone

On Jul 30, 2016, at 4:56 PM, Glen Ihrig<EMAIL_ADDRESS>wrote:
@bobkocisko It's looking great 😃
I hope to get time to try it out in a few hrs...
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@bobkocisko No worries, do what's needed.

Coverage remained the same at 98.346% when pulling 7bb4095100eb133743d78b977b18909405b6df22 on bobkocisko:master into bfe0c201053ffe052ec2dfe010a7dd2c7f054c10 on mxstbr:master.

Ok Glen it should be ready to go, although I must admit that I'm not entirely sure about the :global css usage part.  If anyone has experience using that in react-boilerplate it would be great to get them to weigh in on it.

Coverage remained the same at 98.346% when pulling e2bf3f25788877a3c22a24bd6f2f34a3371ef99e on bobkocisko:master into bfe0c201053ffe052ec2dfe010a7dd2c7f054c10 on mxstbr:master.

This looks ace, I think this is good to go! @gihrig your thoughts?

I haven't actually tried it out, but reading the doc it looks top-notch, so yeah 💯

Awesome, good job @bobkocisko! 🔥

Thanks guys!  Glad to be able to help.  BTW, great job to you on react-boilerplate!  Being brand new to React, it was a huge help not only to sift through the React ecosystem but also to have the extra automation and production-quality tools available for free.  Keep up the top-notch work!

Thanks for this clarification @bobkocisko - a huge time saver!
Do you know by a chance how to reference bootstrap's CSS when DLL plugin is off? My app does now work in production mode when react-bootstrap is included, unfortunately Can't figure out where to exclude bootstrap-css-only if not in DLL config.
The reason why I had to switch DLL plugin off is because it's currently incompatible with WebWorkers in dev mode :–) https://github.com/mxstbr/react-boilerplate/issues/784

Wow that's a weird error that I thankfully haven't run into.  I hope you can find a solution to get the dllPlugin going again.
The good news is that react-bootstrap should work fine without the dllPlugin.  The parts of the documentation referring to dllPlugin are only to exclude bootstrap-css-only from being built into dllPlugin.  If you don't have dllPlugin turned on then there should not be any problem.
If you're having a problem getting it going though I don't think I can offer any specific help since I've not run into having to remove dllPlugin.
Good luck!

Looks like I was able to figure out what was wrong. This actually had nothing to do with bootstrap-css-only.
The issue was with what webpack's DedupePlugin was doing with react-bootstrap in production. After removing the plugin from webpack.prod.babel.js, I got my app with mapbox's WebWorkers working again!
The cost of removing DedupePlugin for me was just extra 4KB in the build folder :–)
This issue is probably relevant:
https://github.com/webpack/webpack/issues/959

Great!
Sent from my iPhone

On Aug 7, 2016, at 7:45 AM, Alexander Kachkaev<EMAIL_ADDRESS>wrote:
Looks like I was able to figure out what was wrong. This actually had nothing to do with bootstrap-css-only.
The issue was with what webpack's DedupePlugin was doing with react-bootstrap in production. After removing the plugin from webpack.prod.babel.js, I got my app with mapbox's WebWorkers working again!
The cost of removing DedupePlugin for me was just extra 4KB in the build folder :–)
This issue is probably relevant:
webpack/webpack#959
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Add lamp topic

Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/main/CONTRIBUTING.md.
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288, size <= 75 kB)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

LAMP is a very popular group of software to server operators. Even the Wikimedia projects use it.

Something that does not neatly fit into the binary options above

[ ] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/main/docs

Please replace this line with an explanation of your proposed changes.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Thanks for the contribution!


HSR getHealthServiceRequestSummary failed because Adapter org.w3._200…

…1.xmlschema.Adapter1 is not applicable to the field type java.time.Instant

changes have been moved to https://github.com/bcgov/jag-icon-2/pull/73


kore-rpc support logging options directly

@geo2a is working on https://github.com/runtimeverification/pyk/issues/300, which is to be able to audit lemma coverage of proofs in a semantics, to determine which simplification rules are actually needed or not.
Currently, we have to launch the RPC server on the side with the correct options, and the scrape the log entries on the side as well.
Can we make each RPC call has an extra optional argument logs: ["LOG_ID_1", ..., "LOG_ID_N"], and the responses come back with the log entries for that given call? That way we can get back exactly the log entries for each call, instead of having to rescrape file logs between calls.

First log entries that we care to support:

rules: rule names that are used to do rewriting.
equations: rule names that are used from semantics axioms.
simplifications: rule names that are used from simplification axioms.

We could make it more specific too, by having a boolean flag: log-rules, log-equations, log-simplifications.

From discussion in the team:

It would be good to pin-point exactly what information should be included in the log. That way we will have more flexibility in how we implement it (the information needs to be consistent in both hs-booster-proxy and old backend kore-rpc). We would then add this information as structured data in the rpc response types.
Some rules do not have names, do we use the location in this case? (worse than that, some equations do not have location information)
Experience shows that it often matters more which rules or equations did not apply and why. kore-rpc can log this, for specific named equations. Maybe it would be even better to focus on particular terms, too (unclear how to specify those).

The tool in question here is for auditing existing proof-suites and removing lemmas that do not do any work anymore. That usually happens because in PR #NNN, you introduce some simplification rules, and then in #NNN+3, you introduce more more general rules which make the original rules redundant. So we want a tool that tells us which rules are actually applied, for quickly pruning uneeded simplification rules.
We also want a way to tell which rules are needed for which tests, so that when we upstream lemmas (and tests for lemmas) from client engagements, we can do so in a systematic way by using this to audit the rules used for each test.
So, yes, people have asked for "why doesn't this rule apply", but that isn't what this is for. It's for "I want the log of all the rules that did apply".


Update usages of AppearanceComponent.TryGetData()

About the PR
When doing a build of Content.Client, there's a large number of warnings generated; a decent chunk of these are from using AppearanceComponent.TryGetData(), which has been marked as obsolete. This PR removes all but one of these warnings, and gets a few more along the way.
This is quite chunky, so it's split into a few CLs:

b2dac14c2f1949b06c2e3c985219b0a93e3a68ec Is non-controversial changes, where the systems already had access to the non-obsoleted version - just shuffling arguments around
a0f18e35473bb1898c237d4474d75a1f18da4969 - Contains changes where I had to make a minor change to get the data (e.g.  changing access level private->protected for some SharedApperenceSystem pointers)
Three slightly more complex ones - StackVisualizer, RecyclerVisualizer and DisposalUnitVisualizer needed changes to their prototypes and some movement between Content.Client/Shared/Server.

I noted a couple of things doing this:

I'm seeing intermittent failures from Content.IntegrationTests (but these are happening on master, too)
Most implementations of VisualizerSystem don't call the base class in OnAppearanceChange - seems like they ought to? (I'm happy to go though and fix these, if so)
Some of the non-controversial systems could be converted to use VisualizerSystem - I changed this when clearly appropriate, but some systems seemed to have a few responsibilities.
For a clean build of Content.Client, this reduces the warning count from 370 to 282.

Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog

:cl:

Most implementations of VisualizerSystem don't call the base class in OnAppearanceChange - seems like they ought to? (I'm happy to go though and fix these, if so)

this shouldnt be necessary, the base impl is just empty

Please split this pr up or it has a high chance of sitting in review hell.

Yeah, agree, it's getting pretty unwieldy. I'd really like to clean up the compiler warnings, though. Does it sound reasonable if I revert all the changes except those in https://github.com/space-wizards/space-station-14/pull/13357/commits/b2dac14c2f1949b06c2e3c985219b0a93e3a68ec and https://github.com/space-wizards/space-station-14/pull/13357/commits/a0f18e35473bb1898c237d4474d75a1f18da4969 (i.e., the uncontroversial "straightforward" changes) and I'll make individual PRs for the recycler, stack, and disposal visualizers?

Gonna abandon this and recreate smaller PRs.


typo: corrected

emergered-->emerged

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

that typo really needs to be edited!


Add Metadata SSZ container

See: the NIF's README and this PR
MetaData
(
  seq_number: uint64
  attnets: Bitvector[ATTESTATION_SUBNET_COUNT]
  syncnets: Bitvector[SYNC_COMMITTEE_SUBNET_COUNT]
)

Hi, can I solve this issue?

Sure! Go ahead!

Hi! I wanted to ask -

Should I make the Bitvectors of type U64 or declare new custom types of ATTESTATION_SUBNET_COUNT and SYNC_COMMITTEE_SUBNET_COUNT.
What should I perform in the test? Is there any reference I can take? I tried to find it in the lodestar but couldn't find any test related to it.

If the constants are in the configs in ssz_types/config.rs, we should make the container receive it as a generic <C: Config>. If not, a new type is fine.
For the test, we should serialize and check the output is correct. The same for deserialization. This is mostly meant as a smoke test, since errors only appear at runtime.


lxd in Debian Testing - missing CGroup memory and pids controller

I wanted to try lxd on my Debian Testing server, but after building it and starting lxd I get the following output:

WARN[04-06|20:24:39] AppArmor support has been disabled because of lack of kernel support
WARN[04-06|20:24:39] Couldn't find the CGroup memory controller, memory limits will be ignored.
WARN[04-06|20:24:39] CGroup memory swap accounting is disabled, swap limits will be ignored.

I suppose I don't care or know much about the AppArmor part, but the memory part would be nice to take care of. Problem is, I don't know how or why it is missing.
I read the very similar report #1554 but I don't think the solution applies to me because I have most of the cgroup mounts already mounted by systemd:

cgroup on /sys/fs/cgroup/systemd type cgroup (rw,nosuid,nodev,noexec,relatime,xattr,release_agent=/lib/systemd/systemd-cgroups-agent,name=systemd)
cgroup on /sys/fs/cgroup/devices type cgroup (rw,nosuid,nodev,noexec,relatime,devices)
cgroup on /sys/fs/cgroup/net_cls,net_prio type cgroup (rw,nosuid,nodev,noexec,relatime,net_cls,net_prio)
cgroup on /sys/fs/cgroup/pids type cgroup (rw,nosuid,nodev,noexec,relatime,pids,release_agent=/run/cgmanager/agents/cgm-release-agent.pids)
cgroup on /sys/fs/cgroup/blkio type cgroup (rw,nosuid,nodev,noexec,relatime,blkio)
cgroup on /sys/fs/cgroup/cpu,cpuacct type cgroup (rw,nosuid,nodev,noexec,relatime,cpu,cpuacct)
cgroup on /sys/fs/cgroup/cpuset type cgroup (rw,nosuid,nodev,noexec,relatime,cpuset,clone_children)
cgroup on /sys/fs/cgroup/freezer type cgroup (rw,nosuid,nodev,noexec,relatime,freezer)
cgroup on /sys/fs/cgroup/perf_event type cgroup (rw,nosuid,nodev,noexec,relatime,perf_event,release_agent=/run/cgmanager/agents/cgm-release-agent.perf_event)

Curiously, nothing about memory there. When I look at the dmesg output I find this:

...
[    0.019272] Initializing cgroup subsys io
[    0.019279] Initializing cgroup subsys memory
[    0.019399] Disabling memory control group subsystem
[    0.019401] Initializing cgroup subsys devices
[    0.019405] Initializing cgroup subsys freezer
...

I'm trying this in a recent-as-of-today Debian Testing machine using a 4.4.0-1-amd64 kernel, systemd 229, lxd 2.0.0.rc8.
Just tell me if you need any other information. Presumably there is something I have to tell systemd to stop disabling the memory control.

Debian requires a custom boot parameter to have the memory cgroup enabled.

cgroup_enable=memory must be on your kernel command line apparently.
If you also want swap accounting, you'll need to also add: swapaccount=1

Note that this is purely a Linux distribution problem, distributions have different kernel configurations, some disabling things entirely, some requiring a boot flag. LXD detects what you actually have at run time, turning things on is something that you need to do yourself or convince your distribution to do it for you.

Thank you for the quick response! I will have to read more about the implications of enabling it and why Debian leaves it out by default.

what about pids controller? can't find info about it


Use __builtin_unreachable in HAL_ASSERT no-assert mode

This fixes a compile error when building with esp-clang:
esp-idf/components/hal/esp32/include/hal/mmu_ll.h:252:9: error: variable 'mmu_value' is used uninitialized whenever switch default is taken [-Werror,-Wsometimes-uninitialized]
        default:
        ^~~~~~~
esp-idf/components/hal/esp32/include/hal/mmu_ll.h:256:12: note: uninitialized use occurs here
    return mmu_value;
           ^~~~~~~~~
esp-idf/components/hal/esp32/include/hal/mmu_ll.h:242:23: note: initialize the variable 'mmu_value' to silence this warning
    uint32_t mmu_value;
                      ^
                       = 0

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

sha=c3b7af6c3def8b0d5014c2389f5838b66705ee11

Hey sorry I didn't realise there was a CLA required. Regarding the patch, take it or leave it, but I'm just not that interested in reviewing a legal contract for this


Hierarchy view

💬 Description
This is quite a beefy PR but for good reason. Nothing complex but more of a shift of thinking for us as a team.
gather-content-ui has always been a component library only for us internally but we're experimenting on building larger UIs to illustrate how we could piece together entire chunks of UIs for the app rather than only doing that in the app.
There are many benefits;

no business logic or speed issues (Storybook is our faster env for development)
we can isolate UI challenge and tackle them in the correct place
we can do design reviews in a faster env
we can hook into addons like Knobs to allow people to customise their experience for testing
and much more!

I have also included some much-needed packages to allow us to build faster e.g.;

uuid for generating uuids for loop keps
faker for generating fake content

I have also started to move library-based stories that I have touched into their component directories so things can start living in a single area rather than scaling the entire codebase to find what you are looking for 👍
🚪 Start Points
I would check the "web app" based story and take it from there. These stories are just larger formats of the original library-based stories, they're a little more complicated but only because they're larger (IMO).
You can make these even simpler if you don't include Knobs and dynamic settings to be applied but you then lose the power.
✅ Checklist

[x] Tests written
[x] Browser tested
[ ] Added to documentation
[x] Added to storybook

 Create  in gather UI

@kyleharper Loving the new concept, I think building larger UI in gather ui is 💯
This PR also seems to be building some specific UI (from the title), but there's no detail of it in the description or the attached Trello cards. If this is the case, could we see the designs/UI in action? That would maximise the "context transfer" efficiency.

@altaudio I think grabbing me and us having a chat is best. I don't agree with adding too much context to a public repo or Trello cards that only we can access.
Some overall context will help though so ping me. I'd also recommend just reviewing the code and looking for smells at the point.

@AmeeMorris @altaudio find design attached. I'll be merging this morning, please review by then 👍

@altaudio @DavidHollins6 feedback applied, please approve 👍


Mask passwords when written as json

Signed-off-by: Gary Brown<EMAIL_ADDRESS>Which problem is this PR solving?
Ensure that passwords are not accidentally written out as json.
Short description of the changes
Don't serialize the password fields as json.

Feels like there's got to be a more reliable way.


Explore japicmp-gradle-plugin as a Binary Compatibility checker?

https://github.com/melix/japicmp-gradle-plugin

I've tested out japicmp by running it manually and while it is a useful tool for manual inspection, it has what I believe to be false positives that make automated checks difficult. The maven plugin is also quite limited -- what I'd like is something that could fetch older versions of the artifact from a maven repository automatically.
For anyone wondering what this looks like, I've run a report comparing 3.6.1 with 3.7 (as of 26fe47d473b33e5792250cb29138778f8dee489e) -- it's available at https://files.stellardrift.ca/mc/configurate-core-changes-3.6.1-3.7.html
I think the idea is still useful, but as long as it's possible to do manual reports i don't think it'll be super high priority.


Do not merge

Add page size to Python code gen.

@jmuk
Could you take a look at this? If it looks OK, I will make the corresponding change in the Ruby codegen as well.

FYI @tseaver @tbetbetbe
This addresses the concern mentioned in googleapis/gax-python#94 and recorded as issue #110

This change conflicts with #153. I will finish this up once that change is merged.

@jmuk updated for other languages, PTAL
@garrettjonesgoogle This change adds page_size into optional parameters, which affects PHP. I've more-or-less tried to do the same thing to PHP codegen as to Python/Ruby/NodeJS, but could you check that this change makes sense in the context of PHP GAX?

LGTM

@garrettjonesgoogle Should I wait for your LGTM before I merge this?

LGTM

@geigerj Sorry I missed seeing the issue earlier, but wouldn't it make more sense to have the page_size be passed as a member of CallOptions (like page_token), rather than as a separate parameter?

My original thinking was that

page_token belongs in CallOptions because we've given it additional meaning beyond its use as field in the proto request message, in that page_token is a toggle for the response type being iterated over.
in contrast, page_size, as a call parameter, is a simple wrapper for a proto field, no additional semantics.
We'd have to consider that if both page_token and page_size are in CallOptions, do both of them act as toggles? Or just one of them? Or neither, with some other option acting being a separate toggle?

I'm now thinking that it's possible to do better than our current set-up; from #237, it sounds like @michaelbausor will be redesigning the way we specify the page streaming options to be more consistent across the vkit languages, which may involve moving where page_size/page_token are specified.


Helm values not parsed correctly

We generate random tags in our ci/cd pipeline. Today we had a problem that an image was not deployable. When I looked at the tag, I noticed that a part was missing. I did some tests and found that a certain combination of characters leads to problems. We can't explain it yet, but it seems more like a bug.
How to reproduce the problem:
Chart.yaml (created with helm create test-chart):
name: test-chart
description: A Helm chart for Kubernetes
type: application
version: 0.1.0
appVersion: 1.16.0

values.yaml:
var_a: 72044e0
var_b: "72044e0"
var_c: 72044e011
var_d: "72044e011"
var_e: 72044e07d2
var_f: "72044e07d2"
var_g: 82h2532

templates/test.yaml:
# No quotes in values.yaml
var_a: {{ .Values.var_a }}
# Quotes
var_b: {{ .Values.var_b }}

# No quotes in values.yaml
var_c: {{ .Values.var_c }}
# Quotes
var_d: {{ .Values.var_d }}

# No quotes in values.yaml
var_e: {{ .Values.var_e }}
# Quotes
var_f: {{ .Values.var_f }}

# No quotes in values.yaml
var_g: {{ .Values.var_g }}

Templating:
helm template . -f values.yaml
---
# Source: test-chart/templates/test.yaml
# No quotes in values.yaml
var_a: 72044
# Quotes
var_b: 72044e0

# No quotes in values.yaml
var_c: 7.2044e+15
# Quotes
var_d: 72044e011

# No quotes in values.yaml
var_e: 72044e07d2
# Quotes
var_f: 72044e07d2

# No quotes in values.yaml
var_g: 82h2532

As you can see in the example, an unquoted 72044e0 is templated to 72044, 72044e011 towards 7.2044e+15
Output of helm version:
version.BuildInfo{Version:"v3.4.2", GitCommit:"23dd3af5e19a02d4f4baa5b2f242645a1a3af629", GitTreeState:"clean", GoVersion:"go1.14.13"}

Output of kubectl version: -
Cloud Provider/Platform (AKS, GKE, Minikube etc.):  -

Unquoted, values are parsed into their native YAML types. The YAML parser is interpreting “e0” and “e011” as scientific notation. This is intentional behaviour from the YAML spec’s definition. This is also the same reason why “ON” and “NO” are treated as Boolean values.
to fix this, wrap your values in quotes. It will be interpreted as a string.

Hi @bacongobbler Thank you for your explanation. Of course this makes sense. We will adjust our templates.


Reload config endpoint - /-/reload

It would be great to have the possibility to reload the configuration file, just like we can do with prometheus:
curl -X POST http://localhost:8080/-/reload
I see we have some methods, but it's not exposed:
https://github.com/conprof/conprof/blob/master/scrape/manager.go#L84

Agreed! If someone wants to pick this up that would be amazing!

I can work on it if @syepes doesn't want!

@geobeau I had a rapid look last night but could not figure out how to add the hook, if your more familiar with the code base I'll also be interested in seeing how you implement it. :-)

I made #71 which is a naive implementation. @brancz @syepes any advices on how to make it more elegant?

I merged #71, maybe @syepes can try out the image that will be built from master and we close this issue once tested? :)

I'll give this a try with your setup

@geobeau | @brancz
I just have given this a test drive and there is an issue.
The reloading gets triggered but it's reloading the current (old) config that was previously loaded on the struct, I think that before running the actual reload we need to call ApplyConfig and then updateTsets with the necessary parameters.

@geobeau do you think you could have a look at that?

Yes, sorry for the issue

Made another pull request. It looks like it's working fine now

Merged #70, @syepes can you retest with the latest build?

@geobeau  | @brancz
Works like a charm! thanks


Updating Wisconsin rules:

Added negative lookahead to green bay for gamblers (hockey team) and to milwaukee for bucks (basketball)

Added goodregex matches for mke, scott walker, and gov(\.|ernor)? walker

Added ~46 subreddits to the getfromthese list (multi of all added subreddits here)

any subreddits listed in the code need to be in lowercase. otherwise looks good.


Deploy to Mode

Chain Name
Mode Mainnet
Chain ID
34443
RPC URL
https://rpc.mode.network
Block Explorer URL
https://explorer.mode.network
Deployment Funds
No

I will be funding the deployment address, just waiting for funds to arrive

0.015 ETH sent to 0x05f32B3cC3888453ff71B01135B34FF8e41263F2 - Tx info

Done, thanks!


chore(repo): Update CODEOWNERS to require approval for versioning PRs

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[x] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[x] build/tooling/chore

Description

[ ] npm test runs as expected.
[ ] npm run build runs as expected.

In order to have more granular access control over who can trigger stable releases of our packages, we are adding a CODEOWNERS rule targeting the CHANGELOG.md files in each package. These files are only changed by the automated "Version Packages" PR that is generated by Changesets, so it should be a reasonable way to control access to publishing.

fixes JS-697

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Refs #22936 -- Moved more of Field.get_db_prep_lookup() to lookups.

Another increment bit of https://code.djangoproject.com/ticket/22936.

Will reopen if/when I can solve the test failures.


Add a few example debug transports

Add a few example debug transports to make it easier to work with the debug protocol formatting:

[ ] Debug transport which will parse individual dvalues coming from Duktape and provide them to a user callback in parsed form. Similarly, accept dvalues and write them to Duktape in binary form. Dvalues can be represented with a C struct containing a type tag and a union of values.
[ ] Debug transport which will parse full debug messages (ending in an EOM) and provide them to user callback. Similarly, accept full debug messages and write them to Duktape in binary form. Debug messages can be represented as an array of individual dvalues (which can be tagged structs).
[ ] Debug transport which parses full debug messages and provides them to user in the JSON mapping form. Similarly, accept JSON mapped inbound messages and write them to Duktape in binary form.

The first two transports would be very useful for people who want to decode the debug protocol right on the target.

Another 1.3.0 milestone... 1.3 is going to be a huge upgrade at this rate. :smile:

I'm not 100% strict about milestone targeting though - I used 1.3.0 for this because I have a few (uncommitted) transport tests which I can probably use to write the first two examples quite quickly.
The JSON transport example won't make it to 1.3.0 probably unless it'd depend on an external library. Or perhaps it could use an entirely separate Duktape instance for JSON parsing and stringifying only.

Here's an example transport with dvalue encoding and decoding (very early draft, missing stuff, hasn't been tested well):

https://github.com/svaarala/duktape/compare/example-debug-dvalue-parser

With this the main program which would implement a local debugger, would look something like:

https://github.com/svaarala/duktape/blob/cf0feb743fe45c3d3153a89a7fc4323cd073468e/examples/debug-trans-dvalue/test.c

which should be a little bit easier than dealing with dvalues.

Hm, nice, the only thing I don't like is the need to allocate and free dvalues.  Each dvalue sent is 3 lines (create, send, free), which could get ugly.  Since you have separate make_tag functions anyway, why couldn't it be simplified to something like this below:
duk_trans_dvalue_send_tag(ctx, DUK_DVALUE_REQ);
duk_trans_dvalue_send_tag_int(ctx, DUK_DVALUE_INTEGER, 0x15);  /* StepOver */
duk_trans_dvalue_send_tag(ctx, DUK_DVALUE_EOM);

Chances are you're not going to do much else with the allocated dvalues after sending them, besides freeing them, so why not simplify the API?

The dvalues need to be allocated for the receive direction (they may need to be kept until the entire message has been received so they need a copy of the input data) so I used them also for the send direction. I guess the dvalues could point to the temporary buffer and the "release" it when done. Not sure if that'd be easier to follow.
But adding those wrappers for sending dvalues more easily would be easy, I'll add them.

Added a few wrappers: https://github.com/svaarala/duktape/commit/433fae49d2255232fe6a12abee75d5c4f352f7ac
The sending code now looks like:
duk_trans_dvalue_send_req(ctx);
duk_trans_dvalue_send_integer(ctx, 0x15);  /* StepOver */
duk_trans_dvalue_send_eom(ctx);

Ah, very nice.  That's even better naming than mine. :)

Hm, maybe send_req() could take a command ID and avoid the extra integer send?

Perhaps add duk_trans_dvalue_send_req_cmd() so that it's somewhat visible that it's actually sending two dvalues? It'd be nice if there was a 1:1 mapping for individual dvalues so duk_trans_dvalue_send_req() should IMO just send the REQ.
(I'll try to reduce the long prefix of the example later on; duk_trans_dvalue_xxx to duk_dtrans?)

Yeah, duk_dtrans_xxx Looks more concise for a public API.  Overlong function names make it seem like an internal API.
I'd be fine with a separate send_req_cmd.  I definitely understand the rationale for wanting a 1:1 mapping and I agree with it 100% (you want to have your foundation be as generic and stable as possible), but the public API should also represent everyday use. :)

This is just example code and not part of the public API so it'd be good if it was clear it's not a "normal" API call though.

Fixed endianness handling (dynamic detection for double endianness), improved coverage so that all except a few dvalue encode/decode code paths were tested (some bugs fixed). Renamed functions a bit, made consistency renames for the socket example transport. Added to dist and merged to master.


Vatumledor stat block: incorrect traits and damage on Mental Blast

Vatumledor (Prey for Death) is an ancient conspirator dragon, but his Mental Blast attack is incorrect compared to the generic ancient conspirator dragon statblock.
It should have the "mental" trait added, and the damage type should be mental, not bludgeoning.
Correct Statblock

Vatumledor's Current Statblock

I checked the actor -
When in humanoid form, the Conspirator Dragon's attacks all switch to bludgeoning, including the Mental Blast.


Update bitbar license from unknown to mit

Requested: https://github.com/matryer/bitbar/issues/9
Included: https://github.com/matryer/bitbar/commit/fff58a43eb1c1d081c8cb8996b98b38ecc2c406e

Thank you for the contribution. It was merged directly as a3186b7b3f753b76b0ada2f5158786c4a2b1d92f to keep commit history cleaner. Your contribution is still credited to you.


Doesn't the mssql-jdbc-12.2.0 version support TLS v1, v1.1?

I changed the mssql-jdbc version from 9.4.1 to 12.2.0.
However, when I tried to connect to MSSQL from the client, the following error message occurred.
*** error message**
"tlsv1 was negotiated. please update server and client to use tlsv1.2 at minimum"
Upon checking, the mssql version on the customer's server did not support TLS 1.2.
I recommended updating it, but they said they couldn't do it at the moment for other reasons.
I wonder if mssql jdbc version 12.2.0 does not support TLS v1, v1.1.

The driver supports TLSv1 and TLSv1.1. Where is the server located? If it's on Azure, I recall Azure only allowing TLSv1.2. Also, it's possible that the JDK might have TLSv1.1 disabled. So, if it's failing on an older TLS version, it's likely a server/env setup issue.
In our docs: https://learn.microsoft.com/en-us/sql/connect/jdbc/setting-the-connection-properties?view=sql-server-ver16, if you look up sslProtocol it lists out the supported TLS versions and TLSv1.1 is on there.

The server is installed on secure equipment, not a CSP.
Maybe adding the following options to the driver url could have an impact?
[...;encrypt=true;trustServerCertificate=true]

.

You'll need trustServerCertificate=false. If it's true then the certificate isn't validated and is unsecure. For your use, your connection string should be like encrypt=true;trustServerCertificate=false;sslProtocol=TLSv1.1. What's your SQL Server version (the output of SELECT @@VERSION)? If the SQL Server is out of date, that could have an impact.

I'm not sure if changing trustServerCertificate=false will work.
If we set it to true, wouldn't that be one less step, since it would just pass without verification?
*** SQL Server version**
Not exactly, but... SQL Server 2008 does not support TLSv1.2 or higher.
But if the mssql jdbc 12.2 version supports TLSv1 TLSv1.1, then the SQL Server version shouldn't matter, right?
As you said, it could be a JDK or some other environment issue...

I checked, and it seems to be because tomcat has sslEnabledProtocols="TLSv1.2+TLSv1.3" in its server.xml.
Thank you for your response. :)


[PE-D][Tester A] Link in DG sends you to localhost

This link links to localhost rather than the online setting up page

Labels: type.DocumentationBug severity.VeryLow
original: FriedCabbageSalad/ped#25

Thanks for highlighting. We have now fixed the issue.


Extend and improve RSS feed

Expose IPT UUID in channel. This will help differentiate between multiple registered IPTs at the same URL
Expose feed's own address in channel. This will make the feed easier to cache, etc.
Fix elements having email addresses. The format used is currently invalid.

An example feed with all changes proposed above is attached. Please use https://validator.w3.org/feed/ to ensure feed is valid.
feed.xml.zip

Also: make sure the RSS is refreshed on every republication (e.g. by using version number). From my experience, sometimes a republication triggers an update, sometimes it does not (not tested). I think it has something to do with what items were changed, e.g. if title was updated -> triggers an update (again not tested).

Further verification of fix needed using https://validator.w3.org/feed/

Issue verified - feed is valid according to W3C Feed Validation Service.


System Freeze while installation

My system freeze while I am executing make -j command in the installation commands. I have no issue in executing rest of the commands

Please remove -j or specific the thread number