Support popup appears mid tutorials

Describe the Issue
Every few lessons I get the Become a Support popup. I don't mind that yall ask for donations but every 2-5 lessons is really annoying. It would be great if you could make it so that it only pops up once you complete an entire module like completing the Cat Photo App module or the Cafe Menu module rather than it popping up every 3-5 lessons within the 69 lessons of the Cat Photo App module. It would also be nice for those of us who can't afford to donate to have an option underneath the ask me later to set it the popup to don't ask me again. If I had the means to support I would.
Affected Page
https://www.freecodecamp.org/learn/2022/responsive-web-design/learn-basic-css-by-building-a-cafe-menu/step-7
Steps to Reproduce

Go through the Cafe Menu module
Continue through the lessons
You'll see the popup every few lessons

Expected behavior
Show the popup at the end of the the entire module and give me the option to not show this popup again and if clicked save that setting to my account. You can even add a setting in my account to re-enabled the popup. If you don't want to add the link to disable the popup then at least fix it so that the popup appears at the end of the module.
Screenshots

System

Device: Custom Build Desktop Computer
OS: Windows 10
Browser: Chrome
Version: 127.0.6533.89

Additional context
No response

Thanks for your input @codewithtyler 👍
We are continuously adjusting our methods to try and get more supporters without it turning people away - so this is constantly changing.
Every 2-5 lessons does seem like it might be a bit much. Just floating an idea - what if we had a second modal that was shorter/faster to show during the middle of the project instead of this one. Then show this one at the end of projects.

I think one at the halfway point of the module and one at the end of the module would be way better than what it is now.

Thank you for reporting this. It should be every 20. I am investigating.

I was wondering if you refresh your page every few challenges?

I have the following extensions installed:

Bitwarden
Dark Reader
UBlock Origin
vidIQ Vision for YouTube
IPX - Influencer Profits Extension
Global Twitch Emotes
Keepa
Anori

@huyenltnguyen, thanks for looking into it.
That is all true, but the logic changes when a user is shown the modal.
https://github.com/freeCodeCamp/freeCodeCamp/blob/6b9979ae50cd7202d85beab843729d9b3d2322fe/client/src/redux/selectors.js#L56-L60
So the current logic in summary is the following:
If a user has not completed 10 challenges in total, show the modal after 10th challenge and every 20 after that.
If a user with more then 10 completed challenges, show the modal after 3 challenges and every 20 after that.
Let me know if you see any inconsistencies in the logic.

@codewithtyler, appreciate it.
Could you confirm that you are having the same issue when using your browser in incognito mode where there are no active extensions?
Also, what are the ways you close/skip the donation modal?

Since the length of the video is 20 seconds, we do want to show the modal if the modal was displayed less than 20 seconds ago. Here is the related pr for more context: https://github.com/freeCodeCamp/freeCodeCamp/pull/54817

Ah, I see the logic. It's so you can't simply reload the page to skip? It might help to explain that in the saga, since it's not obvious from the code.

If a user has not completed 10 challenges in total, show the modal after 10th challenge and every 20 after that.
If a user with more then 10 completed challenges, show the modal after 3 challenges and every 20 after that.

I think this is what I'm seeing. I think my confusion is in the fact the code @huyenltnguyen showed above mentions that it does the check per session. Seeing as I'm spending multiple days in a row going through the modules it may seems like it's a bit much. I do like @moT01's suggestion of having the modal show in the middle and again at the end of each module. This way you still suggest the donation but it comes across as less aggressive to people.

I've also noticed the donation box appear at inconsistent times. I tried to stay vigilant and take screenshots each time but i eventually forgot to keep doing it for my proof. I have some screenshots though (I started taking screenshots at step 9, and then again at 29 and 49 which seems consistent with every 20 steps except that I started with step 9, not 3?? not sure how that happened, but I definitely did see the modal at step 3 too, it is just that by the time I decided to try to screenshot it, I was already at step 9 then). This was the js platformer project btw if that makes any diff. Unfortunately I didn't keep up the screenshots after step 49. Sorry about that!) My theory is that because I switch between my laptop and my cell-phone when working on challenges, that something about that switch caused the 'jump'.

@hbar1st, if you close browser/tab or refresh your page, the logic might restart.

Oh okay. Are you aware of the performance issue that was being discussed (the editor would perform slowly on occasion)? The workaround for this is to close the tab and reopen it. I’ve been doing this on occasion to make sure I get the fastest performance. This would then explain why it would seem that the donation popup shows up every few steps.

Thanks for letting me know. I will try to keep the logic somewhere else to make sure it does not interfere with refreshes.

Performance issues aside. I think I identified my issues above based on @ahmaxed's comment. I'm curious to hear what everyone thinks about @moT01's suggestion of having the modal appear twice: once midway through the module and one at the end of the module. This in my opinion would mitigate the issue of the modal feeling annoying at times.

I will make sure to AB test Tom's idea to see how it effects user behaviour.

We would need to move the completionCount state from the redux store to sessionStorage so it will not be effected by refreshes.

@hbar1st, I am wondering if you still experiencing the slow down. It seems to have been resolved.
https://github.com/freeCodeCamp/freeCodeCamp/issues/55745
Could you do a hard refresh and see if the issue have been resolved?

To clarify my suggestion earlier - I meant that we could have a shorter modal to show in the middle of projects - not just once in the middle of the project, but many times (if needed) in the middle of the project. Projects have great variability in length, so I think we still need to show it more than once in places. e.g. some projects are 20 steps long, some are almost 200.

I looked around a little and found a few issues related to the editor slowing down (there may be more):
https://github.com/freeCodeCamp/freeCodeCamp/issues/55017
https://github.com/freeCodeCamp/freeCodeCamp/issues/54736
https://github.com/freeCodeCamp/freeCodeCamp/issues/54716
Looks like a number of steps have been taken to improve things.

@ahmaxed unfortunately I am not working on any curriculum at the moment but I will keep an eye out if I return to it.

Thanks for the suggestion, I will add that to the AB test queue.

You're welcome and thank you to being open to my ideas.


merge withids updates

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

BingAds/scripts/concepts/ids.md
:white_check_mark:Succeeded

BingAds/scripts/reference/AdGroupSelector.md
:white_check_mark:Succeeded

BingAds/scripts/reference/BingAdsAccountSelector.md
:white_check_mark:Succeeded

BingAds/scripts/reference/BudgetSelector.md
:white_check_mark:Succeeded

BingAds/scripts/reference/CampaignSelector.md
:white_check_mark:Succeeded

BingAds/scripts/reference/KeywordSelector.md
:white_check_mark:Succeeded

BingAds/scripts/reference/NegativeKeywordListSelector.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add OSS scripts for checking lint and formatting

These exist upstream and bad things happen on merge when misaligned.

This should mostly match what we are expecting (as it's close to head clang-format):
https://github.com/google/iree/blob/benvanik-ci/.github/workflows/build_and_test.yml#L17-L30
That's just a check though - need to do basically the same thing with -i to edit in place.


feat: regenerate with openapi-generator 5.4.0

This PR regenerates the library with openapi-generator version 5.4.0. It also includes some upstream fixes to type definitions from the Cloudsmith API.
Our Terraform provider uses this but is pinned to an older version so should be safe to update here.

\o/ very excited to see this since I have been prepping some work that will want to leverage this API! 🎉 💜


Add PowerShell Gallery to recommended training and reading resource

PR Summary

PR Context

PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Change is not breaking
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

User-facing changes

[x] Not Applicable
OR
[ ] Documentation needed

[ ] Issue filed:

Testing - New and feature

[x] N/A or can only be tested interactively
OR
[ ] Make sure you've added a new test if existing tests do not effectively test the code changed

[ ] Add [feature] to your commit messages if the change is significant or affects feature tests

I believe PowerShell Gallery is not training site.

I use it a lot to understand modules and It´s a way to improve the code formatting and syntax.

My comment is not blocking.

I know it, only expose my reason to propose to add that resource to the list. Your opinion is a good point of view. I think that PowerShell Gallery should be part of the resources (maybe not inside the learning or reading). Can we analyze create a new section? It's too much, isn't it?

@vmsilvamolina We should move all PowerShell docs to PowerShell-Docs repo. In the repo we need to leave only docs related to dev process.

I agree the PSGallery is a great resource, but it doesn't fit under the training category and would be misleading.


Improve ease of use of api client in no_std

After solving https://github.com/scs/substrate-api-client/issues/279, with a  no_std compatible Api, one could use theoretically use the api-client with most features inside a no_std environment. But practically, a lot of workarounds are needed, because many types from substrate (Header, Block ,.. .) do not implement Serialize / Deserialize in no_std.
Improvement Ideas:

If parity allows it: https://github.com/paritytech/substrate/issues/12994
Provide most important types (Header, Block,..) with (de)serialization implementations, just like in https://github.com/scs/substrate-api-client/pull/377
Do only enforce Serialization for types that are actually requested (for now, at least the full FrameSystemConfig is enforced, no matter what is actually requested via RPC) (not sure if that is possible, would need to be evaluated)

Green light from parity, so lets try to go with 1.

PR on parity side: https://github.com/paritytech/substrate/pull/13027

Marked as blocked. No response from parity for two weeks, even after asking further questions. Maybe we'll have to go for a different solution.


How do you exclude documents that contain a specific attribute?

Is there a way to configure the extension only to include documents where 'isAvailableForPurchase' is true, and ensure that documents are removed from the index if this value changes to false?

At this time, its not available configure this to include or exclude.  For now, you can use Algolia Rules to add a filter to only return documents with 'isAvailableForPurchase' is true.

At this time, its not available configure this to include or exclude. For now, you can use Algolia Rules to add a filter to only return documents with 'isAvailableForPurchase' is true.

ok, thanks


Installing Method without XCode

I find a way to install this driver without xcode.
1- Download app and copy it application folder.
2- Click activate and close app(Repeat it few times until it wants a permission)
3- Go settings/Security and allow rog hid.
4- Reopen app and click activate one more time.
5- Restart computer.
-In Catalina and Bigsur Backlight and Keyboard backlight controls working well but capslock light is not working. Device 0b05:1866
Bug: Sometimes screen brightness reduces itself to zero.

Thanks for confirming that pre-signed app works for other users with SIP disabled.
About CAPS Lock key, does the text capitalization work? Have you tried pressing multiple times? Actually, for some reason all ROG HID keyboards with an CAPS lock led suffer from this problem. I managed to fix it on 0b05:1869.
Screen brightness reduces itself to zero when you press and hold the decrease brightness key or randomly (even when you don’t press anything).
For other Fn key features, please have a look at the README. They’ll be implemented in a future release. DriverKit has zero documentation as of now -_-

-Screen brightness reduces itself to zero when you press and hold the decrease brightness key or randomly
--In my case it happens randomly or I didnt see a pattern.
-Text capitalization works I have capslock led as well but led is not working even with that kext

If it doesn’t occur when pressing a key. I don’t think it’s related to ROG-HID. As the driver only dispatches events to system on keypress. Still I have a hunch that it might be related to #2
Did CAPS Lock LED ever work for you without the driver? We can always set caps lock led state by calling ‘_hid_interface->SetLED(0x2,0)’ where 0 means off and 1 means on. But it doesn’t actually toggle the CAPS Lock state.

@valinor61 Your weird behavior of brightness keys must be fixed now. Please try the latest release. To fix LED, I need to know if the LED ever actually worked?

Yes it fixed now. It was M key I tested now working without issue. Capslock led is not working with v1.1 and it has never worked in osx.

Ok great! Now for CAPS Lock LED, If it has never worked before, I would need to have access to hardware in order to debug it. So, unfortunately, that's not possible for me to fix as of now.
The fix that is there in this driver for CAPS Lock LED doesn't fix the LED itself but the erratic behavior of it. Meaning, LED works without this driver too, just not reliably.
Closing this issue.


copytranslator: Add version 9.0.0

CopyTranslator

Application without proper homepage and documentation page in English cannot be accepted into official bucket.

Changed the homepage to README in English already. Is it detailed enough or I should contact the author for more translated documents?


Error when I compile with rebar3

When I use rebar3 to compile jsonx,got error like this:
=ERROR REPORT==== 19-Apr-2017::11:36:37 ===
Error in process <0.207.0> with exit value: {{badmatch,{error,{load_failed,"Failed to load NIF library: '/home/dasudian/Proj/swdportal/deps/jsonx/_build/test/lib/jsonx/priv/jsonx.so: cannot open shared object file: No such file or directory'"}}},[{jsonx...

Everything is ok when I compile with rebar...
Is there any advice?Thanks

rebar3 does not build ports same way as previous version did.
Add following to jsonx's rebar.config to enable old behaviour via plugin:
{plugins, [pc]}.
{provider_hooks, [{pre, [{compile, {pc, compile}}, {clean, {pc, clean}}]}]}.


Keras EarlyStopping callback on val_auc running mysteriously

System information

OS : Windows 10
Python version : 3.6.5
Tensorflow : 2.3.0

Simple DL GridsearchCV modelling using Keras
epochs = [1, 6, 11, 16, 21, 26, 31, 36, 41, 46]
batch_size = [2,4]

 stopper = EarlyStopping(monitor='val_auc', patience= 10, mode = 'max', min_delta = 1, restore_best_weights=True)
 save_mod = ModelCheckpoint(r'C:\......................\best_model.h5', monitor='val_acc', mode='max', save_best_only=True, save_freq
 = 'epoch')

 param_grid = dict(epochs = epochs, batch_size = batch_size)

 def create_classify_model(learn_rate = 0.01, momentum = 0):
            # create model
            network = Sequential()
            #input layer and 1st hidden layer
            network.add(Dense(units = data_seg.x_tr.shape[1], activation="relu", input_shape =
            (data_seg.x_tr.shape[1],)))

            #dropout layer for input layer
            network.add(Dropout(0.2, input_shape = (data_seg.x_tr.shape[1],)))

            #second hidden layer
            network.add(Dense(units = math.trunc(data_seg.x_tr.shape[1]*0.8), activation = "relu"))

            #dropout layer for hidden layer
            network.add(Dropout(0.5))

            #output layer
            network.add(Dense(units = len(np.unique(data_seg.y_tr)), activation = "softmax"))

            optimizer = SGD(lr=learn_rate, momentum=momentum)

            #compiling neural network
            network.compile(loss = "categorical_crossentropy", optimizer = optimizer, metrics =
['acc',auc_metric()])

            return network

neural_network = KerasClassifier(build_fn=create_classify_model, workers = -1, use_multiprocessing =
True, verbose=2)
grid = GridSearchCV(estimator=neural_network, param_grid=param_grid)

fit_params = dict(callbacks=[stopper, save_mod], validation_split = 0.05)

grid_model = grid.fit(data_seg.x_tr, data_seg.y_tr, **fit_params)

Output
471/471 - 1s - loss: 0.7568 - acc: 0.6019 - auc: 0.6357 - val_loss: 0.4909 - val_acc: 0.7600 -  val_auc: 0.8676 125/125 - 0s - loss: 0.5264 - acc: 0.7751 - auc: 0.8459 WARNING:tensorflow:Early stopping conditioned on metric val_aucwhich is not available. Available  metrics are: loss,acc,auc_1,val_loss,val_acc,val_auc_1 472/472 - 1s - loss: 0.7242 - acc: 0.6288 - auc_1: 0.6494 - val_loss: 0.5680 - val_acc: 0.7000 -  val_auc_1: 0.7896 124/124 - 0s - loss: 0.6316 - acc: 0.6250 - auc_1: 0.6942 WARNING:tensorflow:Early stopping conditioned on metricval_aucwhich is not available. Available  metrics are: loss,acc,auc_2,val_loss,val_acc,val_auc_2 472/472 - 1s - loss: 0.7193 - acc: 0.6182 - auc_2: 0.6563 - val_loss: 0.5279 - val_acc: 0.7400 -  val_auc_2: 0.8544 124/124 - 0s - loss: 0.5929 - acc: 0.7863 - auc_2: 0.7995 WARNING:tensorflow:Early stopping conditioned on metricval_aucwhich is not available. Available  metrics are: loss,acc,auc_3,val_loss,val_acc,val_auc_3 472/472 - 1s - loss: 0.7060 - acc: 0.6299 - auc_3: 0.6649 - val_loss: 0.5369 - val_acc: 0.8000 -  val_auc_3: 0.8400 124/124 - 0s - loss: 0.5564 - acc: 0.7661 - auc_3: 0.8305 WARNING:tensorflow:Early stopping conditioned on metricval_auc which is not available. Available  metrics are: loss,acc,auc_4,val_loss,val_acc,val_auc_4 472/472 - 1s - loss: 0.7258 - acc: 0.6161 - auc_4: 0.6398 - val_loss: 0.5676 - val_acc: 0.7400 -  val_auc_4: 0.7936
The ouput here, showcases that the val_auc metric which has been used to monitor EarlyStopping has been given an integer value, which increases with every epoch end I suppose. Hence, can someone help me understand about how can I monitor the val_auc in this case ?

@innovativeC,
On running the given code, I am facing an error stating NameError: name 'data_seg' is not defined.
In order to expedite the trouble-shooting process, could you please provide the complete code to reproduce the issue reported here and also the dataset you are using. Thanks!

@amahendrakar , data_seg.x_tr and data_seg.y_tr are actually the X and Y_true datasets used here. You can insert any classification dataset here, the result I am getting is constant across any classifcation dataset I have used whenever I've utilized auc as stopping metric.
PS - Can't share the complete code, since its proprietary. That being said, only preprocessing of the dataset was done prior to the code shared above..

@innovativeC,
In this case, could you please share a dummy dataset with similar shape and size, so that we can reproduce the issue on our end. Thanks!

@amahendrakar, Sure I am sharing the URL of the dataset I used, https://www.kaggle.com/vetrirah/av-healthcare2?select=train.csv. The data_seg.x_tr and data_seg.y_tr here would be the X and Y sets.

@innovativeC,
I am still facing the same error. The dataset you have provided does not seem to have X and Y sets. Please find the gist of it here.
Could you please provide a minimal working code sample, which we can use to reproduce the issue on our end? Thanks!

@amahendrakar  This is the link to the dataset https://drive.google.com/file/d/18ZOZ_tiRAXZGCdqaFzHyHYA0J44qytx-/view?usp=sharing. Also I have made some changes to the collab notebook which you had shared. You can find it here - https://colab.research.google.com/gist/innovativeC/7f9df6ab55653628074a3d898cf044c6/43645.ipynb

Was able to reproduce the issue with TF v2.3 and TF-nightly. Please find the gist of it here. Thanks!

@amahendrakar @ymodak Any insights on why this is happening ? Thanks!

Hi guys, any update on this bug ?

Just encountered the same problem when tuning keras model with nni. I observed that the val_auc[_number] comes from creating the same model multiple times in one script. The first time we create the model, val_auc has no suffix. And each time after the first creation, val_auc becomes val_auc_1, val_auc_2, and so on.

Just encountered the same problem when tuning keras model with nni. I observed that the val_auc[_number] comes from creating the same model multiple times in one script. The first time we create the model, val_auc has no suffix. And each time after the first creation, val_auc becomes val_auc_1, val_auc_2, and so on.

Same issue.  Here is a MWE
`import numpy as np
from tensorflow.keras.layers import Input, Dense
from tensorflow.keras.models import Model
import tensorflow as tf
def make_and_fit():
inp = Input(shape=(1,))
out = Dense(1, activation='sigmoid')(inp)
model = Model(inputs=inp, outputs=out)
auc = tf.keras.metrics.AUC()
model.compile(loss='binary_crossentropy',
metrics=[auc])
x = np.random.normal(size=10)
y = np.random.normal(size=10) > 0
xv = np.random.normal(size=10)
yv = np.random.normal(size=10) > 0
earlystopping = tf.keras.callbacks.EarlyStopping(monitor='val_auc',
patience=2)
model.fit(x=x,
y=y,
validation_data=(xv, yv),
epochs=2,
verbose=1,
callbacks=earlystopping)
for i in range(2):
make_and_fit()`

@innovativeC Is this still an issue for you? Can you please test with recent TF2.7 and tf-nightly?
@cranedroesch i tested your code by adding clear_session  as shown below. As Keras tracks its inputs/outputs, i think we cannot use same metric name if they are in memory. Clearing them from memory, results in better memory management also as listed here
for i in range(2):
  tf.keras.backend.clear_session()
  make_and_fit()

I have same issue too:
WARNING:tensorflow:Early stopping conditioned on metric auc which is not available. Available metrics are: loss,auc_1
WARNING:tensorflow:Early stopping conditioned on metric auc which is not available. Available metrics are: loss,auc_2
WARNING:tensorflow:Early stopping conditioned on metric auc which is not available. Available metrics are: loss,auc_3
and ...

UserWarning: Early stopping conditioned on metric val_auc which is not available. Available metrics are: auc_8,f1_score,loss


kernel modules compress mechanism

connects to resin-os/resin-beaglebone#18
@telphan @floion @petrosagg

SGTM

LGTM


Usage start error using az consumption usage list on Azure CLI version 2.57.0

Describe the bug
az consumption usage list --start-date 2021-10-01 --end-date 2021-11-01
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
The command failed with an unexpected error. Here is the traceback:
'usageStart'
Traceback (most recent call last):
File "/home/raimond/.local/lib/python3.8/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 664, in execute
raise ex
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 729, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 711, in _run_job
result = list(result)
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/aaz/_paging.py", line 87, in next
return next(self._page_iterator)
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/aaz/_paging.py", line 46, in next
curr_page, self._next_link = self._extract_result()
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/command_modules/consumption/custom.py", line 85, in _output
result = list([transform_usage_output(item) for item in result])
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/command_modules/consumption/custom.py", line 85, in
result = list([transform_usage_output(item) for item in result])
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/command_modules/consumption/custom.py", line 95, in transform_usage_output
usageStart = parser.parse(result['usageStart'])
KeyError: 'usageStart'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
Related command
az consumption usage list
Errors
The command failed with an unexpected error. Here is the traceback:
'usageStart'
Traceback (most recent call last):
File "/home/raimond/.local/lib/python3.8/site-packages/knack/cli.py", line 233, in invoke
cmd_result = self.invocation.execute(args)
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 664, in execute
raise ex
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 729, in _run_jobs_serially
results.append(self._run_job(expanded_arg, cmd_copy))
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/commands/init.py", line 711, in _run_job
result = list(result)
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/aaz/_paging.py", line 87, in next
return next(self._page_iterator)
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/core/aaz/_paging.py", line 46, in next
curr_page, self._next_link = self._extract_result()
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/command_modules/consumption/custom.py", line 85, in _output
result = list([transform_usage_output(item) for item in result])
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/command_modules/consumption/custom.py", line 85, in
result = list([transform_usage_output(item) for item in result])
File "/home/raimond/.local/lib/python3.8/site-packages/azure/cli/command_modules/consumption/custom.py", line 95, in transform_usage_output
usageStart = parser.parse(result['usageStart'])
KeyError: 'usageStart'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues
Issue script & Debug output
debug1.txt
Expected behavior
Result from az consumption list
Environment Summary
azure-cli                         2.57.0
core                              2.57.0
telemetry                          1.1.0
Extensions:
account                            0.2.5
aks-preview                      1.0.0b5
application-insights               1.2.0
costmanagement                     0.3.0
rdbms-connect                      1.0.4
resource-graph                     2.1.0
storage-preview                  1.0.0b1
virtual-wan                        0.3.0
Dependencies:
msal                              1.26.0
azure-mgmt-resource             23.1.0b2
Python location '/usr/bin/python3'
Extensions directory '/home/raimond/.azure/cliextensions'
Python (Linux) 3.8.10 (default, Nov 22 2023, 10:22:35)
[GCC 9.4.0]
Your CLI is up-to-date
Additional context
No response

Thank you for opening this issue, we will look into it.

Same issue here.
PS C:\> az consumption usage list --start-date 2024-01-01 --end-date 2024-02-01
This command is in preview and under development. Reference and support levels: https://aka.ms/CLI_refstatus
The command failed with an unexpected error. Here is the traceback:
'usageStart'
Traceback (most recent call last):
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 233, in invoke
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 664, in execute
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 729, in _run_jobs_serially
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 711, in _run_job
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_paging.py", line 87, in __next__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/aaz/_paging.py", line 46, in __next__
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/consumption/custom.py", line 85, in _output
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/consumption/custom.py", line 85, in <listcomp>
  File "D:\a\_work\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/command_modules/consumption/custom.py", line 95, in transform_usage_output
KeyError: 'usageStart'
To check existing issues, please visit: https://github.com/Azure/azure-cli/issues

hi Everyone - I can confirm the same issue.
I am currently running some tests using Azure DevOps Pipelines, and have prepared a pipeline that runs two jobs in parallel, both run the following command against two different subscriptions (service connections) under the same tenant:
        az consumption usage list
        --billing-period-name $(lastMonth)
        --include-additional-properties
        --include-meter-details
        --query "[].[instanceId, consumedService, instanceName, instanceLocation, product, pretaxCost, usageStart, usageEnd]"
        --output tsv

I ran this command 6 times within the span of about 40 minutes:

5 of those runs ended up with one of the job failing and the other one working fine (returning results)
1 run finished with both jobs completing OK
strangely enough, while I reliably get an error indicated above, I have not seen both jobs failing yet - only one of those seems to fail at any given run
this command never returns any errors when I run it from my local (always successful)

Hope that sheds a bit of light and helps your troubleshooting efforts.

urllib3.connectionpool: https://management.azure.com:443 "GET /subscriptions/895cda87-06a5-4a91-b04c-d023ccbc6525/providers/Microsoft.Consumption/usageDetails?$filter=properties%2FusageEnd%20ge%20%272024-01-08T00%3A00%3A00Z%27%20and%20properties%2FusageEnd%20le%20%272024-01-09T00%3A00%3A00Z%27&$top=1&api-version=2023-05-01 HTTP/1.1" 200 2976 cli.azure.cli.core.sdk.policies: Response status: 200
Looks like it gives the response, but a closer look at the url shows that there's 2x usageEnd. First one should be of course usageStart.

I've been facing this issue too with my workflow that checks for the az consumption usage list  :
ERROR: The command failed with an unexpected error. Here is the traceback:
ERROR: 'usageStart'
Traceback (most recent call last):
  File "/opt/az/lib/python3.[11](https://github.com/turbotio/ops/actions/runs/8277743509/job/22648667583#step:6:12)/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 664, in execute
    raise ex
  File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 731, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/core/commands/__init__.py", line 7[14](https://github.com/turbotio/ops/actions/runs/8277743509/job/22648667583#step:6:15), in _run_job
    result = list(result)
             ^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_paging.py", line 87, in __next__
    return next(self._page_iterator)
           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/core/aaz/_paging.py", line 46, in __next__
    curr_page, self._next_link = self._extract_result()
                                 ^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/consumption/custom.py", line 85, in _output
    result = list([transform_usage_output(item) for item in result])
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/consumption/custom.py", line 85, in <listcomp>
    result = list([transform_usage_output(item) for item in result])
                   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/opt/az/lib/python3.11/site-packages/azure/cli/command_modules/consumption/custom.py", line 95, in transform_usage_output
    usageStart = parser.parse(result['usageStart'])
                              ~~~~~~^^^^^^^^^^^^^^

I can confirm that the error still exists also in latest Azure CLI version 2.58.0.
Are there meanwhile any updates on this or a workaround to make this work again?
It's really bad not to be able to retrieve the detailled cost consumption per ressource via this simple CLI query since meanwhile more than a month.

I'm facing the same issue

I am also facing the issue in
az version {   "azure-cli": "2.58.0",   "azure-cli-core": "2.58.0",   "azure-cli-telemetry": "1.1.0",   "extensions": {} }

As a workaround you can try an older version
docker run -it mcr.microsoft.com/azure-cli:2.56.0

Still there in 2.61.0

az version
{
"azure-cli": "2.62.0",
"azure-cli-core": "2.62.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"ai-examples": "0.2.5",
"ml": "2.28.0",
"ssh": "2.0.4"
}
}

I might have found the issue on the following line:
https://github.com/Azure/azure-cli/blob/29564830498870c401679e0059fddbbf5851f10c/src/azure-cli/azure/cli/command_modules/consumption/custom.py#L78
The above line reads as follows:
filter_from = "properties/usageEnd ge \'{}\'".format(start_date.strftime("%Y-%m-%dT%H:%M:%SZ"))

Note that in the above line the filter from is using usageEnd instead of usageStart.
The fixed line should read as follows:
filter_from = "properties/usageStart ge \'{}\'".format(start_date.strftime("%Y-%m-%dT%H:%M:%SZ"))

Is there someone around who can test the above code changes?

While the usageEnd/usageStart noted above seems to indeed be a problem, I patched it manually on my install (now 2.63.0) and this error still happens.
Down in the transform_error_output where the error happens, I added a dump of results and it doesn't have the usageStart and usageEnd the code is looking for, or any of the other keys the function wants. The output looks like this:
{
  "id": "...",
  "name": "...",
  "accountName": "...",
  "consumedService": "...",
  "costCenter": "...",
  "meterId": "...",
  "product": "...",
  "subscriptionName": "...",
  "tags": {
    "..."
  },
  "type": "..."
}

Still there in 2.65.0

Issue still persists in current latest CLI version 2.67.0.
I wish this would be fixed soon, as the cost management UI is quite painful to use at the moment, even if you just want to gather a simple total cost of multiple subscriptions.

I am also facing the issue with the below cli version. Please try to fix it asap. It's quite painful to get the data manually from the portal for all the resources in each subscription for a tenant and I have multiple tenants to retrieve this data for.
{
"azure-cli": "2.65.0",
"azure-cli-core": "2.65.0",
"azure-cli-telemetry": "1.1.0",
"extensions": {
"ai-examples": "0.2.5",
"ml": "2.30.1",
"ssh": "2.0.5"
}
}


Add PlainText export

I needed to export data that I indexselect'd down to a small size so I could plot it as a 2D bar graph in Excel. I ended up having to write a script that used pick to extract 25x25 values that I wrote to a text file. It would have been far nicer to use the PlainText plugin to export the data as a text file in spreadsheet form. Hmm. I guess I could have used the Spreadsheet plot instead... Still, this would be a nice feature.
-----------------------REDMINE MIGRATION-----------------------
This ticket was migrated from Redmine. As such, not all
information was able to be captured in the transition. Below is
a complete record of the original redmine ticket.
Ticket number: 461
Status: Pending
Project: VisIt
Tracker: Feature
Priority: Normal
Subject: Add PlainText export
Assigned to: -
Category: -
Target version: -
Author: Brad Whitlock
Start: 11/02/2010
Due date:
% Done: 0%
Estimated time:
Created: 11/02/2010 05:30 pm
Updated: 11/15/2010 04:04 pm
Likelihood:
Severity:
Found in version: 2.12.3
Impact: 2 - Low
Expected Use: 2 - Rare
OS: All
Support Group: Any
Description:
I needed to export data that I indexselect'd down to a small size so I could plot it as a 2D bar graph in Excel. I ended up having to write a script that used pick to extract 25x25 values that I wrote to a text file. It would have been far nicer to use the PlainText plugin to export the data as a text file in spreadsheet form. Hmm. I guess I could have used the Spreadsheet plot instead... Still, this would be a nice feature.
Comments:
Brad - you should be able to do this pretty easily with a Python Query

we have python query code to do this, but not sure we ever shipped it with visit


NIFI-9831: XML schema inference fix for XML elements with attributes

https://issues.apache.org/jira/browse/NIFI-9831
Description of PR
Fixes bug NIFI-9831 where schema inference in case of XMLReader adds extra field to the record's schema if XML node has attribute.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[x] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

[x] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

[x] Has your PR been rebased against the latest commit within the target branch (typically main)?

[x] Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not squash or use --force when pushing to allow for clean monitoring of changes.

For code changes:

[x] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?
[x] Have you written or updated unit tests to verify your changes?
[x] Have you verified that the full build is successful on JDK 8?
[ ] Have you verified that the full build is successful on JDK 11?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?
[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?
[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.

I tried it and checked the good. Removing only a couple of lines looks kind of suspicious but I found that it works good. LGTM

I tried it and checked the good. Removing only a couple of lines looks kind of suspicious but I found that it works good. LGTM

Thank you @simonbence for reviewing it!

@pgyori Thanks for the fix!
@simonbence Thanks for the review!
Merging to main.


Allowing 'F' mode for 1 channel FloatTensor

fixes #1099

Codecov Report

Merging #1100 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1100      +/-   ##
==========================================
+ Coverage   64.57%   64.66%   +0.09%
==========================================
  Files          68       68
  Lines        5411     5411
  Branches      831      831
==========================================
+ Hits         3494     3499       +5
+ Misses       1665     1662       -3
+ Partials      252      250       -2

Impacted Files
Coverage Δ

torchvision/transforms/functional.py
71.38% <100%> (ø)
:arrow_up:

torchvision/transforms/transforms.py
81.53% <0%> (+0.98%)
:arrow_up:

Continue to review full report at Codecov.

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


Drop passPerPreset

Babel plugin execution ordering is sufficient to ensure that the Relay transform runs before the template literal transform when used as follows. As such, specifying passPerPreset is unnecessary, and dropping it avoids a number of problems that arise when using passPerPreset.
We've been running like this for some time now, so we figured it'd be nicer to update documentation to reflect what should be current best practices.

? I'm CLAed up

Does this look okay? It's a pretty small change, and it should make life better for whoever is still trying to ramp up on Relay 1.

Sounds good, not really sure why it was added.

I think it might have been a misinterpretation of (lack of) Babel ordering guarantees. Babel doesn't strictly order transforms as atomic units, but it does impose weaker ordering guarantees, which are sufficient here, since the Relay transform only needs to run before the template literal one, but both operate on the same type of node.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/1032 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-archive-test-target.git

Docs Build status updates of commit c27d3cf:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed] Cannot sync git repo to specified commit because branch Release_Archive_main_2022-02-11-01-19-10 has been deleted or has been force pushed

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Allows users to specify unseal key shares and key threshold

Overview
Allows users to specify unseal key shares and key threshold based on their specific requirements. The changes in this pull request also include modifications to the Custom Resource Definitions (CRDs), a version bump, and updates to a few example deployment YAML files.
Fixes #56
Notes for reviewer
This pull request introduces a different approach compared to PR-57, as this is mode independent(not just Kubernetes specific). Users will have the flexibility to utilize the options field in UnsealConfig to specify their desired values.
Thank you :)

A much-awaited feature. Thank you @farhan-pasha!!

Hey @sagikazarmark, @akijakya could you please have a look and possibly approve the PR.
I am no longer updating the versions + I have rebased the branch.
Thanks again :)


Add a function to convert from/to a known external color space

Some applications have functionality that generates synthetic objects that need to be integrated with a scene.  These objects are sometimes in a specific color space.  For example, a physical sky simulator might produce a blue gradient with known CIE XYZ coordinates.  Another example would be simulation of human hair or skin.  These synthetically generated objects must then be converted into RGB values for the current working space, defined by the OCIO config.  In the past, many applications assumed the working space was linear Rec.709, but that is no longer a good assumption.  Inserting linear Rec.709 RGB values for a physical sky simulation into a renderer that is using ACEScg as the working space gives obviously wrong looking results.
Another example is with applications that integrate an SDK for a digital cinema camera.  These applications receive decoded frames from media files that are in a specific color space.  It may then be necessary to convert these frames into a color space defined in the current OCIO config used by the application.
Historically, OCIO has intentionally avoided providing a formal connection from color spaces in a config to known external color spaces such as CIE XYZ.  In OCIO v2, two new "interchange" roles (aces_interchange and cie_xyz_d65_interchange) were added to facilitate use-cases as described above.  However, to respect the original design intentions of OCIO, these roles were left optional and may not be present in v2 configs, let alone v1 configs.
As discussed in a number of threads with Larry, Zach, and others on Slack, it would be very helpful for the API to include a function that could be used to convert between some well known external color space, such as CIE XYZ or linear Rec.709, and a color space in a given config.  If the interchange roles are present, these would be used.  If not, there would be a series of heuristics that would be used to identify a known color space.  These might be inaccurate in some cases, but the reality today is that application developers are already creating heuristics to solve these types of issues and there is value in at least having a standard set of heuristics that are documented and which could be improved over time, if needed.
For convenience, the function should offer a small number of scene-referred and display-referred color spaces that could be accepted.  These would certainly include the current two interchange roles, but other spaces could be added, if desired.  For example, scene-linear Rec.709 might be something many developers would appreciate for integrating OCIO with existing code.
The goal of the heuristics is to identify a known linear color space in the config.  The heuristics could include the following:

Assume the scene-referred and display-referred reference spaces are linear.  Define a set of candidate reference spaces including ACES2065-1, ACEScg, linear Rec.709, and CIE XYZ.
Try to find a color space whose from/to_ref transform is linear (i.e., only a Matrix, or set of Matrices) and check if the overall matrix matches one of a set of known matrices based on a set of common color spaces.  The matching would be within some tolerance (and perhaps a scale factor?).
If the above fails, the reference space may be using an unknown set of primaries.  Look for strings such as "sRGB", "ACEScg", and "Rec*709" to identify the primaries being used by a color space.  Then check if it has a linear relationship to the reference space.
If the above fails, assume the rendering role (if present) is linear Rec.709.  Otherwise assume the scene_linear role is linear Rec.709.  Note that this may not be the most common value for those roles, but I'm thinking that the expected last fallback should be linear Rec.709.  Any thoughts?

Once the heuristic has identified a color space in the config that is a known color space, the conversion process is basically the same as if the interchange roles are defined.  The function could build a simple config with the defined conversion spaces, add the known color space from the other config, and then use one of the existing GetProcessorFromConfigs calls to create a Processor for the conversion.
Regarding the sub-problem of identifying a linear color space, see also issue #1399.
A more formal specification of the API and heuristics is TBD.
Suggestions are welcome, as is feedback and discussion on the proposed functionality.

This is awesome, it completely captures my concerns and use cases, explains it very clearly.
On the renderer side, this would solve a number of problems that crop up.

I think this is totally reasonable. Thanks, Doug. Agreed that linear Rec.709 should be the last fallback, seeing as most renderers tend to assume those primaries, absent additional information.
Perhaps out of scope here, but I do think it would be wonderful if authors could attach optional chromaticities and chromatic adaptation transform (relative to implicit scene / display reference) metadata to Color Spaces. I feel like that would dovetail nicely if configs generated from OpenColorMath, if and when that becomes a thing.
(We're also not to far from the ten-year anniversary of this ticket: https://github.com/AcademySoftwareFoundation/OpenColorIO/issues/231 :) )

If we could provide CIE colourimetry it would be extremely useful. No need for “scene” vs “display” as that will likely become legacy. The CIE colourimetric definitions work for all colourimetry based downstream of it.
Would it not be sane to simply enforce a CIE_XYZ role and be done with it?

Why do you say "scene" vs "display" will likely become legacy? I'm not sure why you have that impression. The two reference spaces relate different image states, falling on either side of a View Transform (and are themselves related by a required default "colorimetry" View Transform). Even if "scene" and "display" color spaces were both defined relative to XYZ, there would still be a need to distinguish between pre- and post-View Transform states.
That said, unless I'm mistaken -- totally possible -- I think the elephant in the room is the ACES white point, and the arbitrary methods by which vendors implement adaptation from D65 -- i.e., if ARRI uses a CAT02 von kries, and RED uses a Bradford, and FilmLight just scales by an identity matrix, trying to implement non-ACES View Transforms in a config whose scene-referred color spaces are all defined with ACEScsc transforms necessarily means some paths make incorrect assumptions about how to "get back to" D65; and, likewise, there's only one default colorimetry path from the "scene-reference" to "display-reference". (I think Doug mentioned that SynColor provided a means for additional, alternate paths, but it meant drastically increasing graph complexity introducing potential path-finding ambiguity).

Why do you say "scene" vs "display" will likely become legacy?

Because ultimately the CIE colour model underlies all of this, and adding the “scene” vs “display” is just one arbitrary historical vernacular.
In the end, every single encoded value holds meaning, and that meaning is relative to the CIE XYZ foundation, not ACES.
ACES adds in some hand wavy “surround” rubbish, but it’s nothing beyond a power function atop CIE XYZ based colourimetry.
My point would be that folks can layer whatever historical rubbish they want atop of CIE XYZ colourimetry, so it would be incredibly sane to use that for all ground truth. Possibly even specifying revisions, such as 1931 CMFS vs 2012, etc., paving way for potential optional control.

You're conflating two separate concerns. Reread what I wrote above:

The two reference spaces relate different image states, falling on either side of a View Transform (and are themselves related by a required default "colorimetry" View Transform). Even if "scene" and "display" color spaces were both defined relative to XYZ, there would still be a need to distinguish between pre- and post-View Transform states.

So, as far OCIO goes, the difference between the "scene" and "display" reference spaces is  not arbitrary historical vernacular -- it is not merely a distinction between some RGB encoding and XYZ. Here, "scene" and "display" refer to distinct stages in the rendering pipeline -- pre-DRT and post-DRT. That, canonically (in terms of BuiltinTransforms), one happens to be AP0 and the other XYZ is incidental to the purpose the separation of reference spaces serves.
And to be clear, there's no problem with authoring a config that uses XYZ for both the "scene" and "display" reference spaces -- you'd just have to specify an identity transform for the default "colorimetry" View Transform; and, indeed, one could choose not to implement Display Color Spaces and View Transforms at all, and author configs that relate all color spaces via a single reference.
Hit me up privately and I'll provide some examples.
Anyway, to button things up:

Would it not be sane to simply enforce a CIE_XYZ role and be done with it?

Yes, I do think that would be sane. But this ticket concerns configs that aren't defining a CIE_XYZ role, because that hasn't historically been a requirement.

I’m happy to discuss pre and post image formation. That’s not, as you know, a conflation or problem.
The point I would make is that both are properly and ultimately correctly expressed in terms of CIE colourimetry.

Yes, I do think that would be sane. But this ticket concerns configs that aren't defining a CIE_XYZ role, because that hasn't historically been a requirement.

Which is where OpenColorIO could enforce a role.
Currently, the assumption on adjacent colour management workflows is “If unspecified, assume BT.709 primaries and transfer.” which would seem a sane entry point for OpenColorIO.
It provides a reasonable guess, and allows folks to specify the underlying XYZ colourimetry where required for software, in a single line.

Closing as implemented via PR #1710.


Source Request Allnoveread

Source name
AllnovelRead
Source link
https://allnovelread.com/
Language
English
Other details
Could you please add as a source the following site:
https://allnovelread.com/
Thanks
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open issue.
[X] I have written a title with source name.
[X] I have checked that the extension does not already exist by searching the GitHub repository and verified it does not appear in the code base.
[X] I will fill out all of the requested information in this form.

implemented in 2.0 version


REL pyfolio 0.8.0

@twiecki @vikram-narayan I also updated __init__.py while I was at it.
Closes #426

Great, want to wait for https://github.com/quantopian/pyfolio/pull/425 but think we should go ahead then. Also requesting engineering review @richafrank.

@eigenfoo Noticed an issue while attempting to install from head of master, we're missing a comma after 'scikit-learn>=0.18.2' in the install_reqs: https://github.com/quantopian/pyfolio/blob/0ea262f93251f015d70c694d0bd18654bddd7df2/setup.py#L47-L58

@yankees714 @twiecki fixed the bugs

@twiecki?

Waiting to merge https://github.com/quantopian/pyfolio/pull/425.

There was a small kerfuffle with #434: reverted the commit where I made the input checker.

Woohoo!

@twiecki https://github.com/quantopian/pyfolio/releases shows we're still on 0.7.0

OK, should be on github and pypi: https://github.com/quantopian/pyfolio/releases/tag/v0.8.0. Thanks for the help @eigenfoo and @jameschristopher.


Godot 4.0

The upcoming Godot 4.0 version will require a rewrite in code because of the changes in GDScript. This internally will force RetroHub to update to a major version, but the changes go deeper, as new themes will need to be developed for Godot 4.0 as well.
It's very likely that RetroHub will release using Godot 3.0, but plans need to be made for the new version.

Godot 4 was finally released. This means Godot 3 will slowly be phased out, although it's still recommended for upcoming projects. RetroHub should only make the jump for 4.0 when support has matured, and there are more tutorials for it.

According to this blog post, 3.6 will be the last feature release under Godot 3, and only minor patches will follow. While that version of Godot will still likely be supported in the long run, newer versions of RetroHub should shift to 4.0 when any leftover blockers are solved.

Considering that RetroHub has yet to hit a stable release, and Godot 4 has a "compatibility" renderer backend using OpenGL (very important for single board computers and low-end hardware), I've decided to begin porting RetroHub to the new Godot version.
Considering the changes and potential for breakage, this will mark a bump to v0.2.0. Until this port is complete, RetroHub is in feature-freeze.


Minicart disable when use new languages only velocity theme

Bug report
Title
Minicart disable when use new languages only velocity theme
Issue Description
Minicart disable when use new languages only velocity theme
English language is ok
Preconditions

framework Version- master

Steps to reproduce

step1- add a new locale
step2- select this locale in channel
step3- reload the velocity theme
step4- deselect that locale from channel again
step5- Now check the shop view

@psasquatch
Hope the issue is resolve for you.
No response from the last 1month so we are closing this ,Feel free to reopen if still exist.


Trigger tracing

Note that there is no existing standard for trace context propagation in Redis. https://www.w3.org/TR/trace-context-protocols-registry/#registry

@lann @itowlson I spiked out an alternative way for us to do the instrumenting in trigger-http. I don't love it, but it feels a little less invasive.
Let me know what you think. I'm trying to sus out if I should proceed in this direction or not.

Thank you for taking the time to explore options here!  I do share your queasiness about the current iteration but I think you might be onto something.  What I don't yet love is the finish_instrumenting(the_actual_response, blah, blah) because 1) it demotes the thing, the actual purpose of all this, into a mere input to the instrumentation function, and 2) it feels odd to see a finish function with no start!  I'm wondering if this could be tackled with something like
            let resp = match well_known {
                "health" => Ok(Response::new(body::full(Bytes::from_static(b"OK")))),
                "info" => self.app_info(),
                _ => Self::not_found(NotFoundRouteKind::WellKnown),
            };
            instrument(&resp);  // or end_current_span_with(&resp) or something
            return resp;

This seems to separate the "I need to capture the result in the span" from the logic of selecting the path and constructing the appropriate response.
You could even combine the last two lines into something like a return_from_span!(resp) macro - I have no idea if that's a good idea or a bad idea though!
I like how http_span! tidies away that overwhelming pile of span stuff.  Although now you have it I'd definitely consider getting rid of instrumented_servcice_fn and doing it all inline.  (Or just calling it service_fn or the like.  instrumented is not its purpose - I know it's front of mind for you but the purpose is handling the request: the instrumentation is an implementation detail (unless it's being distinguished from another one which isn't instrumented).)
I hope that's helpful - I'm all too aware that I may be being constantly dissatisfied without knowing what I actually want other than "can you make it happen by magic"...!

Thank you for taking the time to explore options here! I do share your queasiness about the current iteration but I think you might be onto something. What I don't yet love is the finish_instrumenting(the_actual_response, blah, blah) because 1) it demotes the thing, the actual purpose of all this, into a mere input to the instrumentation function, and 2) it feels odd to see a finish function with no start! I'm wondering if this could be tackled with something like

I hear those concerns and agree with them.

            let resp = match well_known {
                "health" => Ok(Response::new(body::full(Bytes::from_static(b"OK")))),
                "info" => self.app_info(),
                _ => Self::not_found(NotFoundRouteKind::WellKnown),
            };
            instrument(&resp);  // or end_current_span_with(&resp) or something
            return resp;

This seems to separate the "I need to capture the result in the span" from the logic of selecting the path and constructing the appropriate response.

Unfortunately what you've proposed above wouldn't work b/c the &resp alone is not sufficient to get the route. I need to explicitly pass the route to my instrumentation function somehow and also tell it whether the route is high or low cardinality (this tells me if I should put it in the span name or not). Needing the route is how I've ended up wrapping all the returns.
I tried wrapping the whole handle function with a single instrument function and then passing the route via an extension on the req, but I couldn't get that to work.
Another alternative would be to wrap the whole handle in an instrumented function like below. The downside to this is we would need to explicitly return the route from handle.
fn instrument_handle(response: Result<(Response<T>, String)>) -> Result<Response<T>> {
  // handle error case
  let (response, route) = response;
  // Do a bunch of otel stuff
  Ok(response)
}

// in service_fn
let span = http_span!(request, addr);
instrument_handle(self.handle(...).instrument(span).await)

What do you think about that as an alternative?

You could even combine the last two lines into something like a return_from_span!(resp) macro - I have no idea if that's a good idea or a bad idea though!

I don't either 🙃 🤷

I like how http_span! tidies away that overwhelming pile of span stuff. Although now you have it I'd definitely consider getting rid of instrumented_servcice_fn and doing it all inline. (Or just calling it service_fn or the like. instrumented is not its purpose - I know it's front of mind for you but the purpose is handling the request: the instrumentation is an implementation detail (unless it's being distinguished from another one which isn't instrumented).)

Make sense to me.

"can you make it happen by magic"...!

🪄
(In all seriousness though thank you for your recognition of this and it is no problem. I appreciate your tenacious hunt for the best code.)

Unfortunately what you've proposed above wouldn't work b/c the &resp alone is not sufficient to get the route. I need to explicitly pass the route to my instrumentation function somehow...

I am probably being obtuse but I don't get why that would be an obstacle.  You still have that info after the match expression as far as I can tell - I was just lazy and didn't write it into my example. grin
        if let Some(well_known) = path.strip_prefix(spin_http::WELL_KNOWN_PREFIX) {
            let resp = match well_known {
                "health" => Ok(Response::new(body::full(Bytes::from_static(b"OK")))),
                "info" => self.app_info(),
                _ => Self::not_found(NotFoundRouteKind::WellKnown),
            };
            instrument_me_up(&resp, req.method(), path);
            return resp;
        }

Is it something to do with not wanting to instrument the path if it's a 404?  Could that not be handled by examining the response status in the finish_instrumenting / instrument / whatever function?

I forgot to comment on the second part.  Yes, a wrapping function that does the instrumentation after the whole of handle makes a great deal of sense to me.  I had assumed there was a reason you weren't doing it that way - I know there is an imperial buttload of fiddly exit paths and assumed it was something to do with that - but yes, if you can put it all into a little middleware helper, then that achieves a very clean separation of concerns.
(This may be what you were aiming for with instrumented_service_fn, I am not sure?  If so, and if it can take all/most of the OTel stuff off handle's shoulders, that would 100% justify its existence and I would be delighted to eat my words over it!)

Okay @itowlson I took another crack at this. The code is still very rough, but I'm curious what you think about the latest approach. I like that it keeps OTEL code out of handle for the most part. I don't like that it requires me to return a custom RoutedResponse type. Unfortuantely, that was the only way I could think to get that route information out of the handle function.

@calebschoepp I'm reading this but have gotten myself confused about what "route" means.  Sometimes it seems to be the request path, but other times it seems to be the matched route pattern.  Am I misreading?  Which is it intended to be?  Thanks!

@calebschoepp I'm reading this but have gotten myself confused about what "route" means.  Sometimes it seems to be the request path, but other times it seems to be the matched route pattern.  Am I misreading?  Which is it intended to be?  Thanks!

95% of the time it will be the matched route pattern. 5% of the time when well known endpoints are hit it will be a path (but really you can just think of that as the matched route).

@calebschoepp This feels like a viable approach, although I sympathise with your dislike of adding an extra type just to carry the instrumentation data.  If we go ahead with this, there is definitely stuff we can do to make it less intrusive, e.g. constructors for RoutedResponse or a with_matched_route() helper on Response or such like.  Thanks for all the investigating and experimenting!

@calebschoepp This feels like a viable approach, although I sympathise with your dislike of adding an extra type just to carry the instrumentation data.  If we go ahead with this, there is definitely stuff we can do to make it less intrusive, e.g. constructors for RoutedResponse or a with_matched_route() helper on Response or such like.  Thanks for all the investigating and experimenting!

Happy to experiment.
If we're generally happy with going this direction then I think the next step would be a more thorough code review from you for ideas on how we'll clean it up. With the caveat that obviously I'll go back and full in the todo comments.


!addlicense does not work with some free apps

I use ArchiSteamFarm V1.7 (pre1).
I want to get this free game and free DLC.
http://store.steampowered.com/app/397720/
http://store.steampowered.com/app/420540/
Chat log:
Me: !addlicense 397720
Bot: Result: OK | Granted apps: 397720
Me: !addlicense 420540
Bot: Result: OK | Granted apps:
And my bot don't get DLC.

!addlicense is steam client-based command, and not every app is being able to redeem through steam client request.


Allow one * at the start of a docblock

docblockRe was requiring two, but commentStartRe down below was fine with one. My current project has a custom webpack haste loader that only looks for provides and providesModule and we have a lot of existing code that has only one * in its docblocks so it seemed easier to relax the restriction here.

Thanks! I'll defer to @zpao to create a branch for node-haste1 and publish a patch release with the same change.

I already talked to both of you but I'm actually just going to revert this and fix the other regex. Everything I can find about docblocks refers to (and sometimes requires) **

I'm never going to trust you again when you say "you should merge this".

I'm never going to trust you again when you say that you are "completely rewriting it" but then leave some things and delete their tests 😛

I just copied some other people's code!


Update dependencies

Reduces vulnerabilities from 11 -> 0 (These are development dependencies and not part of the bundle)
The major one here is Lerna - it builds locally etc. but might be worth pushing a release to make sure.
(I've checked there BREAKING CHANGES section of the 4.0.0 changelog and cannot see anything of concern)
I have manually resolved several development dependencies after checking their change logs.
I couldn't see any major changes in their API's (from changelog/commit history)
I have checked our dev tools still work as expected and the build is unaffected.

:rocket: PR was released in v1.3.9 :rocket:


[Self Hosted] Server error in new install (custom domain)

I'm not quite sure how to fix this one (/srv/newsblur/media/css/reader/reader.css exists, looks to contain the right stuff & is owned by my user)
To reproduce:

'git clone' into a new NewsBlur folder.

Run the custom_domain.sh script (needs moving & chmod +x, but I'll do that as a pull request) to my_domain.tld

Change docker-compose haproxy ports to avoid clashes (these are the same as in my previous, working, version)

ports:
      - 1180:80
      - 11443:443

make nb goes OK & logs seem fine.

Open the web page (at the custom domain) the there is an error page & the logs read:

---> Starting NewsBlur development server...

[Jul 24 20:53:18]  ---> [FF    ] [0.02s] [AnonymousUser] Loading welcome

[Jul 24 20:53:19] Internal Server Error: /

Traceback (most recent call last):

  File "/usr/local/lib/python3.9/site-packages/django/core/handlers/exception.py", line 47, in inner

    response = get_response(request)

  File "/usr/local/lib/python3.9/site-packages/django/core/handlers/base.py", line 181, in _get_response

    response = wrapped_callback(request, *callback_args, **callback_kwargs)

  File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/django/views.py", line 67, in sentry_wrapped_callback

    return callback(request, *args, **kwargs)

  File "/usr/local/lib/python3.9/site-packages/django/views/decorators/cache.py", line 44, in _wrapped_view_func

    response = view_func(request, *args, **kwargs)

  File "/srv/newsblur/utils/view_functions.py", line 32, in wrapper

    return render(request, output[1], output[0])

  File "/usr/local/lib/python3.9/site-packages/sentry_sdk/integrations/django/templates.py", line 95, in render

    return real_render(request, template_name, context, *args, **kwargs)

  File "/usr/local/lib/python3.9/site-packages/django/shortcuts.py", line 19, in render

    content = loader.render_to_string(template_name, context, request, using=using)

  File "/usr/local/lib/python3.9/site-packages/django/template/loader.py", line 62, in render_to_string

    return template.render(context, request)

  File "/usr/local/lib/python3.9/site-packages/django/template/backends/django.py", line 61, in render

    return self.template.render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 170, in render

    return self._render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 162, in _render

    return self.nodelist.render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render

    bit = node.render_annotated(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated

    return self.render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/loader_tags.py", line 150, in render

    return compiled_parent._render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 162, in _render

    return self.nodelist.render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render

    bit = node.render_annotated(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated

    return self.render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/defaulttags.py", line 39, in render

    output = self.nodelist.render(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 938, in render

    bit = node.render_annotated(context)

  File "/usr/local/lib/python3.9/site-packages/django/template/base.py", line 905, in render_annotated

    return self.render(context)

  File "/usr/local/lib/python3.9/site-packages/pipeline/templatetags/pipeline.py", line 136, in render

    return self.render_compressed(package, package_name, 'css')

  File "/usr/local/lib/python3.9/site-packages/pipeline/templatetags/pipeline.py", line 69, in render_compressed

    return self.render_compressed_sources(package, package_name,

  File "/usr/local/lib/python3.9/site-packages/pipeline/templatetags/pipeline.py", line 112, in render_compressed_sources

    return method(package, paths, templates=templates)

  File "/usr/local/lib/python3.9/site-packages/pipeline/templatetags/pipeline.py", line 148, in render_individual_css

    tags = [self.render_css(package, path) for path in paths]

  File "/usr/local/lib/python3.9/site-packages/pipeline/templatetags/pipeline.py", line 148, in <listcomp>

    tags = [self.render_css(package, path) for path in paths]

  File "/usr/local/lib/python3.9/site-packages/pipeline/templatetags/pipeline.py", line 143, in render_css

    'url': mark_safe(staticfiles_storage.url(path))

  File "/srv/newsblur/utils/pipeline_utils.py", line 14, in url

    url = super().url(*args, **kwargs)

  File "/usr/local/lib/python3.9/site-packages/django/contrib/staticfiles/storage.py", line 147, in url

    return self._url(self.stored_name, name, force)

  File "/usr/local/lib/python3.9/site-packages/django/contrib/staticfiles/storage.py", line 126, in _url

    hashed_name = hashed_name_func(*args)

  File "/usr/local/lib/python3.9/site-packages/django/contrib/staticfiles/storage.py", line 417, in stored_name

    raise ValueError("Missing staticfiles manifest entry for '%s'" % clean_name)

ValueError: Missing staticfiles manifest entry for 'css/reader/reader.css'

I meet the same problem on Ubuntu 20.04.
After cloning the repo, I changed nothing and just run make nb. It finished successfully and all the containers are started. The error appears when trying to visit the page: ValueError: Missing staticfiles manifest entry for 'css/reader/reader.css'

The problem was solved after running make collectstatic

Ok, I'm going to add make collectstatic to the make nb command. It's bit too many people and you don't have to run make nb all the time, only when things break (which they do a few times a year).


Make tuple_map sufficiently large at init time

Fixed #60. The trace shows that sometimes our phmap::flat_hash_map<...> tuple_map can hit an assertion to check if its capacity is large enough
https://github.com/UWHustle/hustle/blob/3406248302e8a8c75f8eca923cc3c1fb563749f7/src/utils/parallel_hashmap/phmap.h#L1815
and triggers the error.
Reserve enough capacity will avoid this problem.

Should we make this more robust, so we can expand the size of the tuple_map if we hit the new limit?

I agree. Although I haven't understand the intention why this assertion exist. @srsuryadev If you have and idea, please let me know.

@pateljm  Yes, it is just the initial size of the table which we have the flexibility to choose. If it is not able to insert values, rehash takes place and dynamically increase the table size. (It will be handled by the phmap library).

@GindaChen  I think we can make this initial value set in the configuration option object.


Multi-authors journal

I search a solution to write manually short log message for a small team and I found your project very interesting. I know to develop in python but before to implement some features missing for my usage, I want to know if you think it's stupid or not.

I want to add an information about author, maybe I can add it on each entry or simply create different files ?
I want an option to search on all files, maybe to implement a MultiJournal class ?

I'm also wondering on implement an web interface to view journals.

Hi @Starfight, thanks for your questions!

I would recommend using tags for that. You can use custom tag characters so that both eg. #my_project and @author_name work.
Yes, that would work - check out the code in the 2.0 branch though, there should be a much better foundation for that already.

Hope that helps!


build content - Topic Template

Owner : content designer
Validation : Design lead as needed
Definition of done  :

[ ] Validation of template name, definition, example image are validated
[ ] Use case as detailed in requirement doc  is reviewed
[ ] content guidance for the Design and accessibility section of the template has been reviewed with designer
[ ] guidance for the Dev Build and accessibility section of the template has been reviewed with dev
[ ] Identify and write template copy: set labels, error messages, or other copy, I18N code elements
[ ] Sent to Translation & Localization and tag
[ ] Bilingual review is done

Acceptance criteria

[ ] Has EN and FR guidance
[ ] Plain language
[ ] Consistent with previous lexicon used in GCDS.
[ ] Writer does not flag any problem
[ ] Descriptive text for images are created as needed

@SmartMouthWords what do you think of this ? Let me know what we should adapt for the template situation

Flagging today DTO released an update to the topic page design, code, and guidance.

Review done late October and added questions. Will need a second draft to update to latest page structure for the templates.


v3.0 rc3a: AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'

Seeing this on every HA boot from icloud3 Debug Log:
2023-08-20 15:40:57 [__init__....:0136]  son2, son2s_iphone:
										{'ic3_devicename': 'son2s_iphone', 'fname': 'son2', 'picture': 'None', 'evlog_display_order': 0, 'unique_id': '', 'device_type': 'iphone', 'inzone_interval': 120.0, 'tracking_mode': 'track', 'famshr_devicename': "son2's iPhone", 'famshr_device_id': 'AUfPhNVVaDN0td++R46k333FzQOELVeCIKsMddjlx0f/V+8dPl6tcsrsLzCAJ0GwWyNMkl9zJETFm6CQbNuQe32qdHJq8io4RAxiROrX0j0dQG4pny978Fob33oXguqCNhd6wQwu333PT1Oul783LbwyBAnctspuQFhHWAd9ivAIZLAnwa1K', 'raw_model': 'iPhone14,6', 'model': '', 'model_display_name': '', 'fmf_email': 'None', 'fmf_device_id': '', 'iosapp_device': 'son2s_iphone_app', 'track_from_base_zone': 'home', 'track_from_zones': ['home'], 'old_devicename': 'son2s_iphone'}
2023-08-20 15:40:57 [__init__....:0136]
2023-08-20 15:40:57 [__init__....:0142]  Setting up iCloud3 3.0rc3a - Using Integration method
2023-08-20 15:41:16 [device_track:0204]  Traceback (most recent call last):
  File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
    if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
       ^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'
2023-08-20 15:41:16 [device_track:0204]  Traceback (most recent call last):
  File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
    if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
       ^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'
2023-08-20 15:41:16 [device_track:0204]  Traceback (most recent call last):
  File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
    if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
       ^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'
2023-08-20 15:41:16 [device_track:0264]  Device Tracker entity created: device_tracker.snuffy2s_iphone, #1
2023-08-20 15:41:17 [device_track:0264]  Device Tracker entity created: device_tracker.wifes_iphone, #2
2023-08-20 15:41:17 [device_track:0264]  Device Tracker entity created: device_tracker.son1s_iphone, #3
2023-08-20 15:41:17 [device_track:0264]  Device Tracker entity created: device_tracker.son2s_iphone, #4
2023-08-20 15:41:17 [device_track:0109]  Device Tracker Entities: 4
2023-08-20 15:41:18 [device_track:0204]  Traceback (most recent call last):
  File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
    if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
       ^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'
2023-08-20 15:41:18 [device_track:0204]  Traceback (most recent call last):
  File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
    if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
       ^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'
2023-08-20 15:41:18 [device_track:0204]  Traceback (most recent call last):
  File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
    if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
       ^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'

device_tracker.zip
Unzip that into the icloud3 directory and restart ha

Looking good. No longer seeing the error and the trackers appear to be updating.

Thanks. I just updated everything and have uploaded a prelease to the old iCloud3 repository.

I won't be able to test again likely for a few days, but I just installed v3.0 rc3b which shows as pr1 in the ic3 logs.
The same errors as above are showing again.
2023-08-20 17:02:32.800 ERROR (MainThread) [icloud3] 'DeletedDeviceEntry' object has no attribute 'name'
Traceback (most recent call last):
File "/config/custom_components/icloud3/device_tracker.py", line 189, in _get_dr_device_id_from_device_entry
if device_entry.name in [DOMAIN, ICLOUD3, 'iCloud3 Integration']:
^^^^^^^^^^^^^^^^^
AttributeError: 'DeletedDeviceEntry' object has no attribute 'name'


OIDC configuration in Azure fails - flicker refresh loop

When I try to login to my Datahub instance using SSO, the DataHub home page appears for a split second, and then I experience a refresh loop:

It ends with this page:

I have configured my Azure portal as described in this guide and my datahub-frontend has these env values:
AUTH_OIDC_ENABLED:             true
AUTH_OIDC_CLIENT_ID:           <my client ID>
AUTH_OIDC_CLIENT_SECRET:       <my client secret>
AUTH_OIDC_BASE_URL:            <my base url>
AUTH_OIDC_DISCOVERY_URI:       https://login.microsoftonline.com/<my tenant id>/v2.0/.well-known/openid-configuration
AUTH_OIDC_SCOPE:               openid profile email

I see these logs in datahub-frontend:
2022-12-22 18:53:42,722 [application-akka.actor.default-dispatcher-6] ERROR o.p.core.engine.DefaultCallbackLogic - Unable to renew the session. The session store may not support this feature
2022-12-22 18:53:43,399 [application-akka.actor.default-dispatcher-11] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:43,399 [application-akka.actor.default-dispatcher-6] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:43,399 [application-akka.actor.default-dispatcher-10] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:43,482 [application-akka.actor.default-dispatcher-10] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:43,516 [application-akka.actor.default-dispatcher-9] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:43,543 [application-akka.actor.default-dispatcher-8] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:44,221 [application-akka.actor.default-dispatcher-8] ERROR o.p.core.engine.DefaultCallbackLogic - Unable to renew the session. The session store may not support this feature
2022-12-22 18:53:44,862 [application-akka.actor.default-dispatcher-13] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:44,868 [application-akka.actor.default-dispatcher-13] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check
2022-12-22 18:53:44,941 [application-akka.actor.default-dispatcher-13] WARN  p.api.mvc.LegacySessionCookieBaker - Cookie failed message authentication check

I can see that the login to Azure AD was successful, because my user was added to the portal (visible by logging in with admin credentials).

As you can see in the above screenshot, my requests to /api/v2/graphql are getting a 401 Unauthorized request. I can reproduce this by sending the same POST request in Postman copying my cookie from the browser as a header in the Postman request.
We are using Cloudflare and I see those headers in the response.

hi, @adamhowardprice . I met the same problem.
how are you solved this?
thanks!

@jkl0898 I upgraded to 0.9.5!

@adamhowardprice thanks!


Component Schema for actions is overly constrained & ActionScope needs a non-list check

Today the Adaptive component schemas that model actions are set as required when they do not need to be. This confuses authoring canvases like Composer or PVA who throw errors based on these policies.
Additionally, ActionsScope has the potential to accept a non-list item like null and break the runtime.
Description
We currently require actions to be set in schema, but the code is not robust to actions being set to null.
Specific Changes

Change ActionScope to deal with null assignment as the same as empty array.
remove required "actions" constraint on triggers, IfCondition, ForEach schema definitions.

@garypretty please prioritize and add any needed information.


Unable to get deployment info after a successful deployment

Description
I was trying to deploy a full vm on qanet playground and it failed with the following error

Error: Failed to get deployment due to Error: Failed to send request to twinId 9 with command: zos.deployment.get, payload: {"contract_id":9744} due to 300 failed to validate envelope: message has expired

this error happened with me both on node 2 & 3 even though i deployed a full vm on node 3 an hour before this deployment and it was deployed successfully without any issues.
And by checking the contracts list i found that the contracts for the vm are available.

after that i got the ip from the contracts details and i was able to ssh to the vm without any issues. and after reloading the deployment list it also appeared there.

Steps to reproduce

Navigate to https://play.qa.grid.tf/
Configure and deploy a full vm.

Environment

Network: qanet
Weblets Version: v1.7.0-rc3

i'll close as fixed


Total number of features is not displayed

Describe the bug
Total number of features is not displayed

Expected Behavior
Total number of features should be displayed displayed
Reproduction Steps & Sample
Use this web map: https://devext.arcgis.com/home/item.html?id=fa9cf987a08e42018b3756b73f392fae (vpn connection required)

Username: admin
Password: esri.agp

Please do not edit the data.

Create a new Manager app using the web map above
Observe the total count of features below the table once it's loaded

Other Relevant Info
No response

@sarahmcdonald7

@avezina @azizaparveen do you know if there are any specific settings like filters or a certain amount of features in a layer that need to be present in order for the count not to appear? I see the count work fine in some of my apps.

@sarahmcdonald7 I don't think so, I see this issue when I first load the app, but if I select a record, the count shows up as expected

I've not been able to repro. Any console errors when this occurs?

Both me and Alix are seeing this issue, for me, when I first load the app, it works, the if I switch layers for the first time it works, then if I switch back to the first layer again, I see this issue, it is random for Alix.
Test app: https://arcgis4localgov2.maps.arcgis.com/apps/instant/manager/index.html?appid=cce4a70f27084767bc78777a7ae79832
@john could you please take a look, cc @sarahmcdonald7

@jmhauck Looks like some kind of timing issue? Does the count know when the layers are loaded? How does it work?
Also wondering, aside from on load, does the count refresh along with the refresh interval?

This looks good in qa


add WebSocket

The esp-at repository does not accept direct Pull Requests. If there is a demand, please submit it in the https://github.com/espressif/esp-at/issues.


triggers vs hooks

Minor point about language. A smart-contract is a simple "on trigger execute Executable" concept. A trigger is the mechanism that decides that something needs to run, not the thing whose main you're calling.

In other words, iroha_trigger makes me think that the trigger isn't just the event-driven system that launched the smartcontract, but that it is the smart-contract.
The old naming convention was somewhat generic, I admit, but it wasn't conceptually dissonant.
    iroha_hook::info!("Executing trigger");

or maybe
    iroha_smartcontract::info!("Executing trigger");

Personally prefer the hook name, because it's shorter and makes it clear that it acts like lisp hooks do, minus the dynamic typing.
Originally posted by @appetrosyan in https://github.com/hyperledger/iroha/pull/3813#discussion_r1298888133

I'm not sure what is the difference between a hook and a trigger. If someone can explain we can consider renaming, although I find that trigger is quite adequate naming

I don't like changing terminology without good reason.


mysql外表连接异常导致be shutdown

Steps to reproduce the behavior (Required)

Expected behavior (Required)
Real behavior (Required)
StarRocks version (Required)

2.4.0 c0fa2bb

The error message indicates that there're too many connections on the mysql side.
You could decrease the value of jdbc_connection_pool_size in be.conf.


Create css theme style based on wireframe design, called themePalette.css

Task
Create base css theme style based on the wireframe. The colours are listed below.
See the app brand guide in brand guide.
Theme palette:
CORE COLORS
Red: #f64141
Dark-Grey: #2c2c2c
Light-Grey: #aaaaaa
Off-White: #ebebeb
White: #ffffff
SLIDING SCALE
Selected-Red: #f64141
Unselected-Grey: #b8b8b8
Grey-slide-bar: #666666
Box-outline: #dfdfdf
TEMPERATURE GRADIENT:
Blue #3100fe --> Red #f33443
What done looks like:

We have a themePalette.css file in /css to style the website's theme.

Design considerations:
We have decided to use regular CSS files to keep things simple for now. This allows for more contributors and less time to upskill to contribute.
Once MVP is done the team can discuss if we want to transition it to styled-components or something like CSS modules.
Folder paths
CSS is located in /client/src/css
Style guide for CSS files:
Naming convention:
CSS file ->  themePalette.css

Great job @jchen42703 !


Service discover not working properly or the problem is with me? :)

I'm experimenting with docker-compose, consul and registrator, but i can't get this working. Basically, i have two simple services serv1 and serv2 written in node and i just want to send a http request from serv1 to serv2. The Dockerfile for both services is:
FROM ubuntu:15.04

# Install curl and dev tools
RUN apt-get update && \
    apt-get install -y curl && \
    apt-get install -y build-essential

# Install node 5.x (see https://github.com/nodesource/distributions)
RUN curl -sL https://deb.nodesource.com/setup_5.x | bash - && \
	apt-get install -y nodejs

# Set working directory
WORKDIR /home

# Move code to container
ADD main.js package.json ./

# Install dependencies
RUN npm install

# Entry point command
ENTRYPOINT ["node", "main.js"]

For service 1 we get:
var express 		= require('express'),
	request 		= require('request'),
    dns             = require('dns');

(function() {
	var app = express();

	app.get('/', function(req, res) {
		console.log('got get request');
        var hostname = 'serv2.service.consul';

        dns.resolveSrv(hostname, function(error, records) {
            if(error){ return console.log(error); }

            console.log(records);

            request.get('http://'+records[0].name+':'+records[0].port;, function(error, response, body) {
                console.log('got response');
    			console.log(body);
    			res.send(body);
    		});
        });
	});

	app.listen(12346);

	console.log('Service 1 listening on port 12346');
})();

for service 2:
var express 		= require('express');

(function() {
	var app = express();

	// respond with "hello world" when a GET request is made to the homepage
	app.get('/', function(req, res) {
		res.send({message: "hello world"});
	});

	app.listen(12346);

	console.log('Service 2 listening on internal port 12346');
})();

and my docker-compose file goes like this (based on http://blog.neilni.com/2015/09/14/consul-and-consul-template-with-docker-compose/):
consul:
    container_name: consul
    image: progrium/consul:latest
    ports:
        - "8300:8300"
        - "8400:8400"
        - "8500:8500"
        - "8600:53/udp"
        - "<IP_ADDRESS>:53:53/udp"
    command: -server -bootstrap

registrator:
    container_name: registrator
    image: gliderlabs/registrator:latest
    links:
        - consul
    volumes:
        - "/var/run/docker.sock:/tmp/docker.sock"
    command: consul://consul:8500

serv1:
    container_name: serv1
    build: ./serv1
    ports:
        - "12346:12346"
    volumes:
        - ./serv1:/home
    links:
        - registrator
    environment:
        SERVICE_NAME: serv1
    dns:
        - <IP_ADDRESS>
    dns_search:
        - consul

serv2:
    container_name: serv2
    build: ./serv2
    ports:
        - "12347"
    volumes:
        - ./serv2:/home
    links:
        - registrator
    environment:
        SERVICE_NAME: serv2
    dns:
        - <IP_ADDRESS>
    dns_search:
        - consul

No matter what i try to change the above codes, i can't get the communication between the two simple services. Could anyone help me? :)
PS.: In consul/registrator logs everything seems to be working, with serv1 and serv2 been properly registered. Check it out:
registrator | 2016/01/03 18:07:58 added: abba11987dcb 9f2150e64519:serv2:12347
consul      |     2016/01/03 18:07:58 [ERR] agent: failed to sync changes: No cluster leader
consul      |     2016/01/03 18:07:58 [ERR] agent: failed to sync changes: No cluster leader
registrator | 2016/01/03 18:07:59 added: a8124ad1c6a3 9f2150e64519:serv1:12346
consul      |     2016/01/03 18:07:58 [ERR] agent: failed to sync changes: No cluster leader
consul      |     2016/01/03 18:07:59 [ERR] agent: failed to sync changes: No cluster leader
serv2       | Service 2 listening on internal port 12346
serv1       | Service 1 listening on port 12346
consul      |     2016/01/03 18:08:00 [WARN] raft: Heartbeat timeout reached, starting election
consul      |     2016/01/03 18:08:00 [INFO] raft: Node at <IP_ADDRESS>:8300 [Candidate] entering Candidate state
consul      |     2016/01/03 18:08:00 [INFO] raft: Election won. Tally: 1
consul      |     2016/01/03 18:08:00 [INFO] raft: Node at <IP_ADDRESS>:8300 [Leader] entering Leader state
consul      |     2016/01/03 18:08:00 [INFO] consul: cluster leadership acquired
consul      |     2016/01/03 18:08:00 [INFO] consul: New leader elected: 1657b8e31fd7
consul      |     2016/01/03 18:08:00 [INFO] raft: Disabling EnableSingleNode (bootstrap)
consul      |     2016/01/03 18:08:00 [INFO] agent: Synced service '9f2150e64519:consul:8300'
consul      |     2016/01/03 18:08:00 [INFO] agent: Synced service '9f2150e64519:consul:8400'
consul      |     2016/01/03 18:08:00 [INFO] agent: Synced service '9f2150e64519:consul:8500'
consul      |     2016/01/03 18:08:00 [INFO] agent: Synced service '9f2150e64519:consul:53:udp'
consul      |     2016/01/03 18:08:00 [INFO] agent: Synced service '9f2150e64519:serv2:12347'
consul      |     2016/01/03 18:08:00 [INFO] agent: Synced service '9f2150e64519:serv1:12346'

and this is what i get from serv1 logs:
serv1       | got get request
serv1       | [ { name: '1657b8e31fd7.node.dc1.consul',
serv1       |     port: 32786,
serv1       |     priority: 1,
serv1       |     weight: 1 } ]
serv1       | got response
serv1       | undefined

@brunomacf From your consul logs it seems to me that Registrator did it's job here, because apparently all your services appear in the log file. Try to debug the rest in your Node.js app a bit further, e.g. print out the full URL and error of request.get(). Can you reach your serv2 app manually from the outside on port 12347? To be honest, I don't know what the short form of ports: - "12347" does (why not - "12347:12346"?).

see my comments https://github.com/gliderlabs/registrator/issues/320


App not found in Play Store

When I tap on the Play Store logo in the README.md I get an error.
Thanks for developing this app. Definitely the best GitHub app for Android.

This app is just a copy of ForkHub https://github.com/jonan/ForkHub
You can find the original app in the Play Store https://play.google.com/store/apps/details?id=jp.forkhub


Dashboard: Backgrounds not coming through on preview cards

Bug Description
The backgrounds are not visible on the preview cards.
Expected Behaviour
Backgrounds should show up on preview cards.
Steps to Reproduce
For older stories that haven't been updated in about a week, their backgrounds will not show up.
Screenshots

Additional Context

Plugin Version:
Operating System:
Browser:

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

Previews are looking good for me in master, closing.


Refund payments in Adyen from Saleor notifications

This PR adds Adyen refund handling initiated in Saleor.

Handle TRANSACTION_ACTION_REQUEST events for Adyen transactions
Add integration tests for webhook handler
Check if webhook event for specified transaction was already processed to avoid duplicate refunds

Depends on: https://github.com/saleor/react-storefront/pull/321
TODO

[x] Check if refund exists for a transaction in Saleor (use new transaction query)
[x] Add integration tests for transaction-action-update webhook endpoint

[x] Refund is created
[x] Refund is already created

Handle VOID events Created separate tickets:
https://github.com/saleor/react-storefront/issues/362
https://github.com/saleor/react-storefront/issues/361

I had to temporarly disable tests for checking if refunds are created in Mollie and Adyen due to issues with Polly.js.
We need to use the node interceptor instead of fetch in Polly.js, but to do that we need to ditch MSW as well. I've made a PR with attempt to fix this some time ago: https://github.com/saleor/react-storefront/pull/325