Option to provide identity token instead of credential in authenticateUserWithApple

Some of us (I think more than myself) are using this plugin in addition to the Firebase JS SDK, just to provide functionality not available in that SDK (such as A/B testing).
So I need to authenticate users on the JS side, but the current authenticateUserWithApple implementation doesn't allow for that as it returns a credential to use with the signInWithCredential API of this plugin.
Ideally we could get the identityToken returned by Apple, similar to this plugin, which can then be used to create a credential on the JS side, e.g. something like:
const credential = new firebase.auth.OAuthProvider('apple.com').credential({
    idToken: identityToken
});

for authenticating the user.
& at least I don't think there's a way to authenticate the user on the web/JS side with the current implementation but please do correct me if I'm wrong.

Just leaving a comment in an attempt to keep this open

Based on an Apple sign in success, is there currently a way to obtain idToken and refreshToken from Firebase at all?

I agree, it would be nice. When you use authenticateUserWithGoogle the credential returned has an idToken so we can then use signInWithCredential, but I can't get it to work with authenticateUserWithApple

Superseded by #857 857


rename Adapter from liftoff to vungle

🏷 Type of documentation

[ ] new bid adapter
[x] update bid adapter
[ ] new feature
[ ] text edit only (wording, typos)
[ ] bugfix (code examples)
[ ] new examples

📋 Checklist

[x] Related pull requests in prebid.js or server are linked -> Paste link in this list or reference it on the PR itself
[ ] For new adapters check submitting your adapter docs
[x] https://github.com/prebid/prebid-server/pull/3727

We don't allow abrupt renames like this without a transition period. Liftoff can become an alias of vungle and then at some point in a major release liftoff can be removed

update the code so the vungle adapter lists liftoff as an alias.
leave liftoff documentation in place, create vungle docs

Actually if we don't rename adapter explicitly, Xandr will fail on auction with us. Because they require us to have the same name in adapter name and seat name, which all should be vungle.
I'm not sure if alias works for them in such case. I'll give it a try.

We don't allow abrupt renames like this without a transition period. Liftoff can become an alias of vungle and then at some point in a major release liftoff can be removed

update the code so the vungle adapter lists liftoff as an alias.
leave liftoff documentation in place, create vungle docs

@bretg I'm an Engineer from Liftoff, and we are integrating with @PBDMSFT on this adapter for a while.
I'm sure that no other publishers outside of MCG are calling our Prebid-Server adapter today, and I also confirmed with our business side colleagues on this. So it is safe to do the rename, could you please review this PR again?

@Vungle-GordonTian - I'm not sure how you can be so certain that no one else has enabled liftoff. How about a compromise:

you can rename the PBS adapter (since it was already approved). I would really have preferred to not change the original name, but will accept that cat's out of the bag.
you'll add 'liftoff' as an alias to the PBS adapter
you'll add liftoff.md to this docs PR with a new metadata entry of aliasCode: vungle

This way if someone complains to me that we broke their configuration by allowing this rename to take place, we can apologize and give them instructions to replace their YAML file.

@Vungle-GordonTian - I'm not sure how you can be so certain that no one else has enabled liftoff. How about a compromise:

you can rename the PBS adapter (since it was already approved). I would really have preferred to not change the original name, but will accept that cat's out of the bag.
you'll add 'liftoff' as an alias to the PBS adapter
you'll add liftoff.md to this docs PR with a new metadata entry of aliasCode: vungle

This way if someone complains to me that we broke their configuration by allowing this rename to take place, we can apologize and give them instructions to replace their YAML file.

@PBDMSFT Will Xandr work as expected if we use this alias way that @bretg mentioned?

@Vungle-GordonTian We've already made changes on our side to accommodate "vungle". If you add an alias for "liftoff", the adapter name we originally had, it won't hurt anything. Please keep the "vungle" adapter in place though as that change was already released in Prebid Server and updated on our end.

@Vungle-GordonTian We've already made changes on our side to accommodate "vungle". If you add an alias for "liftoff", the adapter name we originally had, it won't hurt anything. Please keep the "vungle" adapter in place though as that change was already released in Prebid Server and updated on our end.

Get it. Then we can go on with our integrating test. I will keep vungle adapter in place. I will add alias as Bretg mentioned simutaneously.


fixes #332 changes in projectlist file to center project cards

fixes #332 The project cards to aligned properly in center
##screenshot##
Before cards

after fix cards

fix width issue some cards width is not equal because of max-w-sm property
##screenshot##

changed max-w-sm to w-96

Thankyou so much man felt good to contribute in your project


emberframing.c: Debugger error/warning in CRC calculation

Hi,

when building libember_slim in debug configuration in VS 2013, the debugger
will raise a runtime warning in the CRC calculcation code:

return (unsigned short)((crc >> 8) ^ _crcTable[(byte)(crc ^ b)]);

The message refers to a possible overflow of "crc ^ b" (unsigned short) when
typecasted to byte.

The code should read like this instead:

return (unsigned short)((crc >> 8) ^ _crcTable[(byte)((crc ^ b) & 0xFF)]);

Thanks
Torben

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 4 Dec 2014 at 2:22

This issue has been fixed with commit 127f061.


Update tweet cell height calculation

Replace old method for tweet cell height calculation with newer.

Hey @tomassliz,
Thank you so much for the pull request! Sorry I didn't merge it, I actually updated the Twitter Kit in the same commit as updating the height calculation method to avoid breaking the app.
Thanks for your understanding, and don't hesitate if you have any suggestions!
Cheers,
Romain


Add more prognostic EDMFX cases to CI

The next step is to make them run longer and not fail...
Closing #2104

bors r+


Blockchain Explorer- Milestone 1

Openblockchain Explorer
Milestone 1
Tasks:

Ported stats page from tnb-analysis to explorer - https://tnbexplorer.com/tnb/stats
Integrated live primary validator and bank APIs at various places - https://tnbexplorer.com/tnb/transactions
Individual account page design - https://www.figma.com/file/LkDMK3NvpVbQjQF45qFOuH/tnbexplorer.com?node-id=54%3A2
Individual account page code - https://tnbexplorer.com/tnb/account/5ad13fd8cc674da7a3ad35426e0fcfe3a3157a044ebda0f54b9b32ee873ea921/
Trace transactions implementation in code - https://tnbexplorer.com/tnb/account/5ad13fd8cc674da7a3ad35426e0fcfe3a3157a044ebda0f54b9b32ee873ea921/trace-transactions
Hired a designer for mobile view screen but the work was not satisfactory - https://www.figma.com/file/XdHCqKeNdP3IyOHvaIWkCz/mobile-page-for-TNBEXPLORER?node-id=0%3A1
Experimented with visualizations via tableau - https://vizyourdata.github.io/javascriptAPI_demo.html
Skill-up of the team in django and react especially towards websockets - https://testdriven.io/courses/taxi-react/
Other discussions on discord and management related work

Objective
Coins
Time spent

Mobile screens designs
30000
~1 week

Javascript based interactive charts in stats page
60000
~2 weeks

Live primary validator and bank APIs at various places
40000
~1 week

Individual account page
50000
~1 week

Tracing of transactions
10000
~2 days

Testnet & backend
30000
~1 week

Management
20000
-

TOTAL
240000

Project wallet address
1dfb0e7dd672032da0d8c29385ba6d22ec9d1134a115cc5596c5e4b69e6fc9a5

Hey @itsnikhil, we are going to have a meeting with govs regarding the standard method to calculate the number of coins for milestones.

@manishram any update on this? it's been more than a week now

Management objective will not be considered.

Milestone 1 approved for 240,000 coins. If you wish to continue on with this project, please submit a milestone 2 proposal using this template! https://github.com/thenewboston-developers/Projects/issues/new?assignees=&labels=Milestone&template=milestone-proposal.md&title=NAME_OF_PROJECT+-+NAME_OF_MILESTONE+-+MILESTONE_NUMBER

Created a separate payout request issue for this milestone.


GUI regions editor

It would be extremely helpful to have a matplotlib region editing interface to add, remove, and reshape regions.  AFAIK, we don't have this now, though some affiliated packages (e.g., https://github.com/astropy/regions/issues/69) provide some of this functionality.  Such editors would be useful for:

Dropping photometry apertures
Creating interactive CLEAN masks (radio application)
Creating serializable "brushing" regions (e.g., for Glue)

The current status of outstanding work on interactive regions is captured in #391.


How to evaluate different Lidar-Data

Hi,
i have a different Lidar data set and I want to classify objects with SECOND. How and in which step can i change the Kitti data to my own data. I have no labels and no images according to the Data.
The training with Kitti has worked
Thank you

Hello,
I have the same problem, I would like to use the pre-trained model to perform inference on arbitrary Lidar data.
Is this possible? Is the data preparation step essential for this to work?
Thanks in advance!

it is possible. Just convert your data that it fits the KITTI-Format (add reflection intesity if necessary). Then replace your data with the data in the KITTI Dataset. The datapreparation steps are essential, because they create GT and remove points outside the visible area of the camera.
For inference put your data in the testfolder and use the train.py -evaluate skript and comment the lines, that are connected to GT. Also change in the Config to kitti_infos_test.pkl.
if you have further questions, feel free to ask them.

Thank you for the reply,
How can I run create_data.py if I don't have any training file?
The script create_data.py gives an error if I don't have the training files or if I miss some .bin files in the velodyne test folder.
Let's say I just have one .bin file on which I want to do inference (it can also be of the kitti dataset, so we eliminate the conversion problem).
Can I do this without having all the files?
Thank you in advance!

just create the whole KITTI-Dataset and replace your files with the files in the Testfolder and use the modified evaluation step. The results (coordinates etc. ) will be stored in the .pkl file.
You only need to replace the .bin files, since the camera data will only be used for indexing and visualization in the viewer

Ok! Thank you for your advice! It's very helpful.
I will update here with the progress of my work.

Hello,
I'm still stuck with the problem because I am using google colab and it's difficult to use all the dataset.
Google colab disk space isn't large enough and if I want to load all the data from google drive it's very slow.
That's why I would prefer to just use a subset of the test set (just 100 .bin files out of 7580) and perform inference on this subset using the pre-trained model.
Is there a way to do this without importing the training set and the other test files?
Thank you in advance!

I'm not shure but i think you have to have to edit the train and val and test txt files. Tere it is defined what files are used for training or inference (test.txt)

Ok, thank you very much! I was able to use just the files I needed by modifying the .txt files located in second.pytorch/second/data/ImageSets/


Scalebar not working properly

Hi guys,
we are currently evaluating the Scalebar from Toolkit. It doesn't seem to be working as expected. First we get the exception "Generic parameter 'V' could not be inferred" when we try to use Scalebar in a view component. Even in the example the same error occurs. When we wrap it with a group, defining the generic parameter with "Scalebar" the exception disappears. But if we do it like in the example that we do not initialize the states like "spatialReference" and "unitsPerPoint", the Scalebar is not shown. If we initialize these states with wgs84 for spatialReference and any value for unitPerPoint the Scalebar appears. When we then change our viewpoint, the Scalebar is going to be updated, but with very incorrect values. You know about this issue?
Best regards
Marvin

Hi Marvin,
Happy to help you get this figured out. The scalebar relies on the spatial reference, and a current units per point and viewpoint value to compute the correct distance. Passing in any value to unitsPerPoint will lead to incorrect values. The correct value for units per point can be obtained by using the onUnitsPerPointChanged modifier on a map view. I can try to give a more detailed suggestion if you're able to post a small snippet of your usage code here.
David

Hi David, thank you for your quick reply. I was able to solve the issue. I seems to be a Swift-UI Issue. I tried to work with a viewmodel and @Published values for the scalar properties. But this leads to incorrect scalebar values. When I do the same with @State like in the example it's working properly. Thanks again!


Add "median" aggregator functionality to Local.Aggregate

In #693 we added all aggregation functions for the janusgraph connector, except a single one: median. This is because I couldn't find any resources on how to do that with Gremlin.
This is the follow-up issue to prevent the other issue from being blocked.
Possible Remedies

more in-depth search
ask external Janusgraph/Gremlin experts

Once we know how to do this, the fix should only be a very small change.

This was actually included in the 0.20.0 release. Closing as complete.


Make sure every key gets updated at some time

When picking a key to update, parcimonie simply picks a random key from the keyring. This way it can happen that certain keys don't get updated for a longe time while other keys get updated multiple times in the same period.
Maybe it is possible to implement a logic that updates every key once before the next round of updates.
I was thinking of storing a set of all keys from the keyring, picking random keys from the set and update a flag in the set when they get updated. When all keys are updated, a new set is generated and so on.
This set needs to be stored persistent so it still exists after a reboot.
For keys that are added to the keyring while a update cycle is still running, the daemon could compare the full set that was used to create the current update cycle and diff it against the actual keyring. Every key that is new gets added to the update set.
The structure of the set could be something simple like
fingerprint:0
fingerprint:1

where 0 or 1 indicate wether the key has or hasn't been update in the current cycle.
Maybe there is a more elegant way to achieve this but I think it would be good to make sure every key gets updated.

This sounds feasible as long as the set is different on each generation, in order to avoid correlation through repeated key refresh order.
I think one simplification could be that the program doesn't remember the whole set of keys, but rather it only keeps a set of keys that it has refreshed. Every time it decides to refresh a new key, it just picks a random one from the keyring that is not in that set, refreshes it, and adds it to the set. Then, when the set contains all keys in the keyring, erase the set and start over. This doesn't require having edge cases for key additions or removals, and enforces the random-ordering property.
I don't see a reason to not do this at least with the set in memory, but persisting the set may have new privacy implications. For example, if the persistent storage directory is in some remote storage (or equivalently, synced with dropbox or whatever), then any write to it will be reflected on the network in a potentially-privacy-disrespecting manner because even if the data is encrypted, the upload pattern would coincide time-wise with key refreshes. Today this leak isn't much of a concern because only a small subset of key refreshes result in disk writes (those that actually bring in new key data). I definitely think persistence should not be the default, and that the setting to control that should come with a big disclaimer.

Although I understand that some keys might not be updated each period (week), I personally like that it's currently a completely random selection. Not sure that I like that each key is "guaranteed" to get updated once per period quite as much. Perhaps the current random selection style is statistically close to "guaranteeing" that each key gets updated at least once per two periods? That's enough for me.
As the time to wait between each key refresh is dependent on the total number of keys N in the keyring, I would guess the number of keys is of less importance -- but has anyone done the math to confirm the probability that a key gets selected (or not) for a low N versus a high N? The answer should say if it's likely that a key might randomly not get updated two periods in a row.

Perhaps there is a way to reduce the chance of a key being selected twice in a period, while keeping some random properties? Say, for a keyring with N keys remembering a list of the N/2 most recently updated keys?
That approach might also be configurable to allow for both random selection with replacement (remember 0) and without replacement (remember N). (Tried to use some statistical terms, but won't pretend I remember enough from university.)

My first thought was picking random keys from the generated set as stated in the first post, but using a set that only contains the already updated keys is more elegant.
The full persistence vs memory persistence is another topic. Maybe the daemon can wait until the computer shuts down and only then write the current set to the persistent storage.
I'll try to do the math for the probability of each key from a set of N keys getting updated in a round of N updates:
There are N^N different combinations how the keys can get updated (N updates per round and N keys to pick from randomly per update). Only N! of these combinations contain every key from the set. So the probability of each key getting updated would be
(N!) / (N^N)

For a set of 10 keys, that would be
10! / (10^10) = 0.00036288 ~= 0.04%

Since N^N grows faster than N!, the probability to update each key per round gets smaller.
I don't know if my approach to this problem is correct, but thats how I remember it from statistics class. It is actually pretty unlikely to update each key in a reasonable amount of time.

Your math is correct, but it's not really showing the whole picture. What it computes is the probability that the current behavior matches the behavior described in the first post, i.e. the probability that today's parcimonie.sh's does a full keyring update in the absolute minimal number of refreshes possible to do so.
I don't think this is an interesting metric to look at. A better way to show the effect of this change would be to estimate how old keys are in the current model.
Let's examine the case of a key k in a keyring of size N. In the current model, the probability of a key being older than 1 refresh is (N-1)/N, i.e. the probability that it was not picked in the last refresh. The probability of a key being older than 2 refreshes is ((N-1)/N) * ((N-1)/N), i.e. the probability that it was not picked in the last refresh and not picked in the refresh before that (which are independent events in the current model since we randomly pick keys with replacement at each refresh).
Thus, generally, the probability of a key being older than r refreshes is ((N-1)/N)^r.
Now recall that the refresh frequency is proportional to N itself, so we need to take this into account in order to come up with a time-based metric. With the default value of 1 week for $targetRefreshTime, that's N expected refreshes per week. This means that the probability of a key being older than $targetRefreshTime is that of being older than N refreshes, which is ((N-1)/N)^N (we just set r = N).
Here's how this looks like for different values of N:
%matplotlib notebook

import pandas as pd
import numpy as np
import matplotlib

from matplotlib import pyplot as plt

d = pd.DataFrame([(((N-1)/N)**N) for N in map(float, range(2, 48))], index=range(2, 48))
p = d.plot()
p.set_xlabel('Keyring size (N)')
p.set_ylabel('Probability of a given key not being refreshed often enough')

This has an upper bound of 0.37; we can thus assert that, in the expected case, 37% keys or less will be older than $targetRefreshTime.
But in practice keys don't actually need refreshing every week. What happens if we care that keys are only refreshed within the last month, approximated by 4 weeks?
%matplotlib notebook

import pandas as pd
import numpy as np
import matplotlib

from matplotlib import pyplot as plt

d = pd.DataFrame([(((N-1)/N)**(4*N)) for N in map(float, range(2, 48))], index=range(2, 48))
p = d.plot()
p.set_xlabel('Keyring size (N)')
p.set_ylabel('Probability of a given key not being refreshed often enough')

So we can assert that 2% keys or less will be older than 4 * $targetRefreshTime, which is about 1 or 2 keys in the average-size keyring, so let's call that negligible.
tl;dr: This change would ensure that about a 37% of a user's keys stay consistently updated within $targetRefreshTime rather than within the current 4 * $targetRefreshTime.
When put in that light, maybe we should just reformulate how the script interprets $targetRefreshTime accordingly, and get essentially the same effect without the potential downsides?

When put in that light, maybe we should just reformulate how the script interprets $targetRefreshTime accordingly, and get essentially the same effect without the potential downsides?

I would, because it would make the setting intuitive. Statistics are not for most people, but everyone will understand a setting of "time after which X% of keys have been refreshed". If X is reasonably high, this also ensures that the fraction of refreshed keys will be basically 1 after double the set time, again something that people will intuitively guess.
Expanding on your math, for any given time, x * $targetRefreshTime the upper limit for the fraction of unsynced keys is 0.37^x, so it's easy to pick a target percentage. Using x = 3yields almost exactly a 95% refresh fraction, so I would redefine$targetRefreshTime` to mean exactly that.


How is the ArchiMate metamodel encoded into the Archi modeler?

How is the ArchiMate metamodel encoded into the Archi modeler? How easy/difficult would be to encode the metamodel for a different visual language for designing software systems?
For example...

Michael

How easy/difficult would be to encode the metamodel for a different visual language for designing software systems?

Hi. It would be impossible.
Archi is specifically an ArchiMate modelling tool. For creating a tool based on a different metamodel, you need to look at a generic framework like Eclipse Sirius,


Also cache analytics.js using a network-first strategy

Library Affected:
sw-google-offline-analytics
Browser & Platform:
all browsers
Issue or Feature Request Description:
Offline analytics only really makes sense if the top-level https://www.google-analytics.com/analytics.js library is also available offline, so that should be cached by the library. I think a network-first strategy is most appropriate.
Special care should be taken to handle the situation in which https://www.google-analytics.com/analytics.js results in a HTTP 307 pointing to a data: URI, as described at https://github.com/GoogleChrome/sw-toolbox/issues/153

This was addressed in #27


Figure out a way to get around ysort-laggs

Yea... YSort. My friend.
https://github.com/godotengine/godot/pull/73813 or a new layer with only the tops

https://github.com/godotengine/godot/issues/74478


Rename runtime components to WindowsAppRuntime

Last of The Great Rename. Runtime artifacts are to be called ...WindowsAppRuntime... not ...WindowsAppSDK... This affects the MSIX packages and DLLs (the project as a whole and build-time artifacts (NuGet, VSIX, etc) are still ...WindowsAppSDK...).
I built WindowsAppRuntime.sln, MrtCore.sln, WindowsAppRuntimeInstall.sln and CreateInstallerTestPackages.sln and ran the tests. All passed except for a few AppLifecycle and PushNotifications tests, but they fail the same in main. @pmpurifoy @aeloros I'll file some bugs.
@huichen123 @axelandrejs  build\Nuspecs\build-nupkg.ps1 lines 112+ mention Microsoft.WindowsAppSDK.pri. Is that dead code? If not, what uses it? Something outside this repo? Was murky so I didn't touch, and seems harmless for now so I'm not planning to hold up the PR for that. Can always be modified in a follow up PR, once we understand how.
@dkbennett FYI updating the package name Microsoft.WindowsAppSDK.Test.InstallerFramework blew out the length (52chars, max=50) so I shortened Installer to Install to fit. Still fits with the installer's lingo (and probably even better, since it's ...Install.exe, not ...Installer.exe). Nothing to do here, just a heads up.
There'll be a matching PR shortly on the Build repo.
This won't be completed until the Aggregator's PR is ready. Unfortunately the changes need to be coordinated manually so I'll wait to submit this one until the other PR's ready, then it's the usual complete this, wait, wait, wait, update the internal PR with the new public build label, check that in, wait, fingers cross, swear, patch, ...

/azp run

/azp run


Refs #21231 -- Backport urllib.parse.parse_qsl() from Python 3.8.

This backports urllib.parse.parse_qsl() from Python 3.8 to replace limited_parse_qsl().
I think there may be a couple of projects using this undocumented function, so I don't know whether we want to mention it in backwards compatibility notes or whether we need to deprecate?
It seems that support for max_num_fields was also patched into Python 3.6.8 and 3.7.2 (bpo-34866), so I don't know whether we even want the backport considering Django's policy on using the latest patch release in a series. That would run the risk that thinks break for people though. Even if we decide to keep it, we should probably use the version available in Python in preference for all versions of Python. What do you think?

Ok. I've pushed a !fixup that removes the fragile string checking on the ValueError exception raised by urllib.parse.parse_qsl(). This only works because we are using the default strict_parsing=False.
I have also added in a second !fixup that strips out the backport entirely. The change to add max_num_fields to urllib.parse.parse_qsl() was released in Python 3.6.8 and 3.7.2 on 24th December 2018. Django has a policy of only supporting the latest patch releases, but this may be deemed too soon - I've added the commit to provide this option should it be preferred at the discretion of one of the fellows.

@felixxm I figured it would be too early, but worth asking. Will wait for Carlton's assessment as you've cc'd him and then remove the !fixup if he concurs.
Were you happy enough with the approach to ValueError → TooManyFieldsSent?

Yep. I don’t see that we need to push here. (I.e. I’d keep the fallback for the now.)

Ok. I've updated this to keep the backport and squashed the other fixup. Should be ready to go.

We should always prefer the standard library version if we have a version that supports max_num_fields, so I changed it to use:
if (3, 6, 8) <= sys.version_info[:3] < (3, 7, 0) or (3, 7, 2) <= sys.version_info[:3]:
    from urllib.parse import parse_qsl
else:
    from django.utils.http import parse_qsl

I've already added a # TODO: on django.utils.http.parse_qsl() that it should be removed when 3.8 is the minimum supported version of Python.

@felixxm I've switched back to using PY38 in the main commit, but added a !fixup using inspect.signature() for consideration. I feel it may be worth looking forward at this point and using the implementation in Python where available. If you feel otherwise, you can drop the !fixup.
@carltongibson I've added another !fixup that pulls in the unit tests I could find in python/cpython. We didn't have this before and the backport is a direct copy-paste from Python itself, but you requested tests so that seemed the most sensible approach. Again, you can drop the !fixup if you have changed your mind.

Ok, cheers Nick. Thanks. I’ll give it another look.

@carltongibson I've added another !fixup that pulls in the unit tests I could find in python/cpython. We didn't have this before and the backport is a direct copy-paste from Python itself, but you requested tests so that seemed the most sensible approach. Again, you can drop the !fixup if you have changed your mind.

Thanks for this @pope1ni. I think we need the tests, even if it is just copy and paste, so 👍

I couldn't find any projects on GitHub using it but, a deprecation shim would be quite light-weight. (It can just map to parse_qsl I think.)

I've added another !fixup with a backward incompatibility note pointing to the function in the standard library. I think a whole shim for this which would need a function (due to the different argument name), a deprecation warning and extra tests for both parts of that is a bit excessive for an undocumented function removal for which the resolution is straightforward.
The only reason for someone using this is if they're trying to parse raw query strings themselves and they knew that this function provided them with a security fix that the standard library version didn't at the time. I think this is very few people, if any.

@carltongibson Rebased. Is there anything else you'd like me to do here?

Rebased targeting 3.2.

@felixxm I think @carltongibson wanted your opinion on how we do the compatibility import: https://github.com/django/django/pull/12017#discussion_r409514541.

Hey @pope1ni. Sorry for the hold-up here. You got bumped because of the feature freeze.  Thank you for your patience. It's currently on the look at in the lull after all the release blockers from 3.1 final turn up list. 😀

The only reason for someone using this is if they're trying to parse raw query strings themselves and they knew that this function provided them with a security fix that the standard library version didn't at the time. I think this is very few people, if any.

This point is noted. Main issue here (from the review POV) is having the mental space to think through whether we can just note it as a breaking change (which maybe we could, yes...)

Thanks!


BOTTLEROCKET_VERSION is null

What happened:
export BOTTLEROCKET_VERSION=$(curl -sL https://raw.githubusercontent.com/aws/eks-anywhere-build-tooling/$BUILD_TOOLING_COMMIT/projects/kubernetes-sigs/image-builder/BOTTLEROCKET_RELEASES | yq ".$(echo $KUBEVERSION | tr '.' '-').$BOTTLEROCKET_IMAGE_FORMAT-release-version")

echo $BOTTLEROCKET_VERSION

https://anywhere.eks.amazonaws.com/docs/osmgmt/artifacts/#download-bottlerocket-node-images
What you expected to happen:
echo $BOTTLEROCKET_VERSION should print bottlerocket image version. something wrong with the yq command.
How to reproduce it (as minimally and precisely as possible):
Follow instruction from the below url and try to build OVA for any kubernetes version or specifically 1.28 or 1.30
https://anywhere.eks.amazonaws.com/docs/osmgmt/artifacts/#download-bottlerocket-node-images
Anything else we need to know?:
Fix:
Broken:
BUNDLE_MANIFEST_URL=$(curl -sL https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml | yq ".spec.releases[] | select(.version==\"$EKSA_RELEASE_VERSION\").bundleManifestUrl")
BUILD_TOOLING_COMMIT=$(curl -s $BUNDLE_MANIFEST_URL | yq ".spec.versionsBundles[0].eksD.gitCommit")
export BOTTLEROCKET_VERSION=$(curl -sL https://raw.githubusercontent.com/aws/eks-anywhere-build-tooling/$BUILD_TOOLING_COMMIT/projects/kubernetes-sigs/image-builder/BOTTLEROCKET_RELEASES | yq ".$(echo $KUBEVERSION | tr '.' '-').$BOTTLEROCKET_IMAGE_FORMAT-release-version")

Working:
BUNDLE_MANIFEST_URL=$(curl -sL https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml | yq ".spec.releases[] | select(.version==\"$EKSA_RELEASE_VERSION\").bundleManifestUrl")
BUILD_TOOLING_COMMIT=$(curl -s $BUNDLE_MANIFEST_URL | yq ".spec.versionsBundles[0].eksD.gitCommit")
export BOTTLEROCKET_VERSION=$(curl -sL https://raw.githubusercontent.com/aws/eks-anywhere-build-tooling/$BUILD_TOOLING_COMMIT/projects/kubernetes-sigs/image-builder/BOTTLEROCKET_RELEASES | yq ".$(echo $KUBEVERSION | tr '.' '-').ami-release-version")

Environment:

EKS Anywhere Release:

$ sudo eksctl anywhere version
Version: v0.20.5
Release Manifest URL: https://anywhere-assets.eks.amazonaws.com/releases/eks-a/manifest.yaml
Bundle Manifest URL: https://anywhere-assets.eks.amazonaws.com/releases/bundles/75/manifest.yaml

EKS Distro Release:

It's only null if a value doesn't exist for that version right?


rtt: restore the proper current rendertarget after the subgraph has been rendered

Please test this with all the backends

Even with render to texture, you shouldn't have to use LOAD_OP_LOAD.
You can first render to texture, then render the texture to the screen.

"- the RTT 1 node detects that it needs to allocate two rendertargets,
one with LOAD_OP=CLEAR and one with LOAD_OP=LOAD because there are
two separate render passes (one for each render)"
This terminology is confusing.  Let's use terminology consistent with Vulkan.
A rendertarget doesn't have load ops and store ops, a renderpass does.
A rendertarget is just the render destination (e.g. texture or framebuffer)?
Also, we don't need multiple render passes because we have multiple render nodes, they can still share the same render pass.
We need multiple render passes if they have different configurations, e.g. drawing to a different destination format, etc.

From my perspective I would prefer if we first optimize the renderpass logic before merging to master.

"add loach_attachment_nested test"
typo (load attachment)

From my perspective I would prefer if we first optimize the renderpass logic before merging to master.

This commit fixes a regression and needs to go to master. Optimizing the renderpass logic is another topic and won't be impacted by this commit.

"- the RTT 1 node detects that it needs to allocate two rendertargets,
one with LOAD_OP=CLEAR and one with LOAD_OP=LOAD because there are
two separate render passes (one for each render)"
This terminology is confusing. Let's use terminology consistent with Vulkan.

I used this terminology to reflect what the code do and our current abstraction use a rendertarget object (which mixes the notion of framebufer+renderpass). This abstraction is not nice but I plan to split it into framebuffer + renderpass (I delayed this split to avoid causing too much conflicts with the upcoming backends branches).

A rendertarget doesn't have load ops and store ops, a renderpass does.
A rendertarget is just the render destination (e.g. texture or framebuffer)?

At the low-level graphics level (Vulkan, Metal, DX) yes. The commit description is talking about the current abstraction (the rendertarget struct). I will reword the commit description to make it more explicit.

Also, we don't need multiple render passes because we have multiple render nodes, they can still share the same render pass.
We need multiple render passes if they have different configurations, e.g. drawing to a different destination format, etc.

Also, we don't need multiple render passes because we have multiple render nodes, they can still share the same render pass.
We need multiple render passes if they have different configurations, e.g. drawing to a different destination format, etc.

In this case we have multiple render pass because they have different load/store operations.

"add loach_attachment_nested test"
typo (load attachment)

Fixed.

The commit description has been updated with the following sentence added:
    The terminology "rendertarget" used in the following description refers
    the ngli rendertarget structure (which aggregates a framebuffer and a
    renderpass and their respective configurations).

Even with render to texture, you shouldn't have to use LOAD_OP_LOAD.
You can first render to texture, then render the texture to the screen.

In theory yes but unfortunately the main user of nodegl is using this pattern. We can probably reorder internally the the graphics operations to avoid this scenario but that will require some work. IMHO, the right solution is to enforce this at the API level (while this will require probably less work on our side, it will require a lot of work in the codebase of our main user).


[Question] About mp3 input files

I have MP3 files at 128  kb/s like
  Metadata:
    encoder         : Lavf58.20.100
  Duration: 00:02:22.11, start: 0.025057, bitrate: 128 kb/s
    Stream #0:0: Audio: mp3, 44100 Hz, stereo, fltp, 128 kb/s
    Metadata:
      encoder         : Lavc58.35

and I therefore converto to wav so that I get the a 22050 Hz file as for the dataset specification:
ffmpeg -i file.mp3 -acodec pcm_s16le -ar 22050 file.wav
Metadata:
    encoder         : Lavf58.12.100
  Duration: 00:02:22.06, bitrate: 705 kb/s
    Stream #0:0: Audio: pcm_s16le ([1][0][0][0] / 0x0001), 22050 Hz, 2 channels, s16, 705 kb/s

The separation works, my guess is if this is the best approach from the given mp3 sample rate and bit rate.
Thank you.

Is this a documentation issue? If yes, please provide a pointer where to extend the documenation.

umx and umxhq are trained on 44100 kHz, so I would suggest to not resample the file. In any case test.py is automatically doing this resampling. We plan to support mp3s by using torchaudio to load the test files. So conversion would be just temporarily.

@faroit thank you.

Well if it makes sense it could be some more docs about mp3 input.
Ok, in the meanwhile I will use the conversion.


Bugfix - move all javelins to 2-tick

The wiki lists most of the javelins as 1-tick creation, but all that I tested in game (bronze, steel, addy, rune) were actually 2-tick.
This PR moves all of the javelins to be 2-tick.

This will close ##22


[material-ui] Component import suggestion not appearing in VS Code

Steps to reproduce

Current behavior
when trying to use component from MUI I used to get suggestion to auto import the component, until yesterday, I couldn't get no suggestion when working with *.jsx files.
Expected behavior
when typing <Button its should show me an suggestion to auto import the component.
Context
I just started facing this problem yesterday, Its was working fine, I created a .tsx file and its worked fine and its showed me the suggestion of <Button but when I create .jsx file, I don't get no suggestion, I deleted all the typescript files from the MUI module, then I started getting suggestion in javascript file, is this issue related to vsode or the problem is with the typescript files in mui.

  Output from `npx @mui/envinfo` goes here.

Having this same issue right now going insane trying to figure out if I broke something in VS Code or if somehow @mui/material is broken somehow I cant do any auto completion as I was before recent using for instance <Box (Auto complete to add import and finish the component but switching the file extension to tsx fixes it fully but JS and JSX is fully broken have uninstalled reinstalled a bunch of plugins attempted to switch the layout of my config file and many more things for instance here is the issue I have below with the  element...

But if I try to import a icon from the icon package it works fine:

But when trying to even do a simple autocomplete on the import itself:

Not sure how this happened I tried basically everything I could find to fix this and I dont think I made it any better closest I got was simply changing to .tsx instead which resulted in the same functionality as the OP:

Any ideas? I have spent the past ~6hrs trying to fix this even reverting my project to 1 month ago when everything was working fine and still not way to fix this 😞

@lyricalcasanova we got exactly the same issue, just 3 days ago everything was working fine, and I am really sure I never changed nothing in my settings.

@AlCo2 You mentioned in your original post you somehow got around this issue by doing the following?

I created a .tsx file and its worked fine and its showed me the suggestion of <Button but when I create .jsx file, I don't get no suggestion, I deleted all the typescript files from the MUI module, then I started getting suggestion in javascript file, is this issue related to vsode or the problem is with the typescript files in mui.

Can you maybe elaborate on what which TS files you removed?
I attempted to recreate this by just deleting all the TS files in ONLY the Box component and the Button component directories but I had no different result?

same issue

I had the same issue (@mui/material ^5.13.4)

Looks like the issue came from VS Code latest version, I downgraded it to 1.87.2 and my suggestions are back!
You should probably disable the auto-update from VS Code as well, until the issue is resolved

Looks like the issue came from VS Code latest version, I downgraded it to 1.87.2 and my suggestions are back!

First, you need to disable the auto-update from VS Code, until the issue is resolved, to prevent the downgrade not get updated again once you restart the IDE. File > Preferences > Settings search for update, change update mode to none
Then, to downgrade, you can download and install from the website, it will override the current version: https://code.visualstudio.com/updates/v1_87

This worked for me too.

I am happy we found a workaround for now, at least I can continue working normally now!! 👍
One question has anyone found the actual issue in the VS Code repo?
If so mention it here so we can get this resolved quickly,
It's not ideal for your IDE to be a dependency for your packages, I would love to try out some of the new features in VS Code soon and not be stuck on 1.87.2 for too long

@AlCo2 I provided an updated / edited version of your original post to copy and paste so others find the solution easily. Optionally I would suggest changing the title of this issue to: "VS Code v1.88 Breaks JS/JSX Import Suggestions (Workaround)"

Edited/Updated OP Raw
**UPDATE: This seems to be a issue with VS Code Version 1.88 and is not present in Version 1.87.2
[Thanks to @thucne for providing a workaround](https://github.com/mui/material-ui/issues/41802#issuecomment-2047977557)** 👍

### Steps to reproduce
JS / JSX (Auto imports broken)
<img alt="Capture" width="960" src="https://private-user-images.githubusercontent.com/109082926/320297815-a77a163b-f66c-4297-a3d5-5cd5a3a2ae00.PNG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTI3ODMwMjIsIm5iZiI6MTcxMjc4MjcyMiwicGF0aCI6Ii8xMDkwODI5MjYvMzIwMjk3ODE1LWE3N2ExNjNiLWY2NmMtNDI5Ny1hM2Q1LTVjZDVhM2EyYWUwMC5QTkc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNDEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDQxMFQyMDU4NDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mMGYyMGVlNjRlM2ZkZTQxODNkZDA0MGUxYTA3NGQwMmJkOWE1ODg2MDZhY2IzN2E4MTg3MDE3ZDE3MTJmYTI2JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.T9vokGk6W1BTnH1yBSl4bYzK609_Pxx2lnAzfNELdY8">
TS / TSX (Works as expected)
<img alt="Capture2" width="960" src="https://private-user-images.githubusercontent.com/109082926/320297823-923bac80-6e03-4763-96d5-c4f30d10b1e0.PNG?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTI3ODMwMjIsIm5iZiI6MTcxMjc4MjcyMiwicGF0aCI6Ii8xMDkwODI5MjYvMzIwMjk3ODIzLTkyM2JhYzgwLTZlMDMtNDc2My05NmQ1LWM0ZjMwZDEwYjFlMC5QTkc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNDEwJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDQxMFQyMDU4NDJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kNWZhNjMxZGFmZGZjYjgyMTUzODY2NjlhZWFmNWFjMjcwOGQwYzQ2NDExN2Y4NTU3ZTQ1ZjJhZTg5OWVlMzVkJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.CcxctFyakat8o_JUdDg4ZAjwDHJhbepRb3EuLs7L_hE">
### Current behavior
when trying to use components from MUI I used to get suggestion to auto import the component, until yesterday, I couldn't get any suggestion when working with `*.js` or `*.jsx` files.

### Expected behavior
when typing `<Button` its should show a suggestion to auto import the component.

### Context
I just started facing this problem yesterday, it was working fine, I created a `.tsx` file and it worked fine and showed the suggestion for `<Button` but in *.js or *.jsx files, I don't get any suggestions.

**UPDATE: This seems to be a issue with VS Code Version 1.88 and is not present in Version 1.87.2
[Thanks to @thucne for providing a workaround](https://github.com/mui/material-ui/issues/41802#issuecomment-2047977557)** 👍

Confirmed there is a workaround that does not involve downgrading from the current version
Simply install this extension and imports will start magically working again
https://marketplace.visualstudio.com/items?itemName=ms-vscode.vscode-typescript-next


[Problem] Build a Grid: Android Basics with Compose

URL of codelab
https://developer.android.com/codelabs/basic-android-kotlin-compose-practice-grid?
In which task and step of the codelab can this issue be found?
4 - Data Source, step -> Create an empty file called DataSource.kt. Copy the following code into the file:
Describe the problem
It doesn't say where to create the file. When I looked in the solution code file structure on github I noticed they placed the file in a new directory named "data". Therefore I created the directory where i found it and created the file inside it, but after i pasted the code in the file it just gave me 29 errors.
I simply could be doing something wrong or I may have overlooked something simple.
I hope someone can tell me what I need to do and I hope this issue will be corrected in the near future

@JeffreyHuig
Hey Jeffrey, could you please send us the DataSource.kt file, that is giving you the error?
Please send the errors you are encountering also.

my mistake i didn't realise it was a practise codelab instead of a follow instructions codelab.
I will close this problem and thank you for replying after a long time


Request: Arrows, Fn, Del, Esc, and Ctrl

I love this little KB. Would like to see the following changes/additions over USB:
Change: Right Shift + wasd = Arrow keys
Change: Left Shift + Right Shift = Caps Lock
Add: SYM + wersdfzxc~ (1-0) = F1-F10
Add: Alt + Backspace = Del
Add: Left Shift + mic/~ = Esc
Add: One of the four top row buttons as Ctrl

Hi - I'd give it a go yourself. I've just managed it. See https://github.com/solderparty/i2c_puppet/issues/23


Updated guide several times with corrected steps or added info

Hmm, this has a lot of changes that I think I've already merged.. you may need to pull from the upstream branch to get your branch looking close to it. I don't think you've made 20 more commits since the last merge.

I'm going to close this pull request.. looking at the changes you've been making lately you really need to merge in my changes before you continue working. This pull request would result in a really messy merge because of the difference between our branches.


Session dot notation and Response setExpires()

Laravel Version: 5.3.30
PHP Version: 7.0
Database Driver & Version:

Description:

Session with dot notation
session()->exists($key,$value);
session()->has($key,$value);
IT PRODUCE WRONG VALUE WHEN DOT NOTATION ARRAY USED
Response setExpires() TimeZone can be from config timezone rather GLOBAL UTC timezone
Steps To Reproduce:
session()->exists('main.one',$value);
session()->has('main.one',$value);
$response->setExpires($time)

5.3 is not supported anymore, please upgrade.


Fix broken link and typos

Summary
Fix of broken link to community tutorials in the README.md and other typos.
Details and comments
Link to community tutorials was not working causing confusion for me and others.

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


feat: preCloseBundle hook

Description
Add a new preCloseBundle hook to allow run build plugins hooks between Rollup writeBundle and closeBundle hooks.
I changed also scripts/patchCJS.ts module to allow build in Windows: I just change process.exit() call with process.exit(0).
Additional context

Trying to integrate with SvelteKit the vite-plugin-pwa we have found a problem about a race condition using both plugins with Vite 3.
SvelteKit uses the writeBundle to call the prerender process (SSG). In the closeBundle hook, it calls the adapter logic, the adapter gets the prerender output and copy the content to the adapter output folder (it can do more things).
vite-plugin-pwa uses closeBundle hook in its build plugin to generate the service worker, it has enforce: ' post', and so will be called by Vite/Rollup after SvelteKit closeBundle hook.
We need to invert the closeBundle hook call, that's, vite-plugin-pwa first and then SvelteKit`.
We can reverse the order just changing the vite-plugin-pwa build plugin with enforce: 'pre', but then we have a race condition: since the closeBundle hook will be called in parallel, both plugins need to be called in a sequential order; why? because the adapter needs to copy also the service worker generated by the vite-plugin-pwa build plugin.
Can we move the vite-plugin-pwa build plugin to the writeBundle hook: the answer is no; the vite-plugin-pwa will need the prerender output, and so we have the another race condition, since SvelteKit and vite-plugin-pwa build plugin will run in parallel.

What is the purpose of this pull request?

[ ] Bug fix
[x] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines.
[x] Read the Pull Request Guidelines and follow the Commit Convention.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Ideally, include relevant tests that fail without this PR but pass with it.

sorry: wrong changelist selected in my IDE, fixing lint

the problem this solves is basically that two plugins both use parallel hooks but these hooks depend on each other.
Introducing a new hook in between solves this particular issue, but it would need more discussion, documentation and comes with a lot of added maintenance/testing and risks of incompatibility with future updates to rollup, so i don't think this would be a great addition in it's current form.
Alternative suggestions (some of which already have been discussed in chat):
1) the plugins depending on each other find a way to signal each other via plugin.api
e.g. plugin-a offers plugin.api.on('someevent', ()=>{})  and plugin-b goes plugins.find(p=>p.name === 'plugin-b')?.api.on('someevent',()=>{resolvePromiseYourHookWaitsOn}
2) enforce 'pre' and 'post' in vite are changed to also apply to parallel hook execution
Instead of running all hooks in parallel it would first run all 'pre' hooks in parallel, then the regular hooks and then 'post' hooks.
This is essentially a more generic and less invasive option as is gives every parallel hook a 'pre' and 'post' phase instead of just adding one extra hook in between the two that are causing the root issue this PR is trying to tackle.
3) use a separate vite plugin to control the execution of parallel hooks
This is addmittedly a hackish solution, but gives you total control without vite changing anything. A separate plugin vite-plugin-hook-execution-order can be used to change the plugin hooks at config time.
Eg. rename all plugin.closeBundle to plugin._closeBundle, register a single closeBundle hook that awaits on each of plugin._closeBundle in the order you need.
There are multiple ways to implement this, it could be used to implement the phased parallel logic outlined in 2) outside of vite core, receive custom configuration so that users can change the order as needed, or be supplied with hardcoded sorting by the plugin that relies on a particular order.
--
This comment is not meant to disagree with adding new hook(s) in general, just that doing so requires more up front discussion and presentation of usecases. I guess prerendering in particular isn't something that rollup had in mind when it was designing it's hooks, so new ones may be warranted at some point if that area is something vite wants to cover on top of bundling itself.

This PR is about the sequential plugin hack, I just renamed it so it doesn't sound drastic ;) .
I guess Rollup should add configurable hooks, points 2) and 3) and this PR have the same problem, we need to hack Rollup.
Point 3) I think it is almost impossible to implement it in the current state


Not able to open png files

Screenshot%202024-07-27%20203106.png. Detail: File seems to be binary and cannot be opened as text

Images are not supported yet. But now (in Insiders) we show a nicer error message and ignore it instead of just failing like this.


Support declaring a dependency version as strict

Context
Often, a dependency cannot easily be upgraded. For example, if a component depends on MyLibrary version 4.0.0, it's unlikely that it would work correctly on MyLibrary version 5.0.0, because MyLibrary follows semantic versioning and that 5 is binary incompatible with 4. However, traditional dependency resolution supports upgrading dependency versions. This means that if a transitive dependency pulls in a more recent version, it will result in the dependency version 4 being upgraded to 5. Another common use case is "this library MUST be used with this other". For example, the api and implementation of a dependency are bound, and must come with the very same version number.
Proposed solution
What we propose here is a way to specify that a dependency version is strict. This means that:

if no other dependency on the same module is found transitively, then the version is selected
if another dependency on the same module is found, and that the selector for this version is compatible with the strict one, the strict version is selected
in all other cases, fail

This means, in particular, that:

if a dependency on version 15 is strict, and that a transitive dependency brings version 17, the build should fail
if a dependency on version [15,20] is strict, and that a transitive dependency brings version 17, then version 17 is selected (because it's compatible)
if a first-level dependency says 17, but a transitive dependency says strictly 15, then the build fails
if a first-level dependency says 17, but a transitive dependency says 15 (not strict), then the 17 version is used

We will not downgrade dependencies (in particular for the latter case), because dependency management as it exists now is all about assuming backwards compatibility. In other words, we can assume that if you upgrade from 15 to 17, things are going to work fine, but not the other way around. This story is precisely about this assumption being false, and providing a way to fix it.
This differs from the existing failOnConflict() flag in the sense that this is specific to a dependency, while failOnConflict() would fail whatever version breaks.
Non-goals

This story doesn't explain how to solve the conflict. It's likely that if you have such a conflict, you have to think about how to solve it because you have 2 dependencies that disagree on something that is supposed to be strict (at least for one of the members). Typical resolution can always happen using the resolutionStrategy.eachDependency block.
The strict constraint will not be published (yet). This belongs to a subsequent story. It means that it will work within a multi-project Gradle build for now, but not as soon as a dependency is published.

Implementation options
The force flag that exists already on dependencies also influences how dependencies are resolved. However, it only applies on first-level dependencies. This behavior is inherited from Ivy's force flag, and exposed to the Gradle DSL. However, instead of adding another strict flag that would conflict with the force flag, we recommend to:

deprecate the force flag
introduce a new ForceMode enum that would have 3 possible values:
** soft: would allow a dependency version to be upgraded, as it is typically using the latest version conflict resolution strategy. This is the default.
** force: would behave like force=true today, by forcing the version of first-level dependencies, unless a transitive dependency is strict
** strict: would implement the strict strategy described in this ticket.

In terms of DSL, this "flag" could live where the force flag is seen today. So instead of:
dependencies {
   implementation('org:foo:1.0') {
     force = true // now deprecated
   }
}

we would write:
dependencies {
   implementation('org:foo:1.0') {
     forceMode = ForceMode.force // direct-dependency forcing strategy
   }
}

or
dependencies {
   implementation('org:foo:1.0') {
     forceMode = ForceMode.strict // strict dependency as described in this ticket
   }
}

Any better name than forceMode is very welcome.
Related work
This could serve as the basis for both "recommendations" and "platforms" implementation. One could see a Maven BOM (bill of materials) as a set of recommended versions. That is to say, if a dependency onto a component is found, we should use the version recommended in the BOM. However if a transitive dependency disagrees, it may be upgraded. But, one could also import a BOM as a "platform" requirement, in which case we could use strict dependencies here: if a dependency onto a module is found, then we must use the version found in the BOM, or fail.
This is WIP spec

It would be good to start with the use cases before designing the implementation. That is, start with the concrete reasons why you might want stricter matching.

The most common use case is: As the author of a library you already know that it won't work with anything higher than the given version. I.e. you've already tried it and it failed. Thus you want Gradle to fail if conflict resolution would upgrade it.
Another use case would be that you want to model a "platform", i.e. you want to deploy to some specific application server and this server provides a couple of libraries in fixed versions. Any attempt to upgrade these versions should result in a build failure, as they wouldn't match the deployment target.
A related concept would be for a publisher to be able to say "I break APIs on major releases, so resolution should fail if a dependency on me is upgraded beyond a major version boundary". Even with that capability, strict dependencies can still be useful to solve the case where a consumer needs to narrow the constraint down even further, because the producer didn't think of some side-effect that the consumer depended on.

I'd like to consider other ways to model this than as an extension to force, but something more like a true 'compatibility constraint'.
So instead of saying "I strictly depend on v1.1" you'd say 2 things: "I prefer v1.1" and "I am only compatible with v1.1". This might more easily be adapted to other use cases like semantic versioning, where you would say "I prefer 1.0.0, and I am only compatible with versions in the range [1.1.0, 2.0.0)".

Yes, this is what I thought when working on publishing steps. It clearly looks like a compatibility constraint. Do you have an idea what it would look like in practice?

Another way to model this would be "I'm compatible with [1.0, 3.0)" + "I'm incompatible with [3.0, )". I'd still consider it valuable to have a concise way of saying both these things at once though.

@bigdaz I'd consider semantic versioning as something that belongs on the producer, not the consumer. I.e. "foo:1.1" would have metadata saying "You can safely replace me with [1.1, 2.0)".

@melix as far as concrete syntax would go, here's one idea:
constraints {
  incompatibleWith("com.foo:bar:3.0")
  recommend("com.foo:bar:2.1")
}

A Dependency might just be a special kind of constraint. I'm not even sure I like the word constraint yet, it's just a placeholder I invented until we come up with something better :)

Ok if we step back a bit, it's a dependency declaration. A typical dependency says:

group: org
name: bar
version: 1.0

However, we want to soften or harden constraints on the dependency version. One way to do it today is to say:

version: [1.0, 2.0)

However, it doesn't prevent the dependency from being upgraded, because "version" implies "preferred version". It will not let us fail depending on the conflicts. So we need a richer model, which may imply that "version" alone is not enough (it's the requested version)

I'm not sure I like:

incompatibleWith("com.foo:bar:3.0")

does it even make sense? This kind of information tends to be dynamic. At a fixed point in time you only know which versions you are compatible with.

I think explicit incompatibility makes sense. It would allow you to attach a proper reason to that constraint for instance. E.g. "This version has a bug that breaks us and which was fixed in the next patch release". Or "I'm incompatible with this component in general, please fail if it is in the graph".

So here are three ways one could express this kind of stricter matching. Each of them has something going for it:
dependencies {
  implementation ("guava:[15, 17]") {
    //this is the current proposal, it's very simple to understand
    strict = true
  }
}

or
dependencies {
  implementation "guava:[15, 17]")
}
constraints {
  //We want incompatibility constraints for other reasons too, so this might supersede "strict"
  incompatibleWith "guava:[17, )"
}

or even
dependencies {
  implementation ("guava:17") { //treat the current "version" field as a preference
    //match strictly against this new, Gradle-only information
    compatibleVersions = "[15, 17]"
  }
}

Doc for further discussion: https://docs.google.com/document/d/1iwXPktvQbVFPsEyyiLzEyS6TinmwFExZTLS0rkk_DY4/edit#

We should try really hard to not use boolean flags and a string here, as we want a richer language than just "strict" (whatever that is). Instead, we want to model these constraints as strongly typed component selectors (or component constraints if you like).
Currently, a dependency declaration has-a single version selector. We have the following types:
version='x' means:

prefer x
accept anything >x, must not use anything <x

`version='[x,y]' means:

prefer the latest version >=x and < y
accept anything >=x, must not use anything < x

version='latest.x' means:

prefer the latest version with status x.
accept anything > latest version with status x, must not use anything earlier.

x+ does string prefix matching which doesn't mean anything useful, but that's another issue.
For the use cases listed in the description, what we want is a way to express the following constraints:
"I require x", which means:

prefer x
accept x, must not use anything != x

"I require anything from x up to y" which means:

prefer the latest version >=x and <y
accept anything >=x and <y, must not use anything = y

One option is to simply provide factory methods for these 2 constraints:
dependencies {
   implementation group: 'abc', module: 'somelib', version: requireVersion('x')
   implementation group: 'abc', module: 'somelib', version: requireVersionIn('x', 'y')
   implementation ('abc:someLib') {
        version = requireVersion('x')
   }
}

These constraints are really just composites that compose up some other simpler constraints. We have some other use cases coming up that require these simpler constraints:

"I prefer x" and "I prefer from x up to y", used in addition to some other constraints.
"must not use x" and "must not use x up to y", used in addition to some other constraints.

So another approach is to provide factory methods for the simple constraints and ways to compose them. The constraints we have are:

accept(p) where p is a predicate that matches component metadata (not a "constraint"). Any component instance that matches the predicate is accepted. Does not express an opinion about preference.
prefer(p) where p is a predicate that matches component metadata. Any component instance that matches the predicate is preferred and implicitly accepted.
both(a, b) where a and b are constraints (not "predicates"), which accepts the intersection of both a and b and prefers the intersection of both a and b.

The predicates we have are something like:

'x' which matches component with version x only.
various ranges, eg '[x,y]' which matches any component with version in the given range.
latest(p) which matches the latest version of components that match predicate p.
not(p).
anyWithStatus('x'), which matches any component with status >= 'x'
anyWithVersionStartingWith('x'), which I'd be happy to see disappear.
later, anyWithAttribute(x, y), which matches any component whose x attribute is compatible with value y.

Everything else is just combinations of this:

version='x' == both(accept('x'), prefer('x'))
version='[x,y] == both(accept('[x,]'), prefer(latest('[x,y]'))
"I require x" == prefer('x')
"I prefer from x up to y and I don't work with z" == both(prefer('[x,y]), accept(not('z'))

And so on.

Sounds like a good direction to go. How about we start with require(p) and later add the other methods like prefer() and both() (or and()).

@melix We will need some release notes and documentation for this feature

Shouldn't we wait until we have an end-to-end story? From DSL to resolving?

Yeah I guess we haven't really discussed how we plan to 'release' this functionality. I suppose developing in 'stealth mode' might be fine for now.
Would be be fine with VersionConstraint being part of our DSL but not announcing it for 4.4?

Yup.

Closing as delivered in #3305


issue where some sites not working on PC browser but working on android.

In two or three RSS feeds I am getting errors, and it hasnt downloaded the feed for a couple of months, where it was working fine before. But this is only happening on two Windows PC's (using firefox latest updates, OS win 10 and 11). Whereas on my android (Feeder app) the sites work fine with exactly the same OPML imported between all three devices. About two months ago they all worked perfectly and I have not changed anything in the meantime. Since the problem began I have left the Win 10 pc as-is and mucked about with the Win 11 Commafeed in an attempt to fix the issue. Setting up API key and things like that. Nothing has worked. Wierdly there is occasions a single feed might appear one day on any device, but then nothing again.
The various errors I see are:
"'304 - not modified' http code received"
"Generate an API key in your profile first."
"eTagHeader is the same"
I assume my Twitter RSS feed has issues due to Mr Musk changing the rules of access (but also sporadically works), but it occurred at the same time that it stopped working with some of the others, and Twitter feeds actually go red sometimes, while the others just don't work (on PCs, Twitter also works fine on Android Feeder app). But I get more info with the Twitter feed issues, which is using rsshub.app to pull the feeds and was working perfectly before, but here are the PC error messages:
"Unable to refresh feed https://rsshub.app/twitter/user/username/readable=1&authorNameBold=1&showQuotedAuthorAvatarInDesc=1&showEmojiForRetweetAndReply=1&addLinkForPics=1&showTimestampInDescription=1&showQuotedInTitle=1&heightOfPics=150 : status code: 404, reason phrase: Server returned HTTP error code 404"
and the message "Generate an API key in your profile first."
I have tried rebuilding the database on the Win 11 machine but it didnt make a difference.
My app versions of Commafeed:
Android, Feeder app is vers 2.4.18
Win 10 & 11, Commafeed is version 3.5.0 (84626e1)
Any suggestions for resolving this would be appreciated.

ah... the old "update to the latest version" trick solved it. apologies for not doing that first. just Twitter still not working but I presume Sir Musk of Elon is behind that.

just Twitter still not working but I presume Sir Musk of Elon is behind that.

@mdkberry If RSSHub's Twitter feeds don't work, you can try nitter feeds, there are multiple instances.
Examples:

https://nitter.unixfox.eu/elonmusk/rss
https://nitter.unixfox.eu/elonmusk/with_replies/rss
https://nitter.unixfox.eu/elonmusk/media/rss


'str' object has no attribute 'COOKIES' when using django-honeypot {% extends "app/base.html" %}

When using this package with django-honeypot (middleware to add honeypot to all forms) and customizing the honeypot_error.html page by using {% extends "app/base.html" %} I get this error: 'str' object has no attribute 'COOKIES'.
cookie_consent/util.py in get_cookie_dict_from_request
Django debug when true is highlighting this line:
{% not_accepted_or_declined_cookie_groups request as cookie_groups %}
https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/util.py#L36
https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/util.py#L53
https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/templatetags/cookie_consent_tags.py#L63
https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/util.py#L134
https://github.com/bmihelac/django-cookie-consent/blob/master/cookie_consent/util.py#L136
Honeypot Related Stuff shown in django debug true:
https://github.com/jamesturk/django-honeypot/blob/master/honeypot/middleware.py#L34
https://github.com/jamesturk/django-honeypot/blob/master/honeypot/decorators.py#L30
This error does not happen when I take out the {% extends "app/base.html" %} of honeypot_error.html. Not a big deal if this does not get fixed, but something to be aware of.
Let me know if it is a django-cookie-consent issue or a django-honeypot issue so I could put the issue on django-honeypot if it is more related to them.

Just realized this is a duplicate of the other issue! Sorry!


add PodDisruptionBudget to otel-operator

hello,
with this PR I'd like to introduce PodDisruptionBudget configuration to otel-operator itself.

@avoidik thanks for your contribution. Pls bump the chart version and run make generate-examples


Nanopore reads that have been double basecalled

Hello all,
I am currently trying to use nanopolish on some canu assemblies. However, looking back at the Metrichor basecalled reads I realized that some of my reads were double basecalled, one from MinKNOW and one from Metrichor. Knowing that nanopolish uses the original reads to "polish" the assembly would this double basecall become an issue? Thank you for your time.
Best,
Alex

Hi Alex,
If you use nanopolish extract to convert the fast5 files to fasta, it should be ok.
Jared

Hello Jared,
Thank you for the quick input, we will go ahead and try it. I do have one more question, is nanopolish compatible with the new R9.4 chemistry?
Best,
Alex

Hi Alex,
The 0.6-dev branch supports R9.4 reads. If you check that branch out it should work on your reads. Note that the 0.6-dev README is different as I made nanopolish easier to run.
Jared


Pagination Feature Request

New Feature
can we have https://datatables.net/ like search, sort, pagination features?

Sorting was already available. Implemented a PR that offers basic pagination.
Searching is possible to add yourself by filtering the ItemsSource, which can hooked to the DataGrid via data binding, and thus will automatically update as you search.
But yes, having built-in per-column searching could be another worthwhile feature.


Request for SEV-SNP Support in CloudStack for Enhanced Virtualization Security

ISSUE TYPE

[ ] Bug Report
[x] Improvement Request
[ ] Enhancement Request
[x] Feature Idea
[ ] Documentation Report
[ ] Other

COMPONENT NAME

Virtualization, Security
CLOUDSTACK VERSION

<IP_ADDRESS>
OS / ENVIRONMENT

Ubuntu 22.04
SUMMARY
CloudStack does not currently support SEV-SNP (Secure Encrypted Virtualization - Secure Nested Paging), a critical security feature for enhancing the protection of virtualized environments. SEV-SNP is designed to secure workloads by preventing hypervisor attacks and ensuring that VM memory remains encrypted even from the host.
I would like to know when SEV-SNP will be supported in CloudStack, and how it can be used once integrated. This feature is especially important for those utilizing AMD's SEV technology and seeking to ensure their VMs are as secure as possible.
EXPECTED RESULTS

CloudStack should provide support for SEV-SNP in an upcoming release, allowing users to take advantage of enhanced security for their virtualized workloads.
Documentation or configuration options detailing how to enable and utilize SEV-SNP once available.

ACTUAL RESULTS
Currently, there is no support for SEV-SNP in CloudStack, which limits the ability to fully leverage AMD's SEV capabilities for securing virtualized environments.

@sl4sh73r to my knowledge, SEV-SNP is a feature in the Server BIOS. Cloudstack is just an orchestrator of the KVM level.
You should be able to turn on the SEV-SNP, and Cloudstack doesnt need to know about it.
The only issue i think you will have is live migration. But this is not an issue to Cloudstack but to all Live Migration technologies with confidential computing. I remember even Google Cloud talks about this limitation in their docs.


Stage 2. Basics Tutorials Task and Python

Stage 2. Basics Tutorials Task and Python
Read Documentation of Taskfile**
it's an amazing tool for semantic automation
Last 3 companies I worked in adopted it widely.
So it's not some "my" thing ;)
Try to play with example from usage.

taskfile

You will need to learn some bash, it also very useful.
Learn Python Concepts
Python tutorials Links

https://www.mygreatlearning.com/blog/python-tutorial-for-beginners-a-complete-guide/
Big one
https://docs.python-guide.org/intro/learning/
https://www.youtube.com/watch?v=_uQrJ0TkZlc
https://www.dataquest.io/blog/learn-python-the-right-way/
https://docs.python.org/3/tutorial/
https://www.youtube.com/watch?v=rfscVS0vtbw

Python Subjects Basic List
make sure you cover most of next areas:

variables

definitions
assignments

types

primitives

int, float
str
bool

complex

list
dict
object
type (classes)

assignment (by value, by reference)

functions

definitions (signatures)
usage
parameter passing (by value, by reference)

defaults
args, kwargs

scope of variable

import system

modules
packages

work with files (IO part) (open, read, write, close)

exceptions (through, catch)

https://khuyentran1401.github.io/Efficient_Python_tricks_and_tools_for_data_scientists/how_to_read.html

@ydmeta,
today I've learned how git works from this course: https://www.pluralsight.com/courses/how-git-works
just to have an idea

a good explanation of scope is here: https://thepythonguru.com/python-functions/#global-variables-vs-local-variables
scope is the area where we can access the variable. if the variable is declared inside the function, we can access it only inside this function. we can declare a global variable either outside of any functions or in a function with the keyword global, but it's not recommended to do so

video course https://www.youtube.com/watch?v=rfscVS0vtbw complete, see djfedos-boostrap/notebooks/python_video_course_nb.py for details


Update Moya version in Readme.

Codecov Report

Merging #1571 into master will decrease coverage by 5.76%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1571      +/-   ##
==========================================
- Coverage   87.82%   82.05%   -5.77%
==========================================
  Files           5        5
  Lines         156      156
==========================================
- Hits          137      128       -9
- Misses         19       28       +9

Impacted Files
Coverage Δ

Sources/RxMoya/Single+Response.swift
87.5% <0%> (-12.5%)
:arrow_down:

Sources/ReactiveMoya/SignalProducer+Response.swift
81.81% <0%> (-9.1%)
:arrow_down:

Sources/RxMoya/Observable+Response.swift
61.76% <0%> (-8.83%)
:arrow_down:

Continue to review full report at Codecov.

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

I'm gonna go ahead and merge it as it's changing only Moya versions and people might not notice new Moya version by reading Readme.

Sorry! I forgot to do this! Thank you for catching it 🙏

@SD10 no worries!


Website down?

Hello, it seems https://cuetorials.com/ is no longer reachable, apparently for a few days already, anyone looking at it or any communication about it already?

Looks like it's back now


manager.py: new file comparisons using hash (manager rev 2.0)

todo:

[x] check if deps work
[ ] python 3.6 +
[ ] more convert jobs

More convert jobs have to wait for fixed GUIDs


Extend Y034 to cover in-place BinOp dunder methods

All the typeshed hits are in Python 2; I can prepare a backport PR for typeshed if we think this change is a good idea.

Backport typeshed PR here: https://github.com/python/typeshed/pull/7166

... And a second typeshed PR: https://github.com/python/typeshed/pull/7167


CondaHTTPError: HTTP Error when  installing tensorflow on windows by anaconda

(D:\Program Files (x86)\Anaconda2) C:\XX\XXXXX>conda install -c https://
api.anaconda.org/conda-forge tensorflow
Fetching package metadata ....Could not connect to https://repo.continuum.io/pkg
s/free/noarch/
Could not connect to https://repo.continuum.io/pkgs/pro/win-64/
Could not connect to https://repo.continuum.io/pkgs/free/win-64/
Could not connect to https://repo.continuum.io/pkgs/pro/noarch/
Could not connect to https://repo.continuum.io/pkgs/msys2/win-64/
Could not connect to https://repo.continuum.io/pkgs/msys2/noarch/
CondaHTTPError: HTTP Error: Could not find URL: https://api.anaconda.org/conda-f
orge/win-64/
why could not connect... ????
conda-forge/tensorflow | 0.12.1 | conda | linux-64, win-64, osx-64

This seems to be an issue with Anaconda, not TensorFlow.


Add clang

Closes https://github.com/dwavesystems/dwave-ocean-sdk/issues/89

Closes #90

How about we merge #90?

I am fine with either, I was not sure if @JoelPasvolsky preferred this one for some reason.

I just saw https://github.com/dwavesystems/dwave-ocean-sdk/issues/89 and decided to do the work on it, I did not know about https://github.com/dwavesystems/dwave-ocean-sdk/pull/90

Ok, shall we proceed with #90 then?

That would be my preference.


Crashing on checking for availability

I have been using this tool for couple of weeks.
This is the first time I am getting this error, and its throwing only for this package name n-mysql
Command
npm-name n-mysql
Error

// @sholladay

There's an open PR to fix this. I'll try to get it merged as soon as possible. I've had limited free time for it.

For reference, this PR: https://github.com/sholladay/squatter/pull/2

The fix for unpublished packages was released in<EMAIL_ADDRESS>There seems to be a fair amount of bad data on the npm registry, some of which could still cause similar issues under certain circumstances. But I think this can be closed for now. There are other open issues for handling the malformed packages.


Webpack 4 support

Webpack 4 had a breaking change for plugins/loaders https://github.com/webpack/webpack/releases/tag/v4.0.0

@rxaviers do you have any plan to port the changes for webpack 4 that you made for https://github.com/rxaviers/globalize-webpack-plugin also to the react-globalize-webpack-plugin?

I am totally open for it, but I currently don't have the bandwidth to work on it. Thanks for your interest.

Hi @rxaviers !
First of all thank you for creating this project, for sure is the best form to include Globalize in a Webpack project. As it's almost a year since the last comment here, is there any advance? You can use some help to enable this for Webpack 4?
Thanks and regards!


Client Allocation Request for: Lin JW

Client Allocation Questions
Core Information

Name: Lin JW
Website / Social Media: f1fpa54bz6hfang5j3nlmk6ieqcv4kda2zcqv3r5i
DataCap Requested: 4TiB
Addresses to be Notarized: https://blog.csdn.net/linjw1008
Notary Requested: philippbanhardt

Hey @linjw1008 - thanks for your request. Can you kindly add more information / context here on:

yourself , e.g. include links to social media / news mentions etc
your history working on IPFS / Filecoin, e.g. notable contributions to the community, type of engagement shown over time etc
type, size and source of the data you (and by extension other Discover participants) are looking to store on Filecoin, e.g. public data vs private data etc
how you intend to store the data on Filecoin, e.g. redundancy, location / miner preferences, etc

Thanks


Change mapped variable in construct examples into an array

My assumption is that allConfigs should actually be an array, since that would be a more plausible object to map over.

yes indeed.

thanks -- this should show up after we publish 0.15, which i expect will be very soon


Update documentation of mysql implementation to current status

This issue is related to Issue Upgrade Documentation as I forgot to update the new documentation since the mysql implementation.

This is closed due to #7


[CLI]: sweep agent crashes during wandb.init()

Describe the bug

The sweep agent crashes during wandb.init(), which is very probably caused by a server-side modification. This afternoon (13:00 - 15:00 CET) I was running a sweep as usual but when I wanted to start a very similar sweep later (after 18:30 CET) it didn't work anymore. Even running an exact copy of the pervious sweep with the same sweep.yaml, as well as code and no package updates, resulted in a crash. I therefore strongly suspect that it was caused by a server-side modification.
From the traceback below, I investigated sender.py and found that history is returns a list of dictionaries which does not need to be parsed again:
history = json.loads(resume_status["historyTail"])
if history:
    history = json.loads(history[-1])

I don't know why this started to occur today and what the correct behavior would be, but removing the json.loads resolved the issue for me as a workaround. I don't have code to reproduce the issue, but I would assume that it occurs with any project using a history. Just to be sure, my minimal sweep.yaml looks like this but guess it won't change much:
method: grid
metric:
  goal: maximize
  name: probe/student.max
parameters:
  enc:
    value: vgg11
program: dino.py

Thanks in advance and best wishes,
Felix

Thread SenderThread: wandb.init()...
Traceback (most recent call last):
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/internal/internal_util.py", line 49, in run
    self._run()
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/internal/internal_util.py", line 100, in _run
    self._process(record)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/internal/internal.py", line 309, in _process
    self._sm.send(record)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/internal/sender.py", line 305, in send
    send_handler(record)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/internal/sender.py", line 770, in send_run
    error = self._maybe_setup_resume(run)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/internal/sender.py", line 629, in _maybe_setup_resume
    history = json.loads(history[-1]) # ORIGINAL
  File "/usr/lib/python3.8/json/__init__.py", line 341, in loads
    raise TypeError(f'the JSON object must be str, bytes or bytearray, '
TypeError: the JSON object must be str, bytes or bytearray, not dict
2022-12-12 21:00:37,743 - wandb.wandb_agent - INFO - Running runs: ['w2ptq40k']
wandb: ERROR Internal wandb error: file data was not synced
Problem at: /local/home/safelix/venv/dino/lib/python3.8/site-packages/pytorch_lightning/loggers/wandb.py 357 experiment
Traceback (most recent call last):
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/wandb_init.py", line 1078, in init
    run = wi.init()
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/wandb_init.py", line 697, in init
    result = handle.wait(
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/lib/mailbox.py", line 259, in wait
    raise MailboxError("transport failed")
wandb.errors.MailboxError: transport failed
wandb: ERROR Abnormal program exit
Traceback (most recent call last):
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/wandb_init.py", line 1078, in init
    run = wi.init()
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/wandb_init.py", line 697, in init
    result = handle.wait(
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/lib/mailbox.py", line 259, in wait
    raise MailboxError("transport failed")
wandb.errors.MailboxError: transport failed

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "dino.py", line 254, in <module>
    main(config)
  File "dino.py", line 38, in main
    wandb_logger = WandbLogger(
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/pytorch_lightning/loggers/wandb.py", line 311, in __init__
    _ = self.experiment
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/pytorch_lightning/loggers/base.py", line 41, in experiment
    return get_experiment() or DummyExperiment()
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/pytorch_lightning/utilities/rank_zero.py", line 32, in wrapped_fn
    return fn(*args, **kwargs)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/pytorch_lightning/loggers/base.py", line 39, in get_experiment
    return fn(self)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/pytorch_lightning/loggers/wandb.py", line 357, in experiment
    self._experiment = wandb.init(**self._wandb_init)
  File "/local/home/safelix/venv/dino/lib/python3.8/site-packages/wandb/sdk/wandb_init.py", line 1115, in init
    raise Exception("problem") from error_seen
Exception: problem

Additional Files
No response
Environment
WandB version: 0.13.6
OS: Ubuntu 20.04.2 LTS
Python version: Python 3.8.5
Versions of relevant libraries: json.__version__ = '2.0.9'
Additional Context
No response

Thanks for creating the issue. I have the same problem!

@safelix @chris-clem. Thank you both for writing in and reporting this.
Could you please provide us the debug.log and debug-internal.log files for the crashing runs found in the project directory under the wandb folder. Additionally, @safelix , with the sweep experiment, are you resuming an existing sweep or spinning up a new sweep?

@safelix , @chris-clem . Our infra team identified the cause of the issue. A fix will be released soon.

Thank you for reaching out! I'm not sure where to find the debug.log and debug-internal.log files, since the error does not happen during a standard run and there is no run directory if I'm not mistaken. It happened when spinning up a new sweep but I also tried to delete runs and resume the existing sweep.
If I can provide you with any additional information, please just reach out.

Hi @safelix , this stemmed from a recent server side change. The issue has now been resolved. Please do let us know if you encounter any other problems.

It works again, thanks!

Same for me, thanks!


Parallels Desktop 20.2.2 Crack + Activation Key [Latest] 2024

Parallels Desktop 20.2.2 Crack + Activation Key
Parallels Desktop allows you to run Windows and Mac applications side by side. Choose your view to make Windows invisible while still using its applications, or keep the familiar Windows background and controls on your Mac. Whether you need to run Windows programs that don’t have Mac versions, or you’re making the switch from PC to Mac and need to transfer your data, Parallels Desktop has you covered
Download Latest Version Now 👈🎯✔
Parallels Desktop 20.2.2 Crack + Activation Key
Parallels allows you to run Windows and Mac applications side by side. Choose your view to make Windows invisible while still using its applications, or keep the familiar Windows background and controls on your Mac.
Over simplest form, fast and powerful running Windows on a Mac without rebooting!
Run thousands of Windows programs on your Mac
Migrate from PC to Mac has never been so easy
Reusing an existing Boot Camp partition
Dowload

▶▶DOWNLOAD Parallels Desktop🢃
▶▶Parallels Desktop Crack FREE📥
.
.
.

▶▶DOWNLOAD Parallels Desktop🢃
▶▶Parallels Desktop Crack FREE📥


Empty hash at the end of URL causes page reload in HTML5 mode

For example, If I open http://localhost/#, page is reloaded to http://localhost/.
Looks like issue happens here: https://github.com/angular/angular.js/blob/master/src/ng/location.js#L882
When http://localhost/# loaded $location.absUrl() returns http://localhost/ and $browser.url($location.absUrl(), true) called, which causes page reloading.

@dritus - would you like to try to fix this? We need a unit test the demonstrates the issue and then the fix, which is to strip empty hashes from the initialUrl before testing.

I can try to fix this, but right now I don't have time.


Stack multiple notifications

When I run the below example from the readme on macOS 10.12.6, the second notification almost immediately replaces the first. Is there a way to get these to stack as two separate notifications?
const notifier = require('node-notifier');
// String
notifier.notify('Message');

// Object
notifier.notify({
  'title': 'My notification',
  'message': 'Hello, there!'
});

Play with the settings in Notification Center. If you chose the 'Alerts' alert style instead of 'Banners' for terminal-notifier, you'll get the behavior you'd expect. Downside is that they have to be manually closed, I believe.

Hm, no luck. Even setting wait: true doesn't seem to do it.

Actually, this works if installing from master branch as opposed to the version on npm. FWIW it works for me both on 'Banners' and 'Alerts' in the MacOs notification preferences.
Depends on https://github.com/mikaelbr/node-notifier/issues/198

Correction: @tylerdmace is correct. I was setting the alert style for iTerm and not for terminal notifier as he wrote.


Failure when adding dependencies: ghc: needed (==8.0.1)

When installing on macOS 10.12.2 I receive the following error:
-- Failure when adding dependencies:
      ghc: needed (==8.0.1), <IP_ADDRESS>61117 found
    needed for package apply-refact-<IP_ADDRESS>
*** Binary installation failed with error 1.

Do I actually have to downgrade ghc?

This is solved by just upgrading ghc to 8.0.2. It's just that the message needed (==8.0.1) is a bit confusing.

Weird that it just started having problems because it comes from #152 which was merged early in 2016.
Maybe it's because your global Stack config specifies an LTS version that conflicted with apply-refact. The vim installer searches in your config file and matches the system LTS version so that the installation of ghc-mod will function properly (it is sensitive to cabal and ghc version). https://github.com/begriffs/haskell-vim-now/blob/master/scripts/setup.sh#L44


No such property: iconFontsDir for class: java.lang.String

[x] Review the documentation: https://github.com/oblador/react-native-vector-icons
[x] Search for existing issues (including closed issues): https://github.com/oblador/react-native-vector-icons/issues

Environment
Windows 10, rn-vector-icons v7.1.0

Description
After following the android instructions, build fails
* What went wrong:
A problem occurred evaluating script.
> Exception evaluating property 'iconFontsDir' for java.util.ArrayList, Reason: groovy.lang.MissingPropertyException: No such property: iconFontsDir for class: java.lang.String

Reproducible Demo
yarn android

I made a typo while customising the files being copied


Centre-align my instagram photos

Hello,
I followed the instructions on instafeed.js website in order to add my company's instagram feed on my website, and it has been very successful. However, my feed (located on my homepage) is off-centre...it is too far to the left of the page. How do I centre-align my feed?
Thanks,
Dani

Dani.
Can you please explain how do you add my company's instagram feed on my website?
I have the same issue in my company.
Thanks...
Jorge

I fixed this issue by using the "text-align" attribute on my parent div in my css:
section.social {
	text-align: center;
}

Since my instafeed div is the child, it centers it! I hope this makes sense and is helpful!


TextMatch doesn't work when use Search.Repositories

when i use Search.Repositories, set TextMatch = true, but it doesn't work
this is my code:
repos, resp, err = client.Search.Repositories(ctx, query, &github.SearchOptions{
		Sort:      sort,
		Order:     order,
		TextMatch: true,
		ListOptions: github.ListOptions{
			Page:    page,
			PerPage: perPage,
		},
	})

I found it in go-github, in search function, use switch to add Accept  to the req.Header, it lead to i can't get text_matches in reponse when i use  commits topics repositories issues
I don't know why it's designed in this way, and  i didn't found other accept values other than application/vnd.github.v3.text-match+json on the  github restful api, such as application/vnd.github.mercy-preview+json . In fact, i don't know what  application/vnd.github.mercy-preview+json will do even if i read the documentation

Hmmm... that does indeed look unusual.
In the corresponding unit test, it shows TextMatch being used with client.Search.Code:
https://github.com/google/go-github/blob/master/github/search_test.go#L408-L413
Although the official documentation shows an example using the issues endpoint:
curl -H 'Accept: application/vnd.github.v3.text-match+json' \
'https://api.github.com/search/issues?q=windows+label:bug+language:python+state:open&sort=created&order=asc'

which makes me think that this custom header should be added no matter what the value of searchType is.
Do you want to make a PR to change this behavior and test it out, @DarkMatterV ?

Okay，I want to do it


Feature request: Friendly name

Have a friendly name to display in Lovelace instead of the safe-only entity name name from config.

went missing some commits ago, but it's back!

Where can be set? No configurable option.

I can set a name from Lovelace for main plate and backlight, not moodlight.
Would be better to be able to pre-set a friendly name from configuration.yaml because this way the name has to be set one by one for each sub-entity.

I've started cleaning up the code to make it acceptable for HA inclusion, friendly name are no longer accepted

you can now change the name of the moonlight

I've started cleaning up the code to make it acceptable for HA inclusion, friendly name are no longer accepted

I really don't get it why they make so many stupid constraints.

it's about maintaining consistency over all the different integrations, currently that's achieved through the lovelace interface


chore(playwrighttesting): use playwright OSS types

Packages impacted by this PR
@azure/microsoft-playwright-testing
Issues associated with this PR
Type changes by playwright OSS will impact @azure/microsoft-playwright-testing SDK if relevant types are hardcoded.
Describe the problem that is addressed by this PR
Instead of having playwright OSS types hardcoded in the package, we will use the types provided by the playwright OSS package itself (Playwright OSS is added as a peer dependency).
This also changes peer dependency version of playwright OSS to v1.47, which is the minimum supported version of playwright OSS for this SDK.
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
APIView has identified API level changes in this PR and created following API reviews.
@azure/microsoft-playwright-testing

Also renamed MPTReporterConfiguration to ReporterConfiguration as per APIView review

This PR also removes the below constants from the public variable ServiceEnvironmentVariable
    PLAYWRIGHT_SERVICE_OS
    PLAYWRIGHT_SERVICE_EXPOSE_NETWORK_ENVIRONMENT_VARIABLE
    PLAYWRIGHT_SERVICE_REPORTING_URL


Question about parsing the md on :::

Quick question.  I would like to create a different type of markdown-it plugin that would use a "token" similar to the way ::: is used to delineate tabs here in the markdown source.  I thought I would use your code as an example but I can't find anywhere in  the code itself that searces for the tokens :::!?  Where in the code is the md block parsed on :::?
Thanks

@boulderob from here it requires markdown-it-container

Late reply.  Thanks for the answer!  It helped.


Audiobus MIDI Sender example

An example project, building on the SenderSynth Audiobus set up, for using an AKSequencer to send MIDI through Audiobus 3 MIDI send ports.  Included in the project, in a file called Audiobus+MIDI.swift, are some helper methods which maybe should live in Audiobus.swift

Thanks!


Support timezone with minutes offsets

Hi @thooyork ! Thanks for creating a great jQuery clock plugin. I've been using this for a current project and noticed that it lacks support for timezones with minutes offsets. There's also an existing issue  about this. Kindly review my proposed implementation. :smiley:
Proposed solution will support timezones such as:

(UTC+04:30) | Kabul
(UTC-04:30) | Caracas
(UTC+06:30) | Yangon (Rangoon)
(UTC+05:30) | Chennai, Kolkata, Mumbai, New Delhi
(UTC+03:30) | Tehran
(UTC+05:45) | Kathmandu

The idea is to retain your original code and just added new functions minutesCorrection and timeCorrection. To accommodate minutes offsets, they are to be converted to hours (e.g. 30 mins -> 0.50hr, 45 mins -> 0.75hr) to retain the format needed for hourCorrection options property. For example, if the selected timezone is GMT +9:30 and the current timezone is GMT +8:00, the hourCorrection will have the value +1.50.
~ Kris ~

Merged minute offset in timezones