says token is invalid when it is idk try to check it out ig

Your token is probably invalid because its validity is tested each time the script is run. Try another one and if it still doesn't work, contact me on discord: https://dsc.gg/astraadev

bro i used ur token grabber and use console on 2 different accounts so i think its the script but idk

Try to connect to the account with my multi tool (https://github.com/AstraaDev/Discord-All-Tools-In-One). If it works, I'll try to find the problem, if not, it's because of your token.

yep it definitly does work when i use auto login with my token on the multi tool but for some reason is thinks my token is invalid for this selfbot

Fuck, can you create a ticket on my server so we can see where the problem comes from?

Fuck, can you create a ticket on my server so we can see where the problem comes from?

Tell him to enable all intents :)

The issue could possibly be from the requirements.txt file. Latest versions of all required packages would install at the time of running the script. This means the version of each dependency @AstraaDev used while testing would most likely be different from what others are using 3 months down the line. I'd suggest @AstraaDev updates requirements.txt to include specific versions for each dependency. For instance the new Discord.py requires intents before calling discord.Client().

this no work no mo :(

Btw this is a self bot but do I need to use a bot in my server or my own token because this doesn't work


Get the initial client/server integration set up

Make sure we account for CORS (https://developer.mozilla.org/en-US/docs/Web/HTTP/CORS).
Ideally, we should handle app-wide configurations in one place so as to simplify the various requests that will be sent to the API throughout the application.
This will require changes to both client and server.

I think we can close this issue ?


Add cryptographic sequencers/emags

Description

Forces open and bolts open airlocks
Breaks locks on lockers/secure crates
Eventual special-cased interactions with certain objects (just raise an event for now, don't need to code any special interactions unless you really want to)

Taking up this issue.

owned


fix(iam_policy_no_administrative_privileges): check attached policies and AWS-Managed

Description

Create IAM Policy BaseModel class.
Add the following checks:

iam_customer_unattached_policy_no_administrative_privileges: renamed current check iam_policy_no_administrative_privileges to change its behavior that looks for not attached ones in the description and title. LOW, to fix it is deleting it or change it. Add into the description that may be eventual consistent if an ephemeral resource is using it.
iam_customer_attached_policy_no_administrative_privileges: that checks only customer managed policies attached. HIGH, to fix it is changing it.
iam_aws_attached_policy_no_administrative_privileges: that checks only AWS managed IAM policies attached. HIGH, to fix it is detaching it.

License
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Currently we have iam_policy_no_administrative_privileges that checks customer managed policies attached and not attached. This one doesn't belong to CIS 1.4 or 1.5 for AWS. So we can leave it as it is.
Now, we need to more new checks to fit the CIS requirements:

iam_customer_managed_attached_policy_no_administrative_privileges: that checks only customer managed policies attached.
`iam_aws_managed_policy_attached_no_administrative_privileges:  that checks only aws managed policies attached.

iam_policy_no_administrative_privileges: rename this one to  iam_customer_not_attached_policy_no_administrative_privileges change its behavior that looks for not attached ones in the description and title. LOW, to fix it is deleting it or change it. Add into the description that may be eventual consistent if an ephemeral resource is using it.
iam_customer_managed_attached_policy_no_administrative_privileges: that checks only customer managed policies attached. HIGH, to fix it is changing it.
iam_aws_managed_policy_attached_no_administrative_privileges: that checks only AWS managed IAM policies attached. HIGH, to fix it is detaching it.

Not related with the above PR, it was a typo.


IDCOM-1313 Solana earlier timeout ( do not merge )

** This is a backup in case the full retry version does not work. **
Add early timeout logic around Solana sendAndConfirmTransaction to avoid the lambda timing out when the Solana node takes long.
No retry in this PR, that is in a separate PR.

Closing this, it's been replaced by the 'full retry' version.


upgrade versions

Due to old pydantic version, a class with name key was failed and a message of require assign an alias was raised.
later pydantic version has resolved this issue

pydantic >2 is now supported


[a bit BUG] About VSCode setting for dynamic switching of flutter SDK version

Is your feature request related to a problem? Please describe.
I tried to configure the IDE setting for VSCode to switch the flutter SDK version dynamically according to README like that.
{
  "dart.flutterSdkPaths": [".fvm/flutter_sdk"]
}

However, It didn't work well.
After all, I had to click on the flutter version displayed in the bottom right corner of VSCode to switch it myself.
And then the following line was automatically added by VSCode.
{
  "dart.flutterSdkPaths": [".fvm/flutter_sdk"],
+  "dart.flutterSdkPath": "/User/user/path/to/project/.fvm/flutter_sdk",
}

I don't think it's smart.
Describe the solution you'd like
I found a solution to solve this problem completely.
Dynamic switching is now enabled by rewriting the following:
{
  "dart.flutterSdkPaths": [
    "${fileWorkspaceFolder}/.fvm/flutter_sdk"
  ],
}

By adding ${fileWorkspaceFolder}/ in front of .fvm/flutter_sdk, VSCode seems to expand the absolute path of the current project.
ref: VSCode - Variables Reference
So, Could you confirm it and please update README If the idea I've suggested is true?

Will close this issue please reopen if there is any issue


[ControlAddIn] Use "Previous" Page Button remove controladdins in page

Describe the bug
In a page in where I have some controladdins (three). The first time I open it, if I click the Previous button, two of my controladdins are disappearing one by one as you can see in the gif bellow:

I can't reproduce it if I open the page again. I have to CTRL + R before.
If I hit ESC key the page closes correctly.
The "weird" thing too is that the canvas (second group) which is also a controladdin is not disappearing.
Appends on a List Page type object:
<layout
   <area
      <group
            repeater
                 field
                       ...
        >
      <group
              usercontrol(canvas)
       >
       <group
              usercontrol(first) (disappears)
              usercontrol(second) (disappears)
        >
   >
>

I don't know if it's a bug, if it's not, Could you please tell me why does the page / my controladdins are acting like this ?
Thank for any help
Versions:

AL Language: 2.1.79379

Business Central: W1 13.3 (27233)

Hi @AndreyKorepanov ,
I've attached a zip file containing the piece of code to reproduce the issue.
#4546_controladdinissue.zip

Hi @JulienDecottignies, we I've tried your code on 14.x/15.x/latest BC versions and could not repro the issue. Are you still experiencing the problem? Could you try it on the latest BC version?

Hi,
No i'm not. I close the issue. Thanks


Google Home trackers not updating

Home Assistant release with the issue:
0.88.0
Last working Home Assistant release (if known):
0.87.1
Operating environment (Hass.io/Docker/Windows/etc.):
Docker
Component/platform:
https://www.home-assistant.io/components/googlehome/
Description of problem:
My existing trackers from the previous implementation of the Google Home device tracker are not updating after upgrading to 0.88 and updating my config.

Do you have any other device tracker configured with new devices tracking set to false ?  See #21284

I do, but the specific devices I'm trying to track are already set to true.

So I can confirm that the new component will not use the known devices from the old version. I've also found a problem with it.
Here was a known devices entry for the old version:
kyle_bt_office:
  hide_if_away: false
  icon:
  mac: ip.ip.ip.ip_mac:mac:mac:mac:mac:mac
  name: Kyle (Office)
  picture:
  track: true

And here is one for the new version:
ip_ip_ip_ip_mac_mac_mac_mac_mac_mac:
  hide_if_away: false
  icon:
  mac:
  name: Kyle (Office)
  picture:
  track: true

With the old version, you could change the id, and it would still track based on the mac field. The new version doesn't fill in the mac field, so if you change the id, it will just create a new entry and the old one won't work.

I have the same issue when trying Google Home Presence Detection for the first time on 0.88.1.  In other words, I don't have devices in known_devices.yaml from the previous way of doing things with a device tracker platform, but have only newly created devices with the new googlehome: component.   I did not tamper with the ID or friendly name of the device, and am using defaults for the configuration.yaml entry (as below).
googlehome:
  devices:
    - host: xxx.xxx.xx.x

The sensor shows up, and i can get it to do an initial changes of state from "not_home" to "home", but it will not update after that.  Interestingly, and not sure if related, but I could only get the state to change to "home" if I put my phone in "pairing" mode (using  Google Pixel 2).

I'm seeing the same behavior as described by @mrsynds - without changing anything in my known_devices.yaml (except making track: true) restarting my pi makes all the trackers say 'not_home'. Putting my phone into pairing mode will switch them all to 'home' (within range) but they will never update after that, they'll just remain 'home' until my next restart.
I also added these to a person component, which should reflect the last-updated device_tracker, and noticed that leaving the house accurately shows me as 'not_home' while away (based on other trackers) when though the Google homes still show 'home'. This implies to me that the trackers are simply not updating, rather than updating inaccurately.

I can confirm that with Pixel 2, I could only see the device on the yml file after putting in pairing mode, after this the device stay as home forever.

Same issue here,3 Google Homes, 2 different Android phones. HA sees the phones on initial pairing with the Google Homes, but then never again.
Even having the phones in BT pairing mode doesn't set them to Home.
Anyone else still having this issue?

Same scenario:  1 Google Home Hub, 1 Google Home and 1 Google Home Mini. HA sees the device on initial pairing mode. Once pairing mode is disabled, The entity state changes to "not_home" and never changes afterwards unless pairing mode on the phone is enabled again.

üst to add to this, seeing the same behavior, Googlehome never to change state  to connected...
secondly: if a device isn't powered on at HA startup, the device is never seen in HA, even if powered on  after that. While the device holds timers and alarms, these are also not seen. which seems a major Bug...
please see my post in the community : https://community.home-assistant.io/t/issues-with-googlehome-component-bt-tracking/122277

I've been playing with the unofficial Google Home API. Seems like the issue comes from the Google Home device itself, as it displays the exact behavior we are seeing. Once the phone is no longer in pairing mode, Google Home stops seeing it.
Looks like the component won't be able to be fixed at all.


Requesting Temporary ignoring of default.go oci-runtime-validation test

After two weeks of testing and a lot of digging of git commit history, I think I have finally found what has been causing CI failure for #694 's OCI validation test (there are some other failing tests, but this is not related to them).
The surprising reason behind that test failing is a knock-on effect of the way -

Our CI is set up (I have partial blame in this :sweat: )
We recently adding these capabilities
runtime-tools not validating there tests on runc (?)

If you see in commet I have mentioned that the CI is faioing on youki for these three capabilities, although if you check the integration test CI of any other PR there is no issue. The reason behind this is :

We added caching mechanism to the CI for integration tests on 7th Sep Here. This caches the build artifacts of the runtime-tests builds, which is the compiled tests, and has a very good reason of doing so, as without it the CI takes 7-8 mins and with caching it takes about 3-4 mins. The downside is that the tests are not built each time, and we always use the version that was cached on 7th Sep.
runtime-tools itself updated one of their dependencies go-capabilities on 26th of October here
The go-capabilities itself was updated on Aug 5 here to include the three new capabilities, and thus the runtime tools itself as well inherited these updates.
runc released version 1.1 here on 18th Jan , which included the support for these capabilities. I think we also have only recently implemented these as well.
As our CI was using the cached version of tests, they did not check for these and thus tests were passed. But when I moved the git module in the refactor, the cache was invalidated, and youki was tested with new version and failed the tests.
The probable reason is that the CI runner's kernel might not be updated or compiled with correct flags or has permissions to set these capabilities, so runc cannot use them OR the oci-tests has bug in it, (as far as I checked the do not validate the tests on runc or some other runtime)

It is too late here, so I'm not sure what approach might be best, my suggestion is to either comment the default.go test and open an issue if not yet opened on oci-runtime-tools
I do not have runc 1.1 yet, so cannot verify if the tests are also failing on it as well , but I would guess that it is so. I will try to get the 1.1 and check on it if I can.
@Furisto @utam0k Please take a look. Thank you.

um... we got into trouble 😭
First of all thanks for the awesome research. If it was for you, I probably wouldn't have noticed it.
I don't want to remove as many tests as possible because default includes many tests. it gets a little weird, but how about hacking from stdout only when default.go run? e.g. ignore only the relevant test cans in default.go.

Hey @utam0k
I agree that removing the test should be the very last option, as we have already commented few tests as they do not work, and removing tests will make more bugs slip through.
Currently my suggested approach is this :

Build runc 1.1 locally and run oci tests on it
If runc also fail the tests, then the tests themselves need to update :
then I will open an issue on the runtime-tools repo notifying this, and wait for few days to see if they reply.
If they do, then we can wait till they update, and then use that new version for us, till then we can keep using the cached version, as even though capabilities tests are old, other seems to have no major changes since our cache, and are currently working
In case they do not reply, or won't be fixing the issue in near future, we can work on the way you suggested, and use grep to ignore these three specific capabilities related test failures, until we find some other good way to deal with it.
In case runc does pass the tests, that would mean that it is our implementation that has some errors, and then we can fix them on our side, which would mean that the CI is not broken

I'll update here once I have ran the runc check.
@utam0k What do you think?

Hmm I cloned and built runc from main branch, and it seems that it is passing the default.go tests, but failing the delete.go tests :thinking: :thinking: :thinking:
That should not be happening right? If you get time, can you also get runc 1.1 and verify this on your end as well?
If that is right, it would mean that is is some bug from our end, likely that we need to check the kernel version and enable the BPF and other features according to that.

@utam0k I'll use this single message to keep updating status, so that there is not much mail / notification spam
(updates are from top oldest to bottom newest)
Update : It seems that the default tests fail when we run the script with sudo permission, instead of getting sudo from inside the script itself, i.e. running sudo ./oci-tests will make the default fail, but just running ./oci-tests and then giving sudo permission to the line running test will pass the default test

I think I figured out what is causing the issue, and I think solution is simple if I understand it correctly :
As far as I know, we currently support CAP_PERFMON, CAP_CHECKPOINT_RESTORE, and CAP_BPF but in the capabilities code, we still ignore them when setting capabilities, Here : https://github.com/containers/youki/blob/main/crates/libcontainer/src/syscall/linux.rs#L136-L140
That is why I think even though youki reports that they are supported, they are ignored above when setting capabilities, and thus the error occurs.
I tried commenting that part, and unconditionally dropping the cap (the _ arm), and that seemed to pass the default and delete tests as well.
@Furisto if possible can you confirm what I am thinking is correct or not? This seemed to slip by originally due to the CI cahcing I have mentioned.
@utam0k What do you think?

@YJDoc2 Makes sense to me. We should support these capabilities in Youki as well.

@YJDoc2 Sounds good to me to support them. But If we will support these capabilities, we have to check the linux kernel version. That's the only thing I want to pay attention to.

@YJDoc2 is there still pending action items for this issue?


  Just cuz some retard on discord said so doesn't mean it's true

man no need to be rude to me?? you haven't showed any proof that this is yours, how do you expect me to believe you??🤨🤦🏾♀🤦🏾♀

man no need to be rude to me?? you haven't showed any proof that this is yours, how do you expect me to believe you??🤨🤦🏾♀🤦🏾♀

My bad


Slot highlighting is misalligned with recipe book

Not exactly sure how, but means other mods might have the same situation.

Fixed in 1.0.23


Reservations

My Reservations and Improved style and change app state depending on user state

Add My reservations page and display all reservations for signed user there
Add navbar redux global state, if navbar is shown or hidden
Change left-margin of home, my reservations and auth pages depending of navbar sttate
If the user is not signed in redirect to auth page
Improved style for home and styled reservations

Hello @Sanja969
Status : Approved 🟢
Great Job working on the detail component
[x] Code is clean
[x] Redux logic implemented correctly
[x] No linter errors


Fix ConnectionClosed_BlameAttributedCorrectly test

I can't see this failing locally, but what I imagine is happening is that:

The client sends the close message and closes the connection in close succession
The proxy is reading from the client and receives the close message and the connection close at about the same time
Kestrel signals RequestAborted in response to the connection close
The proxy happens to observe the cancellation before reading the close message and tears everything down (this is a race - that's why the test is flaky)
Because the close message never went through the request pipeline, the telemetry parser never saw it, so we don't consider the close as graceful

I'll keep re-running the CI a few times here


trim output's trailing whitespace

Whitespaces were annoying with https://github.com/SublimeText/TrailingSpaces loaded

Thanks!
I'll create a new release for this now.


Fix invalid provider configuration block

Fix invalid provider configuration block

:tada: This issue has been resolved in version 0.4.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


:white_check_mark: tracer

#5

97.222% some of things I didn't test are related to #14
@guillaumecrespel ready to be reviewed


Incorrect capture's scanRect

Seems like crop before rotate will return wrong scan view frame, as you can see below, the second image show correct cropped area on the thumbnail view.
Crop then rotate

Rotate then crop

Can you show me the code you are using to display the scanning rectangle?
I believe you are using lastScannedImage?

@benjohnde yes, i was displaying lastScannedImage, is it correct ?

Fore more information, both of luminanceLayer & my custom code return same result of incorrect scan rect

Yeah that is basically correct, weird.
I don't see a false note in the code.
In ZXCapture.m:
      // If scanRect is set, crop the current image to include only the desired rect
      if (!CGRectIsEmpty(self.scanRect)) {
        CGImageRef croppedImage = CGImageCreateWithImageInRect(videoFrameImage, self.scanRect);
        CGImageRelease(videoFrameImage);
        videoFrameImage = croppedImage;
      }

      CGImageRef rotatedImage = [self createRotatedImage:videoFrameImage degrees:self.rotation];
      CGImageRelease(videoFrameImage);
      self.lastScannedImage = rotatedImage;

Hmm you meam the small overlay (brighter area) does not match with the result thumbnail?

Because that is independent from ZXCapture.

That's true, the BarcodeScanner should to be updated, right ? :D

Yeap, but as the BarcodeScanner should be rewritten in Swift, I wont fix it as of now

You can give it a shot if you want to :)

@benjohnde to solve this one, the transformVideoRect have to be converted from portrait to landscape if needed. Sample code:
// Correct video frame under Portrait mode cuz the framework will crop before rotate
CGPoint scanPoint = CGPointMake(
  transformedVideoRect.origin.y,
  self.view.frame.size.width - transformedVideoRect.size.width - transformedVideoRect.origin.x);

CGSize scanSize = CGSizeMake(
  transformedVideoRect.size.height,
  transformedVideoRect.size.width);

transformedVideoRect = CGRectMake(scanPoint.x, scanPoint.y, scanSize.width, scanSize.height);

Do you want to hand-in a pull request? :)

Sure, I will

PR #444 is ready


How can I make a program using the seal library to be a dll?

I am writing a program using seal library, I installed the library and used cmakeliststxt to find the packege. Now I want to make the program a dll, but failed. The error was like this : "undefined reference to `seal::CoeffModulus::Create(unsigned long long, std::vector<int, std::allocator >)' ". How can I solve it? Or, how can I use seal in java? What I am trying to do is using jni to use seal in java. I hope someone to give me some suggestions. Thank you.

Check out the mpc4j which contains a Java wrapper for SEAL already


Almenscorner/issue111

Add option to decode all base64 encoded strings in the documentation with the use of -d as requested in #111

Codecov Report
Patch coverage: 58.82% and project coverage change: -0.60 :warning:

Comparison is base (1dbf233) 95.89% compared to head (21b5a90) 95.30%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #112      +/-   ##
==========================================
- Coverage   95.89%   95.30%   -0.60%
==========================================
  Files          59       59
  Lines        3194     3239      +45
==========================================
+ Hits         3063     3087      +24
- Misses        131      152      +21

Flag
Coverage Δ

unittests
95.30% <58.82%> (-0.60%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/IntuneCD/documentation_functions.py
79.68% <58.82%> (-4.32%)
:arrow_down:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ISHRemote Get-IshTypeFieldDefinition sees Event progress and detail column DATETIMEKIND

DATETIMEKIND fields are removed from the ISHEvent FieldDefinitions and pester tests are aligned accordingly.

Similar change to #185 ... just making Pester test count match up with actual count from soon-to-be-released Tridion Docs 15.1/15.1.0


The correct order integrating QR code onboarding for maker？

Open Helium-app, scan the QR code, the qr code content is like string:
helium://add_gateway/{txn}

then the txn is signed by wallet and then commit to helium, if the owner field of txn must equal to
then wallet address(is it right?), to generate the txn before QR code generated, must run the miner command in gateway:
sudo docker exec miner miner txn add_gateway owner={ownerAddress} --payer {payerAddress}
===>
{txn}

Based on what I said above, I think, if i(maker) want to integrate QR code onboarding:

folk and add add directory to src/makers/ of https://github.com/helium/hotspot-app, add files including hotspots.ts like https://github.com/helium/hotspot-app/blob/main/src/makers/clodpi/hotspots.ts, which contains lines:

  onboardType: 'QR',
  onboardUrl: 'https://xxxx.xyz/dashboard',

build the App to apk, then install App on my phone
open the App, select the hotspot item which added in step 1
clieck the website(URL is onboardUrl) to open a dashboard developed by maker
enter the hotspot productId/macId or other unique ID which uniquely identifies the hotspot, and enter the Helium-App wallet  address
then, the website notify the gateway through the connection from hotspot to maker's backend, the hotspot run the command which generate {txn} using Helium-App wallet address as ownerAddress and the payerAddress
the website generate a QR code with string helium://add_gateway/{txn}
using the Helium-App to scan the QR code, and the process the txn, signed by the wallet acccout, commit to the helium blockchain.

Question:

Is the onborading process above correct?
the owner field of txn must equal to wallet address who want to add the hotspot ?
Can the QR code be affixed to the product during hotspot production?
onboardUrl in hotspots.ts must be required?

Are you a maker applying under the HIP19 process?

Are you a maker applying under the HIP19 process?

yeh, #941 Question What is the development process like

please direct these questions to your designated maker channel. thanks for understanding.


document post-process action of dropping untranslated languages

We began of policy of dropping languages which are mostly untranslated. The PR that introduced this policy did not document this post-process action. This documents this policy in the section of the update-translations.py script where we state the post-processing steps that we perform.
As such, this is a follow-up to #102

Concept ACK.

ACK bee0aa2a03f2c0252e02604132d9b7f317baf107


Update index.php

Following the new requirements, changing to PHP 5.5.9 or higher.
Thanks

Right, we have other places too with this hardcoded requirement.
Going to use a common shared constant we already set, closing this for now, good reminder anyway!


[Bug] bad display of head_on_collisions_comparison_percentage widget

Describe the bug
There are two cases in which there is a bug:

Downloading from web, for example from here
Auto download when sending to Telegram

Expected behavior
Image download should look like (or more similar) to the one web screenshot
Also, if possible, In web itself  "shift" the labels on the graphs to fit the
For example here the 17% with "אחרות" text can be shifted up AND here the 50% of both categories can be shifted left
(This will solve this issue as well)
Screenshots

Download from web:

Download from Telegram - see that text is missing in the smaller chart:

Printscreen from Web (Chrome):

Environment
Browser: Chrome
Environment: Production

Solved in this issue: https://github.com/data-for-change/anyway-newsflash-infographics/issues/1136


document how to tell when public transport road becomes private logging road

users express confusion.
presumably, public roads connect settlements, and in many (though not all cases) already exist in OSM.
add to documentation.

I think we are never going to truly solve this especially as we scale up. The difference in classification between path, track, unclassified roads, etc. is very subjective and hard to get right. Then beyond that, we have to decide whether a track gets the access=forestry tag.
It may help our case to tag start dates on all roads in our target areas? Since the public roads enable logging and lead to dedicated logging roads, we may get a clearer picture by showing all the road development over time?

Agree with Kris. It will be very challenging to keep track on change. Collecting the start date for all roads will be very helpful to evaluate their impact.
However, there are clear differences between pure logging roads (going just though forest and ending in nowhere) and other roads (connecting farms and villages). We can still point out this different to sensitize users.


move up the lines handling multiple input by adding acq

Don't we need to update the "expected" test case for this?

Done.

Thanks! Merged and released.


Extend UIGP to multiple uncertain parameters (with different input variances)

Addresses #70

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (d02ffd5) 95.63% compared to head (1c945cb) 95.62%.
Report is 1 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #74      +/-   ##
==========================================
- Coverage   95.63%   95.62%   -0.02%
==========================================
  Files          51       51
  Lines        3918     3930      +12
==========================================
+ Hits         3747     3758      +11
- Misses        171      172       +1

Flag
Coverage Δ

unittests
95.62% <100.00%> (-0.02%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Keyvault requirement for Subscription Mode

When creating a batch account with and the Key vault uses only EntraID Authentication, batch account creation fails with 'invalid key vault reference'. only when using Access policy for associated key vault is when the creation succeed, can guidance be updated to reflect so requirement.

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

ID: 2146b9a6-94f1-b2a8-972e-63602992d092
Version Independent ID: ec164b99-5fc9-f5a1-6eb7-1d5fb1cad568
Content: Create a Batch account in the Azure portal - Azure Batch
Content Source: articles/batch/batch-account-create-portal.md
Service: batch
GitHub Login: @Padmalathas
Microsoft Alias: padmalathas

@SamRakaba
Thanks for your feedback! We will investigate and update as appropriate.

@SamRakaba
Thank you for bringing this to our attention.
I've delegated this to content author @Padmalathas, who will review it and offer their insightful opinions.

PR#

Thank you for your feedback!!
This has been taken care and the document has been updated to reflect the content with a "NOTE". The document is available for public to consume. Closing this issue.
#please-close


1.24 can not add break point

use chrome,1.24 unminfied cesium.js
when i add break point at any line in the file of cesium.js,it will directly jump to the end line of earcut.js。

Hello,
I think this issue has been fixed in this PR: #4097
It will be available in the next release.  If you're still seeing problems then, feel free to re-open the issue.
Thanks!


Support for block comments

KSS supports block comments /**/, however sc5-styleguide wasn't able to parse it properly. Is this a bug?

KSS supports block comments with only CSS. In order to use preprocessor it only supports inline comments. See this section for details

@kchetan92 If you still have a problem, please tell which syntax are you using, SASS, LESS, SCSS? If not, can we close the issue?

Thanks @varya , @junaidrsd . Your suggestion worked.


Skipping background_tasks in unit testing

We can skip background tasks while performing unit testing and execute the function normally.
def background(*arg, **kw):
    from background_task.tasks import tasks
    return tasks.background(*arg, **kw)

**skipping background tasks while testing **
from functools import wraps
def background(*arg, **kw):
    def wrapper(f):  # a wrapper for the function
        @wraps(f)
        def decorated_function(*args, **kwargs):
            return f(*args, **kwargs)
        return decorated_function

    from background_task.tasks import tasks
    if 'test' not in sys.argv:
        return tasks.background(*arg, **kw)
    else:
        return wrapper

I was wondering if it's possible too.
There is an option BACKGROUND_TASK_RUN_ASYNC that, I assumed, makes the task run immediately, but in fact, it's only changing the behaviour of the worker/runner.
I understand that the package takes a different approach for the testing. You might need to invoke the worker from your test case explicitly:
...
from background_task.tasks import tasks
...

@background()
def task(...):
    ...

@pytest.mark.django_db  # NB! to access the DB
def test_run_task(self):
   task(...)
   assert tasks.run_next_task()

However, it wouldn't work with scheduled tasks. That case would require some patching of the code under the test :(

Would be great to have an analogue of task_always_eager/CELERY_ALWAYS_EAGER for use in tests, for sure.
For lack of better alternatives at present, replacing the wrapped tasks with the original function seems to work alright:
import some_module.tasks as tasks

...

@patch('some_other_module.tasks.some_background_task', new=tasks.some_background_task.task_function)
def test_something_calling_a_task():
   ...


How does the first proto file import the message in the second file?(Go)

b.proto
syntax = "proto3";
package b;
/** Command 命令 */
message Command {
    int32 type =      1;  // 種類
    bytes content =   2;  // 命令
};

a.proto
syntax = "proto3";
package a;
import "b.proto";
message S {
    b.Command cmd =          3;  // 命令
};

I use the following syntax to create a file:
protoc --go_out=plugins=grpc:. a.proto --proto_path=.
a.pb.go
...
type S struct {
Cmd *Command    // error mgs : undefined: Command
....
}
...
How can this be solved?

You at the very least need to also compile b.proto.

After I compile b.proto, a.proto is still wrong, and there is no automatic association. Is there a solution?

We a moving towards a world where the go_package option is required for generating any .pb.go. One cannot expect protoc-gen-go to know where a remote reference is located in the Go namespace if that information is not available somewhere. The go_package option records precisely the information needed. Lacking it, we can't connect the protobuf namespace to the Go namespace in a way that works for all situations (as you are evidently observing). There are some rules that protoc-gen-go follows when go_package is missing, but they almost never do what users expect.


Fixed the metric format function to correctly handle for inf and nan

If a metric was set to use precision 0, then an inf or nan result in the data frame would cause the transformer to raise an unhandled exception

Coverage decreased (-0.2%) to 92.369% when pulling 9cdce0572de14488fd0f5959e2e67b2146d3a46b on metric_with_zero_precision_and_inf_or_nan_result_breaks_pandas_transformer into 174779cf12c0577bee5671c01428158bfc11157e on fireant1.0.


Explanation of changes in 4.0

Wait a second

I'll edit the post later, which is now a bit older, at the latest when I realized how everything escalated and that this Github error was even pinned.
I really let my emotions out here. And I don't want to drastically correct my posts just because they've been more publicized now.
It could be that I speak very inappropriate about the author and also use inappropriate words. I explained all the changes of PyInstaLive 4.0.X and I complained about most of them because until now unfortunately Version 4.0 is bad. And I also mentioned in detail why you shouldn't load this version, but only when the older, most stable Version 3.2.4 shouldn't work anymore for some reason.
In no way do I want to portray the author badly. I'm glad he exists because he has created things that have helped me tremendously in my life, like downloading Snapchat videos as well as loading Instagram live streams.
I only complained a lot because PyInstaLive is one of my favorite programs and I had a lot of memories with it.
Nevertheless, I think it's worth looking over here and reading through everything.
Also, maybe get some popcorn to drink before you leave it all. I hope you enjoy it.

Hi Dirk,
This isn't a bug or anything else I want to report, just something that seems unclear to me.
I find the program breathtaking, which I have already mentioned in other posts and use it every day. However, I don't find Version 4.0 really successful. I don't understand why you changed the pyinstalive.ini file so drastically badly?
Old:
[pyinstalive]
username = johndoe
password = grapefruits
download_path =
download_lives = True
download_replays = True
download_comments = true
show_cookie_expiry = True
log_to_file = True
ffmpeg_path =
run_at_start =
run_at_finish =
use_locks = True
clear_temp_files = False
do_heartbeat = True
proxy =
skip_merge = False

New:
[pyinstalive]
username = johndoe
password = grapefruit
download_path =
ffmpeg_path =
download_comments = True
cmd_on_started =
cmd_on_ended =
clear_temp_files = False
use_locks = True
no_assemble = False
log_to_file = True

Where is  download_replays, show_cookie_expiry ?
Why the name run_at_start, run_at_finish, changed in cmd_on_started, cmd_on_ended. There is no sense? cmd?
Where is clear_temp_files, do_heartbeat, proxy.?
And why do you swap clear_temp_files and use_locks before it was sorted.
no_assemble, Bro skip_merge was the best. And log_to_file was in the old file over skip_merge
All these things we needed.
Where is the help? Old Version 3.2.4 https://github.com/UnixCro/PyInstaLive
You can find a list of frequently asked questions here.
You can find a list of available commands and an explanation of the configuration file here.

Downgrade to 3.2.4!

I urge everyone not to download this version and download V3.2.4 instead.
I studied PyInstaLive in detail and gave presentations about it. Even if you wouldn't expect it from my spelling, it's probably because of the frustration. The people who are new don't know what it was like before.
I will explain PyInstaLive in detail, in detail and also explain why the parts left out are so important in Version 4.0.0 and why they help us more.
pip install<EMAIL_ADDRESS>

I stripped it down to the bare essentials so that there is less chance of features breaking over time and interfering with the rest of the script. 4.0.0 now fully uses the web API which is more reliable than using third party packages which depend on the app API. And it's less effort to make changes to the API related code if anything no longer works properly

cmd is shorthand for command
download_replays was removed because replays no longer disappear after 24 hours and they are now categorized as normal videos on an user's profile
show_cookie_expiry is removed as a configuration entry, instead the expiration date will now always be shown
clear_temp_files still exists
do_heartbeat is removed as a configuration entry, it's now always used to obtain information about the livestream (you can remove it in a fork but it will cause various bugs)
proxy was removed because I don't have any proxies to test with

Some other configuration entries just ended up having different names while I rewrote the entire script. No particular reason for the changes just deal with it
The order of the entries in pyinstalive.ini doesn't matter so not sure why you decided to complain about that
I removed the FAQ and MOREHELP pages because they were heavily outdated and most of the script's commands and configuration options are pretty self explanatory.
You're free to fork this project and make any change you want. Or keep using the older version where half of the features are broken

Hello Dirk,
Thanks for your quick reply.
I think you misunderstood my post. The problem is that I don't think version 3.2.4 poses any problems at all and I found the options that PyInstaLive still used there extremely useful. I really don't understand why they bother to degrade PyInstaLive and then portray me as a very bad person just because I tell the truth that the program has gone bad.

 Very sad and disrespectful!

Yes, but I, as a daily PyInstaLive user and honorer, am not at all grateful. Most people don't care if something got worse or better. But those who have benefited from something so much, they honor something down to the last detail, and if the developer then makes crap out of the program, what should I be thankful for?

I stripped it down to the bare essentials so that there is less chance of features breaking over time and interfering with the rest of the script. 4.0.0 now fully uses the web API which is more reliable than using third party packages which depend on the app API. And it's less effort to make changes to the API related code if anything no longer works properly.

I think they are trying to talk good here version 4.0.0. If you mean that version 3.2.4 is a privacy vulnerability, which I actually can't quite understand because we only download live streams... Alright then it wouldn't have been a problem if they introduced the privacy improvement, but the rest would have left unchanged.

cmd is shorthand for command. Not much else to say about that.

But what about run_at_start. Don't think it sounds better than cmd_on_start. I mean we grew up with run_at_start.
  download_replays was removed because "Replays" no longer disappear after 24 hours and they are now categorized as normal videos on an user's profile. Ergo it's out of scope for this script which focuses on livestreams.
Didn't you even mention in your old ReadMe file that people with unupdated Instagram app can still post replays?

show_cookie_expiry still exists, the expiration date will now always be shown.

And why is it always displayed, can't you leave it as is to be able to decide for yourself whether it should be displayed or not. PyInstaLive already has a lot of output anyway, the terminal window is already well filled.

do_heartbeat still exists, it's now always enabled to obtain necessary information about the livestream status (you can remove it in a fork but it will cause various bugs).

That's not right at all. Disabling a heartbeat has never caused any problems, even the old message "Could cause performance degradation" when you turned it off back then is absolutely wrong and we discussed that in another Github issue back then, if you want I'll look for it for you Out.
do_heartbeat was the most important function that PyInstaLive had. They have no idea how nice it was to download live streams without the owner knowing they were watching. There was someone with such an extreme advantage, you can't believe it.
Just imagine what your girlfriend would say if she were watching and what she would say if she wasn't watching.
livestream_dl always had a heartbeat, you still had the opportunity to exhibit it back then. But now it's always on and I hate version 4.0.0.

proxy was removed because I don't have any proxies to test with and probably wasn't used that much.

But why remove it? They have changed so much and weren't able to quickly pull any nh proxy from the network and test whether it works with the new version. Instagram is notorious for blocking. Pyinstalive3.2.4 was smart and was able to do something about it. Other users in the Github issue also praised the proxy feature for getting banned. They even mentioned back then in the ReadMe file that if you write a script to monitor a live stream for minutes, you might get banned and use the proxy. Simply omitted in version 4.0.0.

FAQ and MOREHELP were heavily outdated. Most of the available configuration and arguments are self explanatory.

It would have continued to work to this day if the replays thing had been removed. One can really argue about whether it is still relevant now. If I'm honest. But many things were explained in the ReadMe file, now you can't find anything anymore only that the developer has switched to version 4.0.0.

The order in which configuration entries are listed in pyinstalive.ini doesn't matter.
And why don't you leave the order as it was. Should it confuse us even more? You are aware that pyinstalive always screams a pyinstalive.ini

The only 'big' feature that was lost is checking if any users from your following list have any available livestreams. I may add it in a future update but as you know active development has ended and your disrespectful issue does not encourage me to further work on it.

If you hadn't switched to version 4.0.0 it wouldn't have happened either.

What do you think about the proposal to reset everything to the state of version 3.2.4 and to simply install it with the web API if you have such big data protection problems?  Or is something wrong?  Can I help you in any way?  What can I do for you?

What do you think about the proposal to reset everything to the state of version 3.2.4 and to simply install it with the web API if you have such big data protection problems?  Or is something wrong?  Can I help you in any way?  What can I do for you?
Best regards
UnixCro

It doesn't have anything to do with data protection, I switched to the web API because plenty of people were having authentication issues with the app API, and the app API can break completely at any time with no way for me to fix it
There will be no rollback.  You're not forced to update to the latest version, you can keep using 3.2.4 for as long as you want, all the older versions are available by tag anyway https://github.com/dvingerh/PyInstaLive/tags all you need to do to install a different version is specify the version tag in the pip command
I don't use this script anymore, no reason for me to invest any more effort into adding the extra features the old version has, my only goal was making sure the core functionality keeps working (ability to download livestreams)
Maybe some other time i'll readd the features and look for a workaround for the heartbeat request (which I have to rely on now to get livestream health status unlike the app API) and maybe readd some features that were lost

I won't comment on that now... Anyone who has read through this, just trust me, just don't use Version 4.0.0 ...
pip install<EMAIL_ADDRESS>

@dvingerh How about you at least keep the schema from the old PyInstaLive version?
[pyinstalive]
username =
password =
download_path =
ffmpeg_path =
download_comments =
cmd_on_started =
cmd_on_ended =
clear_temp_files =
use_locks =
no_assemble =
log_to_file =

in
[pyinstalive]
username =
password =
download_path =
log_to_file =
ffmpeg_path =
cmd_on_started =
cmd_on_ended =
use_locks =
clear_temp_files =
no_assemble =

or better with the old vocabulary
[pyinstalive]
username =
password =
download_path =
log_to_file =
ffmpeg_path =
run_at_start =
run_at_finish =
use_locks =
clear_temp_files =
skip_merge =

We have already figured out that they will be adding the do_heartbeat feature back soon, but what about --organize and --no-lives is there anything else to come from your side?
I do not think they will switch --generate-videos back to --assemble, but maybe I will get lucky elsewhere.

@dvingerh How about you at least keep the schema from the old PyInstaLive version?
[pyinstalive]
username =
password =
download_path =
ffmpeg_path =
download_comments =
cmd_on_started =
cmd_on_ended =
clear_temp_files =
use_locks =
no_assemble =
log_to_file =

in
[pyinstalive]
username =
password =
download_path =
log_to_file =
ffmpeg_path =
cmd_on_started =
cmd_on_ended =
use_locks =
clear_temp_files =
no_assemble =

or better with the old vocabulary
[pyinstalive]
username =
password =
download_path =
log_to_file =
ffmpeg_path =
run_at_start =
run_at_finish =
use_locks =
clear_temp_files =
skip_merge =

We have already figured out that they will be adding the do_heartbeat feature back soon, but what about --organize and --no-lives is there anything else to come from your side?
I do not think they will switch --generate-videos back to --assemble, but maybe I will get lucky elsewhere.

do_heartbeat still exists, it's now always enabled to obtain necessary information about the livestream status (you can remove it in a fork but it will cause various bugs).

@dvingerh sorry for the ping, but does this means that in v4.0 my user will appear as an active viewer even if heartbeat is set to false?

Yes, and heartbeat can't be set to false because I need to rely on it (for now) to obtain the livestream status (whether it's still active or interrupted, etc)
You can fork the project and remove the function altogether but it'll cause buggy/weird behavior in return
There's a different endpoint I can use to get the livestream status but it's not meant to be called every few seconds and will likely just result in rate limiting or a blocked account. Need to do more testing for that sometime
So you can either choose to keep using the older version whose API reliability is sketchy at best but has more features or use this version which is less prone to break in some way but has less features

I won't make an angry statement, because I'm feeling lucky to have this script.
But I will stay @ 3.2.4 for now aswell and can only recommend that.
"do_heartbeat" (false) is very important to me. It has been discussed already. It makes no sense to appear as an "active user", because you can't interact with the person that is livestreaming. (unless you actually watch + use the script at the same time)
I assume most ppl don't want to be shown as a viewer.
"checking if any users from your following list have any available livestreams" you named it. It's a big loss in the newest version 4.0.0. This function makes it very easy without any or much scripting/coding to monitor for ongoing live streams.
My system is automatically running "--download-following" whenever Instagram sends a live notification through Chrome browser which is also triggering windows notifications. To me it would be a difficult task to filter what exact account is livestreaming and only use download function for that account.
So, long story short. I can only hope for these 2 essential functions to be implemented again.
I'm happy to see any work/developement/maintenance put into pyinstalive.

I already made a few changes bringing those features back + proxy, just not committed yet
Needs a bit more testing but I'll commit it later today so you can give it a go yourself
To install v4 with the very latest changes just omit the version tag from the install command

My system is automatically running "--download-following" whenever Instagram sends a live notification through Chrome browser which is also triggering windows notifications. To me it would be a difficult task to filter what exact account is livestreaming and only use download function for that account.

That's extremely cool. That would save me a lot of work. Would you be so kind and tell me how something like that?
Best regards
UnixCro

Made a beginning for re-implementation of

--download-following argument
proxy configuration file entry
send_heartbeat configuration file entry

Install with latest commits using pip install git+https://github.com/dvingerh/PyInstaLive.git

Wow Dirk! Thanks for that man. But the first thing that strikes me is some weird things.
In V3.2.4
$ pyinstalive
---------------------------------------------------------------------------
[I] PYINSTALIVE (SCRIPT V3.2.4 - PYTHON V3.8.9) - TT-MM-JJJJ HH:MM:SS AM/PM
---------------------------------------------------------------------------
[W] Could not find configuration file, creating a default one.
[W] Edit the created 'pyinstalive.ini' file and run this script again.
---------------------------------------------------------------------------

In V4.0.X
---------------------------------------------------------------------------
[I] PYINSTALIVE (SCRIPT V4.0.0 - PYTHON V3.8.9) - TT-MM-JJJJ HH:MM:SS AM/PM
---------------------------------------------------------------------------
[E] No known arguments were provided.
---------------------------------------------------------------------------

The message that a default configuration file was created is missing. No configuration file was made …

$ pyinstalive -h
---------------------------------------------------------------------------
[I] PYINSTALIVE (SCRIPT V4.0.0 - PYTHON V3.8.9) - 06-17-2022 10:11:57 AM
---------------------------------------------------------------------------
usage: pyinstalive [-h] [-u] [-p] [-d] [-df] [-i] [-cl] [-cp] [-dp] [-dc] [-gc] [-gv] [-na]

PyInstaLive 4.0.0 using Python 3.8.9

optional arguments:
  -h, --help                  show this help message and exit
  -u , --username             Instagram username to login with.
  -p , --password             Instagram password to login with.
  -d , --download             Instagram username whose livestream you want to download.
  -df, --download-following   Check for available livestreams from people you're following.
  -i, --info                  Shows information about PyInstaLive.
  -cl, --clean                Clean the current download path of all temporary files.
  -cp , --config-path         Override the default configuration file path.
  -dp , --download-path       Override the default download path.
  -dc, --download-comments    Download livestream comments. Overrides the configuration file setting.
  -gc , --generate-comments   Generate a comments log file. Requires a livestream JSON file.
  -gv , --generate-video      Assemble downloaded livestream segments into a video file. Requires a livestream segments folder.
  -na, --no-assemble          Do not assemble the downloaded livestream segments into a video file. Overrides the configuration
                              file setting.

I would move the --info and --clean parameters a bit more to the right.

[pyinstalive]
username = johndoe
password = grapefruits
download_path =
ffmpeg_path =
download_comments = True
cmd_on_started =
cmd_on_ended =
clear_temp_files = False
use_locks = True
no_assemble = False
log_to_file = True

I don't know where send_heartbeat (V3.2.4 do_heartbeat) and proxy is. Maybe extra like this?
Ok, I have now established that either you leave out both or you add both. You can't choose. I would suggest always including these arguments as a standard.

Also, the quality has changed for me. But I can't confirm it 100% and ask others to test it too. My computer is going crazy with the constant pip install+git switching.
https://user-images.githubusercontent.com/70098046/174261331-dbece33e-b535-4e62-be80-30cef3c6ef42.mp4
In V4.0.X it seems to me that the picture gets warmer. But I'm not sure …

Even if I don't like the ending .dat, before .lock. And even if there is no --organize parameter. And even if I don't like the PyInstaLive output at all as in V3.2.4.  Am I grateful that you're trying to improve <3
Best regards
UnixCro

The message that a default configuration file was created is missing. No configuration file was made …

This has been fixed

I would move the --info and --clean parameters a bit more to the right.

I have no control over this

Even if I don't like the ending .dat, before .lock.

The .dat file is your saved login session. Don't delete that. The .lock files still exist as usual

Just pushed 4.0.1: https://github.com/dvingerh/PyInstaLive/releases/tag/4.0.1

Gave all this a read and just dumbfounded by the sheer entitlement and ignorance. Props to you for continuing to implement the changes especially after all that.
That being said, perhaps you should consider adding the ability to sponsor your GitHub or donation links such as a wallet address for those who wish to support you to further development for this tool. After all, with so much nitpicking and complaints I've read in this thread, probably should be charging at this rate for spending your time after you've already mentioned you're no longer actively working on this.

I prefer positive feedback over donations, thanks
Re-implementing the missing features was less work than anticipated and I would have done it eventually anyway so I just got it over with

-df command is not working in 4.0.2. Below error is thrown:

No problems here with both the executable and when installed with pip
Have you done as the error says?

-df command is not working in 4.0.2. Below error is thrown:

No problems here with both the executable and when installed with pip Have you done as the error says?

Yes. No problem with any other command. Maybe this error is because I'm using a windows machine?

I also use a Windows machine so that's not the problem.
What's the output of the command where pyinstalive?

I always found the default/MS store installation of Python and pip to cause problems so I would recommend uninstalling it and using the normal installer from here: https://www.python.org/downloads/
Make sure to check the relevant boxes in the installer (like adding Python to PATH and installing pip in the extra options menu)

-> tested v 4.0.2
--> downloaded 1 livestream
---> now that acc is shadowbanned or something?
Message in command line:
[E] Could not get livestream information: Expecting value: line 1 column 1 (char 0)
Message in web version when I click on any live stream:
"This webpage is not available"
(And yes, I tested watching those lives with another account on the web version and it works. It does not display "This webpage is not available")
While downloading with another account i received the following message:
Exception in thread Thread-1: Traceback (most recent call last):   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\threading.py", line 954, in _bootstrap_inner     self.run()   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\threading.py", line 892, in run     self._target(*self._args, **self._kwargs)   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\site-packages\pyinstalive\helpers.py", line 183, in handle_tasks_worker     globals.download.update_stream_data(from_thread=True)   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\site-packages\pyinstalive\download.py", line 279, in update_stream_data     stream_heartbeat = api.do_heartbeat() if globals.config.send_heartbeat else api.get_stream_data()   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\site-packages\pyinstalive\api.py", line 45, in get_stream_data     return json.loads(response.text)   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\json\__init__.py", line 346, in loads     return _default_decoder.decode(s)   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\json\decoder.py", line 337, in decode     obj, end = self.raw_decode(s, idx=_w(s, 0).end())   File "C:\Users\Username\AppData\Local\Programs\Python\Python39\lib\json\decoder.py", line 355, in raw_decode     raise JSONDecodeError("Expecting value", s, err.value) from None json.decoder.JSONDecodeError: Expecting value: line 1 column 1 (char 0)
I don't know if that helps or is just another random error.
Anyways, that 2nd account is now on "challenge required" (after 1 download).
I already reinstalled v 3.2.4.
Now downloading with my first account works even when I can't watch in the web version. I can watch in the mobile app. So the api mode still works.
No idea what causes all those problems with the newest version. I didn't expect this at all.


Add coverage for TestWorker and FetchLinksEmbedData.

This addresses #6542 .

@timabbott rewrote the test. It should now basically be a complete simulation of the steps outlined in my comment.

Added a second commit for having a full test flow through the DigestWorker. The handle_digest_email is really heavy and takes around ~0.04 seconds. test_inactive_users_queued_for_digest queues 26 inactive users in total, so that amounts to ~0.8 seconds for the test to complete. I think we can limit the test to some percentage of all users?

Yeah, for Digest emails, I'd only have it runs for the first two, and have the rest return early.

Updated. Moved the full-flow tests into test_active_users_not_enqueued; the for loop here gradually makes inactive users active, so it's more natural to test the full flow for the last two users. test_inactive_users_queued_for_digest on the other hand starts without inactive users only and makes them explicitly inactive.

Nice, merged, thanks @derAnfaenger!


Not fully undetectable

I wanted to test this and noticed that:
Unencryped - 43/70 engines detected it.
Encrypted - 39/70 engines detected it.
There isn't much change...

PEunion does a good job at binding multiple executables. However, I'm aware that the encryption part lacks behind. In fact, the decrypted file written back to the disk makes this design overhauled. Since my two most recent projects are both 100% fileless, PEunion should also execute decrypted files in memory.
Therefore, a technological overhaul of PEunion is on the agenda for this year. The goal is to compile the output binary as a native assembly with no file drops whatsoever and compile time & runtime obfuscation to be undetectable by both signatures and heuristically. There's a lot room for improvement everywhere.
I cannot make any promises for when the next major version will be released, but I just wanted to share some of the plans.

Actually I think this program by itself is not very good for bypassing common avs, however if you pair it with other free crypters on github it can bypass windows defender with no problem. It is quite good as a binder because you can add exclusions for windows defender using a simple PowerShell script. Here are my results after using this with another crypter on github

trước khi có bản mới, tôi có thể sửa lỗi này bằng cách nào đó. làm ơn

Nếu bạn đang tìm cách tự khắc phục sự cố này, bạn có thể thử thay thế CompileAssemblyFromSourcebằng CompileAssemblyFromFiletrong mã và xem liệu điều này có giải quyết được sự cố hay không. Nếu không, bạn có thể thử nghiên cứu & sửa lỗi;) Công việc kinh doanh hàng ngày của một lập trình viên ... Chúc may mắn! Tôi sẽ đăng tất cả các vấn đề GitHub hiện đang mở bất cứ khi nào có phiên bản mới.

tôi có thể liên lạc với bạn bằng cách nào. tôi cần trợ giúp , làm ơn

help me

CompileAssemblyFromFile accepts a path to a file, not a string containing C# code. As I have mentioned in the main page, PEunion is provided "as-is" until the next major release is available to everybody. In the meantime, I would suggest you to get familiar with CodeDom. I don't have the time to support you with basic debugging and problem solving. So, I would kindly ask you to put in the effort, if you want to fix a bug in the code. I will continue working on PEunion 4.0.

Tôi hi vọng bản PEunion 4.0 được ra mắt sớm nhất

PEunion 4.0.0
The new version of PEunion has been released. All currently open GitHub issues were addressed in the release. Additionally, the new version is a complete rewrite and addresses known issues by fundamental architectural changes.
For more info, please read the main page of PEunion to get an overview over features & functionality.
This message was posted in all currently open GitHub issues.
It there are any issues in the new version, I would like to ask everybody to create a new GitHub issue instead of posting here. This way, I will have a better overview over issues in PEunion 3.x vs 4.0


Install with composer

Hello,
first of all thanks for this CMIS client.
I'd like to use it an Drupal 8 module and try install with composer:
$ composer require dkd/php-cmis
but it is not able:

Using version ^1.0 for dkd/php-cmis
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Can only install one of: guzzlehttp/guzzle[5.3.x-dev, 6.2.1].
- Can only install one of: guzzlehttp/guzzle[6.2.1, 5.3.x-dev].
- Can only install one of: guzzlehttp/guzzle[6.2.x-dev, 5.3.x-dev].
- Can only install one of: guzzlehttp/guzzle[5.3.x-dev, 6.2.1].
- dkd/php-cmis v1.0.0 requires guzzlehttp/guzzle ~5.0 -> satisfiable by guzzlehttp/guzzle[5.3.x-dev].
- Installation request for dkd/php-cmis ^1.0 -> satisfiable by dkd/php-cmis[v1.0.0].
- Installation request for guzzlehttp/guzzle ^6.2.1 -> satisfiable by guzzlehttp/guzzle[6.2.1, 6.2.x-dev].
Installation failed, reverting ./composer.json to its original content.

Please let me know what is the right way to install it with composer?

We currently require guzzle 5.x, but it seems that you require guzzle 6.x somewhere in your composer.json or from another dependency. We should look into updating to Guzzle 6 though.

Yes you are right. Drupal 8 core (or symphony) use guzzle version 6.2.

@NamelessCoder how much effort would be an upgrade to 6?

Should pretty much be a formality - if anything does need to be updated in terms of API usage we have only very few usages to update.

I can probably take a look at this later tonight if we want to go ahead with it!

@dkd-dobberkau - your call

Talked with Olivier, Claus could you look into updating to 6 please.

Will do!

Thanks for fast and positive feedback!
Please let me know where can I setting the ignoreFailures variable because if I try populating the sample repo of alfresco (https://cmis.alfresco.com/alfresco/api/-default-/public/cmis/versions/1.1/browser) get this error

[:error] [pid 5560] [client <IP_ADDRESS>:36397] Uncaught PHP Exception Dkd\Populate\AccessException: "No "set" method(s) can be determined for property choice" at /home/webdev/d8-no-paragraph/modules/custom/cmis/vendor/dkd/php-populate/src/PopulateTrait.php line 266

The setPopulatedProperty function description tell:

Sets a single property via the resolved setter method,
throws a Dkd\Populate\Exception if no method could be found
and $ignoreFailures was false.

but I did not found where set or where use this variable.
Thanks again!

@dj1999 are you using our master branch or a numbered release version? The master branch should not be affected by this error (which is caused by semantic issues with naming of the choice/choices property). See also https://github.com/dkd/php-cmis-client/commit/2605c3bbfdcb265e163c0e8165e441c4009e6623

I had installed with command: composer require "dkd/php-cmis": "^1.0"
What is the recommended install process?

That is the recommended approach - temporarily you can switch to dev-master which should fix the issue. I will look into creating a new release as well.

We could do the guzzle upgrade and then tag.

That is my plan :) I ran into a few issues that require a new alfresco test VM so I had to delay this task until later tonight.

@NamelessCoder Thanks this https://github.com/dkd/php-cmis-client/issues/28#issuecomment-248535257 works fine.


Unable to locate turtlebot3_navigation package to chgn the paramters for the navigation

ISSUE TEMPLATE ver. 0.4.0

Which TurtleBot3 platform do you use?

[ ] Burger
[ ] Waffle
[x] Waffle Pi

Which ROS is working with TurtleBot3?

[x] ROS 1 Kinetic Kame
[ ] ROS 1 Melodic Morenia
[ ] ROS 1 Noetic Ninjemys
[ ] ROS 2 Dashing Diademata
[ ] ROS 2 Eloquent Elusor
[ ] ROS 2 Foxy Fitzroy
[ ] etc (Please specify your ROS Version here)

Which SBC(Single Board Computer) is working on TurtleBot3?

[ ] Intel Joule 570x
[x] Raspberry Pi 3B+
[ ] Raspberry Pi 4
[ ] etc (Please specify your SBC here)

Which OS you installed on SBC?

[x] Raspbian distributed by ROBOTIS
[ ] Ubuntu MATE (16.04/18.04/20.04)
[ ] Ubuntu preinstalled server (18.04/20.04)
[ ] etc (Please specify your OS here)

Which OS you installed on Remote PC?

[x] Ubuntu 16.04 LTS (Xenial Xerus)
[ ] Ubuntu 18.04 LTS (Bionic Beaver)
[ ] Ubuntu 20.04 LTS (Focal Fossa)
[ ] Windows 10
[ ] MAC OS X (Specify version)
[ ] etc (Please specify your OS here)

Specify the software and firmware version(Can be found from Bringup messages)

Software version: [x.x.x]
Firmware version: [x.x.x]

Specify the commands or instructions to reproduce the issue.

HERE

Copy and Paste the error messages on terminal.

HERE

Please describe the issue in detail.

Hi Im still new to the turtlebot3 and ROS and general. I followed the Turtlebot3 E-manual guide: https://emanual.robotis.com/docs/en/platform/turtlebot3/quick-start/ to install the necessary items. However, i realized that i am unable to locate the file where turtlebot3_navigation is stored in order for me to edit the parameters. May i know do i have to download this separately? Thank you

You could find your package with the rospack find cli on your terminal as below.
$ rospack find turtlebot3_navitgation

If you don't see any result from the above command, make sure to source the ROS setup script.
$ source ~/opt/ros/kinetic/setup.bash

If ROS has not been installed correctly due to the recent GPG key expiration incident, please update your key as described in the below thread.
https://discourse.ros.org/t/ros-gpg-key-expiration-incident/20669
$ curl -s https://raw.githubusercontent.com/ros/rosdistro/master/ros.asc | sudo apt-key add -

Thank you.

I was able to locate the file using rospack find. Thank you very much!


gitree -m - output 'no modifications' message if there are no modifications

When I run git status on a clean branch, I get a message saying there are no changes.
When I run gitree -m, there is no output. This is a bit confusing, because I'm not sure if the command ran successfully or not.

(By the way, really cool package! It really helps me)

This is a great suggestion. Open to PRs for this before I have time to get around to it. :)


Project 4 (Testing & RPA)

UI Automation cloud account should be created and I should familiarize with it, more research will be done for this project.


submit package to packagist and psr-4

Hello,
i have test the firelogger.
A great tool.
I have 2 wishes.
Can you submit the firelogger to packagist ?
Can you rebuild the firelogger to psr-4 ?
Your sincerly
Stephan

Hi Stephan,
I don't maintain this tool anymore. I have done my last contribution in 2012. Someone else has to step in.


nginx still doesn't respect kubernetes.io/ingress.class

Created image from master, deployed. After deploy I get into a race between gce and nginx-controller both trying to update the ingresses.
2017-03-09T14:12:44.788002059Z I0309 14:12:44.787978       5 launch.go:99] Watching for ingress class: custom-nginx
...
2017-03-09T14:12:44.868066319Z I0309 14:12:44.867939       5 controller.go:172] ignoring add for ingress jenkins based on annotation kubernetes.io/ingress.class
...
2017-03-09T14:13:15.142941425Z I0309 14:13:15.142918       5 status.go:154] I am the new status update leader
2017-03-09T14:13:44.875652937Z I0309 14:13:44.875617       5 status.go:275] updating Ingress jenkins/jenkins status to [{x.x.x.x }]

When I added a debug line in updateStatus, and logged the result of ing.GetAnnotations()["kubernetes.io/ingress.class"], is see that its updating an ingress with wrong ingress.class.

What is the annotation you have in your Ingress resource?

I have tried this where I want it to be picked up;
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: test
  annotations:
    kubernetes.io/tls-acme: "true"
    kubernetes.io/ingress.class: "custom-nginx"
    ...

but my jenkins has this;
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: jenkins
  namespace: jenkins
  annotations:
    kubernetes.io/ingress.global-static-ip-name: "jenkins-frontend"
    kubernetes.io/ingress.class: "gce"
    kubernetes.io/tls-acme: "false"
    ...

... and should not be picked up

I had similar issue trying to deploy 2 NGINX Ingress Controllers with different classes. Sadly currently don't have time to reproduce and write full bug report.

@goddva I can reproduce this issue. Fix will be included in tomorrow release


fix: add empty registers tag if it doesn't exist

Doesn't look like this CI failure is due to this PR, so merging manually.


Add new fonts for titles/headers

TBD if this is still necessary, the current font is pretty decent


Support OSX's default configuration paths

Like unix-like and windows paths, configuration locations common to OSX should be added to the default load order.

[ ] find system-wide default directory for configuration
[ ] find user default directory for configuration

Python package appdirs uses ~/Library/Preferences/ as the return value for user_config_dir and /Library/Preferences for site_config_dir, which seem very usable.


Reverse engineer visual model from a schema (excluding enums and unions for now)

Given an input flatbuffer schema, produce a visual representation of that schema:
https://google.github.io/flatbuffers/flatbuffers_guide_writing_schema.html

Should support copy and paste as well as importing files.


PMID:25543137

new1: increased cellular protein aggregate level during cellular response to heat (cf fypo:4180)
new2: decreased duration of heterochromatin maintenance involved in chromatin silencing at centromere outer repeat (cf fypo:4544, fypo:4744)
new3: decreased protein localization to nucleus, with protein mislocalized to cytoplasmic foci (cf. fypo:4056, fypo:3191)

increased cellular protein aggregate level during cellular response to heat FYPO:0004808
decreased duration of heterochromatin maintenance involved in chromatin silencing at centromere outer repeat FYPO:0004809
decreased protein localization to nucleus, with protein mislocalized to cytoplasmic foci FYPO:0004810

edit file: 4f92866058675ecf5624b404050649e5cca2545c
release: 44608c390480250c6aee5a0f2a00aae8dfb12d72


Parameterized key_gen salt to support BBS

The current key_gen implementation uses hardcoded salt  as BLS-SIG-KEYGEN-SALT-.
We want to use blst for BBS signatures. In BBS signatures spec, avaialble here, key_gen salt is defined as BBS-SIG-KEYGEN-SALT-.
I was wondering if the key_gen function can be parameterized:

dynamically using a function parameter for salt
or statically with a compile-time macro

Thanks for your detailed reply. I was following the recommendation that the use of different salt strengths HKDF and eventually security of secret key in case we use same key_gen to derive more secret keys in an application. And the other reason is that a BBS key should be derived using BBSed salt(not BLSed salt). :)

in case we use same key_gen to derive more secret keys in an application.

That's what the key_info parameter for. One is supposed to use different parameters to derive different keys. Or use independent IKMs. Or use independent keys without using any specific KeyGen procedure. Again, KeyGen is just a recommendation...

And the other reason, a cosmetic one, is that a BBS key should be derived using BBSed salt(not BLSed salt).

Well, that's not how I read the referred specification. Different salt is not the only (cosmetic) difference. So what would be the point of putting an effort into accommodating parameterized salt if it won't be compliant anyway?

I am convinced it's not worthful to put any effort into this as of now. Even if it becomes a compliant requirement, you rightly mentioned there are other factors like the choice of hash functions and then a better choice would be to implement key_gen at the application side.

TL;TR I would like to use a different salt for bbs, based only on paranoia of ensuring the required "setup" for hkdf.
My main worry is that people may not realize that those are the same functions and treat them as independent (for example use the “bls" KeyGen for a DH exchange and the “bbs" KeyGen to get a bbs key from the result, without realizing that both KeyGen functions are the same). Something like that will invalidate the security analysis of hkdf (mainly the extractor part). Also the info field will help but will not actually solve the issue (when it comes to the extractor at least).
Note also this does not have to do with been compatible to the bbs spec, since, as you noted, the KeyGen function is optional (also we do work currently to add sha256 based cipersuites). It is mostly about my paranoia regarding the theoretical security results of hkdf.
That said I completely understand the blst members not wanting to take up the work and that it could be easier to implement an application layer KeyGen.

The opposition is not actually against the work per se, but rather against doing things for insufficiently justified reasons. Or in other words, if the salt was in fact the only difference, it wouldn't be a problem to add say blst_keygen_bbs. So as soon as you add sha256-based ciphersuite, just drop a note with reference to this issue:-)

That sounds good! Thanks!


Backdoor-apk

Appreciate the pull request but there is no added functionality that makes a compelling case to merge from the forked project into the original project.


Not Always 403 Error

I used the powershell command to disable access:
Set-SPOSite -Identity "" -LockState NoAccess
It is indeed effective at preventing access. However, this page indicates that it will produce a 403 error if you don't enable a redirect. However, this is only sorta true.
OneDrive desktop app -- sign-in not allowed. Good.
Going to exact  does produce a 403 error. However, I don't see a command to hide the app from tehapp launcher on a per user basis (please share if I've missed that). So, when you click the app launcher, it takes you to a page that partially loads, which is a bit confusing. I think this is because that link takes you to a slightly different URL.
So, for example, if I were doing this for Bill Gats, I'd run:
Set-SPOSite -Identity "https://microsoftcom-my.sharepoint.com/personal/bgates_microsoft_com" -LockState NoAccess
However, the app launcher would take him to something like this:
https://microsoftcom-my.sharepoint.com/personal/bgates_microsoft_com/_layouts/15/onedrive.aspx?login_hint=bgates%40microsoft.com&view=3
In the latter, you get a partially loaded page with a blank frame. It mostly works, but it would be good for the powershell command to result in a 403 for anything https://microsoftcom-my.sharepoint.com/personal/bgates_microsoft_com/*
Also, we need a similar command to dynamically do this for all members of a security group, though I understand that is outside the scope of this article.
Thank you.

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

ID: bea1ac5a-f66c-3678-e5e5-7672407d395f
Version Independent ID: 00fffbdd-9663-2441-a5e8-2bf541f7b1d1
Content: Lock and unlock sites - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/manage-lock-status.md
Service: sharepoint-online
GitHub Login: @MikePlumleyMSFT
Microsoft Alias: mikeplum

Hello @DontNeedNoGit
I think this is a very specific case when using de lock against a OneDrive site while the owner tries to browse it from the launcher.
Please let me know if I understood you correctly.
Thanks

I would say this is not a "very specific case" that is outside the bounds of the support article. The article explains how to lock access to a , which is my goal. I don't want these users to access their OneDrives, and it should produce a 403b error as described in your support article. However, the app launcher button does not produce that error. I wouldn't call usage of the app launcher a "very specific case." That's how many users get to their web apps.

Hello @DontNeedNoGit
I think you misunderstood me, I am trying to understand better what you are trying to do, so I can understand if there is a need to edit the article.
I tried and could reproduce what you describe, however, it seems that currently is the way it works if OneDrive is selected from the Launcher, as you said, because of the URL being slightly different.
I'll try to report this to the team, however, a support case opened from your side would also be helpful to reach the team that can make the required adjustments to the behavior of the launcher.
Thanks for the feedback,

The article incorrectly states that a 403b error will occur. That doesn't happen with the app launcher, which I'd suggest is the main way people access it. That error only happens if someone has a shortcut to one specific URL for their OneDrive (other shortcuts won't produce a 403).
I understand a support ticket might help, but that is a huge time sink for me for them to tell me it's "working as designed" and I have to submit a DCR.
So if you think that's the only way for this to create a consistent experience, then perhaps the article should be updated to say "a 403b error will sometimes appear. Other times a partially loaded page will appear."

@DontNeedNoGit Managed to report this to the product group, and I'll wait for feedback before any update to the article.
Thank you!

I asked the article's author and the decision is to leave the article as-is. Also managed to report about this to the OneDrive's team.
@scanum


Merge branch "solombrino" into "main"

Update Solombrino avatar, short bio, long bio, interests, and email address

👷 Deploy Preview for gladia processing.

Name
Link

🔨 Latest commit
5027da33c0ba7c650b8a9ea0987c74935be5db1a

🔍 Latest deploy log
https://app.netlify.com/sites/gladia/deploys/672e5cbbe730cd0008c646d5


Lucas part2

Part 2 Fix
Github Issue Number Here: <YOUR_GITHUB_ISSUE_NUMBER_HERE (include the hashtag)>
What user problem are we solving?
What solution does this PR provide?
Testing Methodology
How did you test your changes and verify that existing
functionality is not broken
Any other considerations

https://drive.google.com/file/d/1iuz_NByOislHfd_mKj8H1TAn7_3sO5b6/view
screen recording of part 2

@LuHG18 looks good to me. Thank you for this PR. Looking forward to your part 3 PR in the beginner project. I'll mark your PR as closed since we will not actually merge these changes into the real DLP app


release 0.5.0

cc @codesome
Signed-off-by: Krasi Georgiev<EMAIL_ADDRESS>

Maybe include #531 in the changelog as a bugfix for a performance regression in the previous version?

@hoffie 	added, thanks


CSS :defined - Appears to be discrepancy between Baseline status and support matrix

See here https://developer.mozilla.org/en-US/docs/Web/CSS/:defined
Baseline banner says support is limited with no Firefox or Safari support, but the caniuse data (see table at the bottom of the page) says it's had full support since versions 63 and 10, respectively.
From my reading there doesn't seem to be implementation/spec discrepancies with Firefox or Safari, so not sure why this would show unavailable for them.

Coincidentally I see #561 was just opened by someone else for the JavaScript counterpart to the API. Perhaps it is the differences in implementation for customElementRegistry.define, which in turn affect whether :defined will match, that accounts for the discrepancy here.

Thanks for the report! This issue and #561 (also #530), are occurrences of the problem described in #495: the banner that MDN currently displays on an individual feature page is that of the group this feature is part of, even though the banner is not explicit about that, which is confusing for readers. We're working on a fix with MDN.
In this case, :defined is part of custom-elements, which contains other features that are not yet widely available. In other words, the data itself is correct. It does not claim that :defined has limited availability.
I had closed #530 as covered by #495, but it's perhaps more useful to keep these issues open so that people bump into them when they consider reporting similar problems.

That makes sense! It would definitely be helpful seeing additional text basically saying "X is part of a broader feature set Y which does not have full support in some of the most widely-used browsers" or something along those lines. Thanks for the response.

Thanks for reporting this, I've added this page (and all others from the custom elements group) to a blocklist on MDN so for now the Baseline banner won't show until we've settled on a more general fix to this problem.


Update uuid-creator to 5.1.0

Updates com.github.f4b6a3:uuid-creator from 5.0.0 to 5.1.0.
Changelog
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.github.f4b6a3", artifactId = "uuid-creator" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "@monthly" },
  dependency = { groupId = "com.github.f4b6a3", artifactId = "uuid-creator" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Codecov Report

Merging #329 (ec1aff1) into main (3180af6) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #329   +/-   ##
=======================================
  Coverage   88.76%   88.76%
=======================================
  Files          91       91
  Lines        2778     2778
  Branches       72       72
=======================================
  Hits         2466     2466
  Misses        312      312

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 8a098e9...ec1aff1. Read the comment docs.


⚠ Heritage of Faith Christian Church - Gold Coast has degraded performance

In f8af0fe, Heritage of Faith Christian Church - Gold Coast (https://heritageoffaith.com.au) experienced degraded performance:

HTTP code: 200
Response time: 14303 ms

Resolved: Heritage of Faith Christian Church - Gold Coast performance has improved in 3713a23.


feat: Integrate react SDK for rendering react templates

Description
Introduces the generator React SDK which enables the rendering of React templates. @magicmatatjahu have provided a rewrite of the markdown-template to react which can be tried with this PR.
What this PR introduces:

New validation rule so only react or nunjucks are allowed as renderer configurations (or none).
Updated authoring.md to include the new react renderer.
Moved any specific nunjucks code into separate utility functions and made a common function for each renderer. This introduced the functions renderFile, configureTemplate and renderAndWriteToFile which each call either react or nunjucks specific code.

TODO before merge

[x] Release the generator React SDK and update the dependency from file to library.
[x] Add some more documentation regarding VSCode debugging.
[x] Figure out if we can remove the requirement of source-map-support and react.

TODO after merge

The generator.js is way to coupled and needs to be broken down. Just look at how problematic it is to separate react and nunjucks code.

Related issue(s)
https://github.com/asyncapi/shape-up-process/issues/35

@magicmatatjahu didnt you change when the registerFilters function was called? Tests are failing 😄

@fmvilas @derberg I am not allowed to merge 🥳

@jonaslagoni @fmvilas you mind wait with merge, I'd like to also review, this is a big change

eh those if-s and else-s 😄
yeah, I know that for now there is no other way doing it
I left some minor comments. What I'm missing is a kind of comparison of what options we had in nunjucks and what is their equivalent in react, kind of matrix to refer to for people familiar with nunjucks engine. I guess that this can be done in a separate PR
I tried your PR manually with nodejs template:
* this file https://raw.githubusercontent.com/asyncapi/asyncapi/2.0.0/examples/2.0.0/streetlights.yml

* I get this in rendered config file

broker:
    mqtt:
      url: mqtt://83

* something ain't right here https://github.com/asyncapi/nodejs-template/blob/master/template/config/common.yml#L30

I'll try to debug later on my own what might be wrong, maybe something on my side 🤷🏼♂

What is the full command you are using? I'll try to replicate it 😄

@jonaslagoni you will have to update to the latest master to enable merge


knative already support initcontainer，can storage be initializer without webhook

/kind feature
I see comment in storage_initializer_injector.go says "This is a work around because KNative does not support INIT containers"
but knative support initContainer now , is that mean we can add initcontainer directly rather than using webhook ?
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]

@homily707 yes we can add the init container in the kserve controller instead of using the pod mutator. This requires a bit refactoring, welcome any contributions! Cc @greenmoon55

I'm glad to help!

The PR for Knative Serving to introduce shareProcessNamespace is here now --> https://github.com/knative/serving/pull/14454


Fake news Detection

💥 Proposal
This model is trained in such a way to predict the fake news with best accuracy.

can you plis assign this issue to me under gssoc 23?

I request you to please assign me this issue under gssoc 2023

Hi, we have several issues on the similar lines. Hence, we cannot assign you this issue.


[Event Request] Codeunit 5760 Whse.- Post Receipt

Hi,
I requested 2 Events in #3217 . The Issue was closed and i was told those Events already exist.
So i pulled the latest bcdocker(i actually was on an old Version). So in the new version i found the event in Function InitSourceDocumentLines and this works for us.
The second Event however is not there.

can you please check again and add this if its not there?
If you got it in your database, how do i get the newest BC version?
I use "docker pull microsoft/bcsandbox:de".
Thanks in advance & sorry for reopening the case

COD5760.TXT
Please find latest version of COD5760 I'm working with and decide if you have what you need or not. Please ask question about Docker command to @freddydk

Hi,
in the txt there is the Publisher I need, So is this the latest released BC version or is it pending to be released?
Thanks

The event already exists. Please read: https://blogs.msdn.microsoft.com/nav/2018/05/03/al-developer-previews-multiple-releases-and-github/


Read line hover details!

I'm not sure if this already exists! But it will be cool to have Line Object return details hover of a line! So it can help when developing an extension!

For example, here I want to get the namespace of that variable!
TextDocument.lineAt(Position).hoverDetails and it will give each word/details array or something

You get trigger the data providers themselves via command: see https://code.visualstudio.com/api/references/commands and find vscode.executeHoverProvider


Same length of Remote Host and Activity bar

To be possible to make the same length Remote Host as it is Activity bar

On a visual level I agree with this. However, we also know that status bar real estate is often super limited, so I'm not sure it's worth the trade off.

Indeed, at least yes, remove that color since the action is not primary.

why not reduce the width of the activity bar?


Updated hbase URL to archive.apache.org

This addresses https://github.com/zsiciarz/vagrant-hbase/issues/14

Thanks! I almost forgot I was using a Polish mirror.


Clarify DWD defaults

Addresses #409

Thanks for getting to this so quickly!
Two thoughts:

The current approach still requires the user to Google the current defaults used in PyTorch. I would strongly prefer to just have defaults in our docstring, rather than pass that indirection to our users.
If we MUST pass that indirection to our users, we should hyperlink the SGD / AdamW:

Argument defaults are copied from torch.optim.SGD. in order to make it convenient.
I have a reasonable preference for #1, but would be willing to hear an argument for #2.

I'm a bit confused, doesn't our docstring already include the defaults, as well as hyperlinks to torch's SGD and AdamW?

I think what is confusing @moinnadeem is that the first method is not __init__, where the defaults are.

Updating and merging after tests pass.. @moinnadeem feel free to reopen if the change, and the comments don't address the issue. But the DWD do seem documented in both the code (__init__) and the docstrings.