CBS? Worked, but now doesn't

Maybe this is just for me, but when I ran this command most recently, it didn't work, whereas it had been working no problem. Any ideas?
youtube-dl http://www.cbs.com/shows/survivor/video/B038A885-94D0-0D47-938B-7BADF048CAB9/survivor-brains-vs-brawn-vs-beauty-the-devils-we-know/
[CBS] survivor-brains-vs-brawn-vs-beauty-the-devils-we-know: Downloading webpage
[ThePlatform] XfH4DAy4QpYp: Downloading SMIL data
Traceback (most recent call last):
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 162, in _run_module_as_main
    "__main__", fname, loader, pkg_name)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/runpy.py", line 72, in _run_code
    exec code in run_globals
  File "/usr/local/bin/youtube-dl/__main__.py", line 19, in <module>
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 412, in main
  File "/usr/local/bin/youtube-dl/youtube_dl/__init__.py", line 402, in _real_main
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 1718, in download
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 679, in extract_info
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 736, in process_ie_result
  File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 668, in extract_info
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 319, in extract
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/theplatform.py", line 234, in _real_extract
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/theplatform.py", line 34, in _extract_theplatform_smil
  File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 494, in _download_xml
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 248, in compat_etree_fromstring
  File "/usr/local/bin/youtube-dl/youtube_dl/compat.py", line 237, in _XML
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1642, in feed
    self._raiseerror(v)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/xml/etree/ElementTree.py", line 1506, in _raiseerror
    raise err
xml.etree.ElementTree.ParseError: syntax error: line 1, column 0

I am having the same problem with both the version from 3/18/2016 and 3/25/2016
youtube-dl -v http://www.cbs.com/shows/big_bang_theory/video/0D36476D-16EC-F0CE-CDA9-5D5956B97CC1/the-big-bang-theory-the-application-deterioration/ [debug] System config: [] [debug] User config: [] [debug] Command-line args: [u'-v', u'http://www.cbs.com/shows/big_bang_theory/video/0D36476D-16EC-F0CE-CDA9-5D5956B97CC1/the-big-bang-theory-the-application-deterioration/'] [debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8 [debug] youtube-dl version 2016.03.25 [debug] Python version 2.7.6 - Linux-3.19.0-51-generic-x86_64-with-Ubuntu-14.04-trusty [debug] exe versions: ffmpeg git-2016-02-15-295de3e, ffprobe git-2016-02-15-295de3e [debug] Proxy map: {} [CBS] the-big-bang-theory-the-application-deterioration: Downloading webpage [ThePlatform] CAtw1PioYHFg: Downloading SMIL data [ThePlatform] CAtw1PioYHFg: Checking video URL [ThePlatform] CAtw1PioYHFg: Downloading JSON metadata [debug] Invoking downloader on u'http://once-aws-us-west-2c.unicornmedia.com/now/od/auto/bb0b18ba-64f5-4b1b-a29f-0ac252f06b68/77a785f3-5188-4806-b788-0893a61634ed/2cfe5a97-97da-4c73-b116-afe93e482a1e/content.once' [download] The Big Bang Theory - The Application Deterioration-CAtw1PioYHFg.once has already been downloaded [download] 100% of 3.21KiB

This issue is already fixed and fix will be incorporated in the next version of youtube-dl.

See our FAQ on how to update to youtube-dl 2016.03.26 or newer, where this is fixed.


Write examples and tracking recipes

Examples: downloadable notebook + in docs. Options: Parse notebook into sphinx, parse sphinx tutorial into notebook?
Recipes can be for example:

cell tracking
single molecule tracking

Tracking recipes will go in motile_toolbox, hopefully soon! @bentaculum Please feel free to add some functions, utils, etc. that you've been using to construct motile pipelines, or just open issues with things you think belong there.
Do the current docs satisfy the examples part of this issue @bentaculum?

Excellent, thanks!


fix(nuxt): access resolved scrollBehaviorType

🔗 Linked issue
https://github.com/nuxt/nuxt/pull/21948
https://github.com/nuxt/ecosystem-ci/actions/runs/5618792731/job/15224930143
❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
We are accessing this.scrollBehaviorType but this is not accessible if the user has provided their own router config. Instead we can access it from the resolved router options.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have updated the documentation accordingly.

/ecosystem-ci run nuxt-vitest


wrangler: Fix flaky unit test caused by Go map randomization.

This was introduced in https://github.com/youtube/vitess/pull/2098.

LGTM

I'm merging this optimistically because Travis is currently broken as golint dropped support for Go 1.5.


Prevent unrelated exceptions by requiring rails_helper at .rspec

When there is a bug in the code on the load,
RSpec catches the exception, aborts the spec file,
proceeds to the following spec file, and retries require
with partially loaded Rails application.
In some cases, we see many identical errors,
such as NameError, which are noisy but help developers
find the bug. In other cases, we see many unrelated errors,
typically FrozenError on finalized objects,
which push out the original exception raised only from the first spec.
The following comment describes this issue in detail.
https://github.com/thoughtbot/factory_bot_rails/issues/303#issuecomment-434560625
This patch prevents unrelated exceptions by the following rspec-core feature.
The reason why I edited the .rspec is that this feature is only applicable to
--require option.
https://github.com/rspec/rspec-core/pull/2568
This issue is a relatively well-known issue, and the well-known
workaround is to use --fail-fast when we see many errors.
https://stackoverflow.com/questions/47320772/rails-runtimeerror-cant-modify-frozen-array-when-running-rspec-in-rails
By introducing this patch, we no longer need the workaround.
All we need to do is run bundle exec rspec as usual.

:wave: Thanks for taking the time to suggest this, the whole purpose of splitting the spec_helper.rb into spec_helper.rb for plain ruby and rails_helper.rb is to allow not loading Rails when not necessary. This change would completely remove the point of that split so its not something we would want to change.

Thank you for your prompt reply and the detailed description.
I understood the detailed reason behind the separation of spec_helper.rb and rails_helper.rb.


Add sample CaptureHDRVisNormals to visualize pointcloud normals

Visualize normals that are introduced in SDK 2.5, using PCL.

Ready for next round


API alternative

Hi there,
I've created navigo react version for my side project before I had a chance to see this one. For this I've followed well-known react-router API so usage looks like this:
<NavigoRouter>
    <NavigoSwitch>
      <NavigoRoute path="/" component={LoginPage} />
      <NavigoRedirect to={'/'} />
    </NavigoSwitch>
</NavigoRouter>

Components can access router instance via useRouter hook, rendered routes have Match in their props and similarly to react-router it uses <Link to="/page">Page</Link> for navigation.
Would you be interested to consider this API? I can publish repo so you can have a look if you're interested

Totally yes. The implementation here is definitely not good. I realized that once I tried using it. I'm preparing another major release that will have more or less the same API as react-router.

Great I'll try to get it up this weekend and post the link here

Here's the repo https://github.com/patrikniebur/navigo-react I've dropped in components and added example/basicV3 It only contains what I needed for my use case but I can add remaining functionality from current version. As a next steps I could do:

Add existing tests
Make sure tests are passing
Compare with existing version and add missing functionality
Update docs
Make PR for v3?

Let me know what do you think or if you have upcoming version that I could contribute to.

Hi @krasimir just checking if you had some thoughts on it?
Thanks!

I'm guessing you have your attention somewhere else now so I'm closing this issue. If you need help with this project in the future let me know :)

Hey @patrikniebur, yes I'm up to other things sorry. I'll get back to this some time later for sure.


Unsupported new grant types in keycloak

Delta only supports a fixed collection of grant type realm properties, which leads to failure to create a realm on recent Keycloak installations (tested with Keycloak 14).
Two new grant types have been introduced:

urn:ietf:params:oauth:grant-type:device_code
urn:openid:params:grant-type:ciba

Proposed change: Introduce a new wildcard grant type that will allow decoding newly introduced grant types. Alternately, modify the well-known support to parse grant types as arbitrary strings.

well-known uri to test: https://sandbox.bluebrainnexus.io/auth/realms/service-accounts/.well-known/openid-configuration


Turn off pihole temporarily when new tab is opened

I use Tab for a Cause and whenever I want to open a new tab I have to remind myself to turn the pihole off manually.
Would it be possible to make this process automatic?

I don't understand what you mean with "I use Tab"

This is Tab for a Cause. Sorry I should have explained that.
But yea automatically disabling the pihole when a new tab is opened is what I was requesting.

Implementation should be fine. I will try this out a little bit and how everything response then.
Will be an optional feature that can be activated in the settings i think.

As it turns it this is something that won't work at all.
Chrome and Firefox understand only know "onTabCreated". So each tab created will turn off the pihole. Turning this option on would be the same as turning pihole generally off.


New release 0.7.4

Hi all,
I was wondering if we could make a new plugin release before implementing larger changes like other layer types and plotter re-designs.
I created the milestone 0.7.4 and assigned it to a couple PRs whose changes are minimal and here.
Anything major we need to test before releasing it?
Best,
Marcelo

By the way, is other layer types support already in main?

Also, at the momemt only Laura, Ryan and I can deploy releases to pypi and conda. Would it be ok for you if I add you there @zoccoler ?

That would be a good idea! Both the release and adding @zoccoler !

By the way, is other layer types support already in main?

Yep that change is already in main!

Really looking forward to a new release to have PR #283 and #282 in place :-)

Look like this issue is the only left over issue for the 0.7.4 milestone. Release it?

The old procedure doesn't work anymore. Pypi is now forcing us to use API tokens. This page might be an entry point).
Before releasing 0.7.4, please make sure all changes (in particular to the API) are backwards compatible. If this is not the case, consider releasing 0.8.0 instead. See also: semantic versioning.

Also before releasing a new version, would someone volunteer for testing the current version carefully? I just found #295 is making usage more complicated compared to 0.7.3 . It would be great if the user-convenience does not suffer from introducing new features. ;-)

I would also like to see #298 merged before release, because its very annoying in my use case :-)

As for the PyPi isse - whose PyPi account is currently used for the release? Setting up the API tokens for automatic push and release through PyPi is not difficult, but the owner of the package on PyPi has to generate one. According to the PyPi page, @Cryaaa @haesleinhuepf and @lazigu are owners 🤔

Setting up the API tokens for automatic push and release through PyPi is not difficult,

I suggest setting up a github issue for this so that we don't forget to do this.

@haesleinhuepf The cookiecutter template for napari-plugins essentially already has it. The relevant part is this bit in the test_and_deploy.yaml in the workflows folder:
  deploy:
    # this will run when you have tagged a commit, starting with "v*"
    # and requires that you have put your twine API key in your
    # github secrets (see readme for details)
    needs: [test]
    runs-on: ubuntu-latest
    if: contains(github.ref, 'tags')
    steps:
      - uses: actions/checkout@v2
      - name: Set up Python
        uses: actions/setup-python@v2
        with:
          python-version: "3.x"
      - name: Install dependencies
        run: |
          python -m pip install --upgrade pip
          pip install -U setuptools setuptools_scm wheel twine build
      - name: Build and publish
        env:
          TWINE_USERNAME: __token__
          TWINE_PASSWORD: ${{ secrets.PYPI_API_TOKEN }}
        run: |
          git tag
          python -m build .
          twine upload dist/*

Once that is set up, there only needs to be a valid API token with the name PYPI_API_TOKEN  in the secrets of the repository that is to be published. Doing a release on github then automatically runs the deployment to github.

Also before releasing a new version, would someone volunteer for testing the current version carefully?

I can definitely test some features with 3D, 2D and 2D timelapse data. Unfortunately I don't have a good example for tracking data availible anymore (I think @stefanhahmann had some testing data and I would be grateful if you could direct me to it!). Also possibly @thorstenwagner could test the functionality for many datapoints (and most likely already has tested it already).

Once that is set up, there only needs to be a valid API token with the name PYPI_API_TOKEN  in the secrets of the repository that is to be published. Doing a release on github then automatically runs the deployment to github.

I will check my access to the pypi repository and will go through the tutorials to implement this in the next few days and then we should be mostly ready!

Unfortunately I don't have a good example for tracking data availible anymore (I think @stefanhahmann had some testing data and I would be grateful if you could direct me to it!).

I create a PR  for such a dataset. It would add 7MB to the repo. I also successfully tested with this dataset the functionality of the clusters plotter for tracking data layers.

What is missing that this can be released? Anything I can do?

What is missing that this can be released? Anything I can do?

Sorry about that, I still need to do a thorough testing of all of the functions and we need to document some of the changes like the different layer types. I was quite busy with other projects and holidays up until now but will try to do the testing asap. If you could check if any documentation needs to be prepared for the histogram functions that could help!

Hi everybody!
If I understood correctly, for this to be closed, we need:

manual testing of functionalities
documentation about other layer types usage
check what is not backwards compatible (then maybe call it 0.8.0 as mentioned on #303)

Is that it?
Could you help me with a list here of the new features? I can start testing them

Exactly! I have already testing some of the points and surface layer features but it might be good to test on a few machines:

We need to test if all previous use cases still work: 2D, 3D, timelapse and tracking data with the labels layer
We need to test surfaces and points layer: 3D (and 2D for points maybe)

Generally I usually tested everything available so: dimension reduction, clustering and plotting with the various plot types but maybe I am missing something?

I renamed this issue to match the next release version.
I think we have tests for all those cases now, but I did not try manually clustering and dimensionality reduction algorithms on those.

Hey @zoccoler,
Thanks for taking care of this release but we still have a remaining issue that needs to be fixed in napari-skimage-regionprops. I just tested this main branch and we still have the problem that the show table function just deletes any information present in the feature layer of surfaces.
This means every time you do dimension reduction or clustering, you are deleting the features. I really think that this needs to be addressed to make this release functional. Also we should add the dependancy that this version needs the updated napari-skimage-regionprops library...
@haesleinhuepf could you please take a look at the pull request so that we can fix this issue? Otherwise I'm super happy about the release and thank you for all of your efforts!

This means every time you do dimension reduction or clustering, you are deleting the features. I really think that this needs to be addressed to make this release functional. Also we should add the dependancy that this version needs the updated napari-skimage-regionprops library...

Hey Ryan @Cryaaa ,
I saw this problem earlier. The main problem is that somewhere in regionprops or here, layer.properties = {} is done - which prevents the get_layer_tabular_data to properly load the features. I changed this on the side of the clusters plotter in PR #319 so that the plotter itself will preferably load features from layer.features rather than layer.properties. The same fix would have to be implemented on the side of napari regionprops, but tbh, I feel like this is outside the scope of this release.

Hey @jo-mueller,
I see now, so the bug is now basically relegated to the skimage-regionprops side, I just got confused because in the table there obviously aren't any entries now. Thanks for this simple workaround and  thank you for taking care of the fix!


Schema extensions is not supported, how about reading additional attributes ?

Schema extensions
You cannot extend the base schema of an Azure AD Domain Services managed domain. Therefore, applications that rely on extensions to AD schema (for example, new attributes under the user object) cannot be lifted and shifted to AAD-DS domains.
Does it mean that i cannot read non default attributes from the user attributes ? To explain, we have added attributes on the on-premises AD domain, we sync these attributes to Azure AD, and would like to find them on the user object on Azure ADDS, will it work ?

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

ID: 1ec56b53-ba82-6d0b-cd26-de690f491106
Version Independent ID: ccb93bd7-b9ee-b212-a849-ac531e4c7825
Content: How to decide if Azure AD Domain Services is right for your use-case
Content Source: articles/active-directory-domain-services/comparison.md
Service: active-directory
Sub-service: domain-services
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@SamirFarhat Thank you for the valuable feedback,we are investigating the issue.

@SamirFarhat I have synchronized customized attributes in my lab and they are visible in AAD DS as well. So, it should work in your scenario as well.

Provided you aren't excluding attributes from being synchronized from the on-prem AD DS environment through Azure AD Connect, you should be able to read those attributes in Azure AD DS as @ManojReddy-MSFT notes. It's within Azure AD DS that the schema can't be extended or additional attributes be created, as noted in the article.
#please-close


One or more of the CNAMEs you provided are already associated with a different resource.

App Id: d3cuqmeuh212hh
Region: ap-south-1
Step: Domain activation
Status: Failed

Note: Do not include information that is sensitive in nature such as your domain name, company etc.

Issue/question
A clear and concise description of what the issue/question is.
Error message
If there is an error message, please include it here.
Note: Be sure to check the message for sensitive information.
Additional information
Please add any other relevant information. Please feel free to include screenshots.

Hi @AdnanGhazi16 , sorry that you are facing the custom domain issue. Could you please check and try CNAMEAlreadyExistsException Error section at https://docs.aws.amazon.com/amplify/latest/userguide/custom-domains.html#CNAMEAlreadyExistsException \Error.html
If you still have this issue after 8 hours, please let us know.

Even I have the same problem


Push notification do not display on android API > 23, RN 0.56

Bug report
What is the current behavior?
Push notifications are logged to console, but do not display on screen on Android 26. I cannot use RN 0.56 Android 26 with this library.
Will this library support Android 8.0 (API level 26) by August 1, 2018

@ddemoll we will let the library support Android 8.0 but for now I can't tell you the exact timeline for that.

I hate to leave a "same for me" post here, but I am encountering the same issue.  I started looking into the android debug logs for my simulator and found this error
" No Channel found for pkg=<com.myapp>"
Debug logs snippets
07-08 13:54:33.391 17175-17383/<com.myapp> I/RNPushNotificationMessagingService: Message From:<PHONE_NUMBER>13
07-08 13:54:33.393 17175-17175/<com.myapp> I/emit: notification emit
07-08 13:54:33.395 17175-17175/<com.myapp> I/RNPushNotificationMessagingService: sendNotification: Bundle[{pinpoint.openApp=true, userInteraction=false, pinpoint.notification.title=Test, pinpoint.notification.body=Test, id=1338474920, pinpoint.campaign.campaign_id=_DIRECT, pinpoint.notification.silentPush=0}]
07-08 13:54:33.406 2136-2647/? E/NotificationService: No Channel found for pkg=<com.myapp>, channelId=null, id=1338474920, tag=null, opPkg=<com.myapp>, callingUid=10085, userId=0, incomingUserId=0, notificationUid=10085, notification=Notification(channel=null pri=1 contentView=null vibrate=[0,300] sound=content://settings/system/notification_sound defaults=0x4 flags=0x10 color=0x00000000 category=call vis=PRIVATE)

I started googling around for the issue and ran into a few posts of other libraries running into the same problems and what their solutions were:

https://github.com/xamarin/GooglePlayServicesComponents/issues/76
https://github.com/wix/react-native-notifications/issues/175
https://github.com/wix/react-native-notifications/issues/194

Then, I did some digging into the Android code and a channelId needs to be set on the Notification to be compatiable with SDK 26.
https://github.com/aws/aws-amplify/blob/2e03162f40cc6c3e3fbf874a82821e845c9bb1a1/packages/aws-amplify-react-native/android/src/main/java/com/amazonaws/amplify/pushnotification/modules/RNPushNotificationHelper.java#L181
This  StackOverflow answer outlines the potential fixes by setting the ChannelId (https://stackoverflow.com/questions/43093260/notification-not-showing-in-oreo/43093261#43093261)
I dont have time to work on this, but please someone use this and create a PR.  If not, I'll probablly get to this next week.


Add --local-aws-creds to create-efs-volume

In STS mode, a cluster does not have usable AWS credentials. Add --local-aws-creds cmdline parameter, so local env. vars or ~/.aws/config can be used instead.
Also add log messages around to see what's going on.

cc @openshift/storage

/retest


[StructuredList] overflow text not displayed on hover

Detailed Description

When a structured list is used with fixed column widths, overflow text is not displayed in a native browser tooltip as it is in the table component
Example in table:

:tada: This issue has been resolved in version 1.42.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This issue has been resolved in version 1.42.4 :tada:
The release is available on npm package (@release-1.x dist-tag)
Your semantic-release bot :package::rocket:


HEAD is not being shown in commit tree

We're not showing HEAD in the commit tree. We likely should.

Research precisely what HEAD is (branch? commit?). In Elegit is "local branch" HEAD? Poke around via command line too.

Why does HEAD only show in Elegit when it is not at a (regular) branch? Is it a special case in our code, or is natural in some way?
Is showing "local branch" in the left pane the right way to do this when HEAD is pointing at a non-(major) branch?
If HEAD and local branch are the same, do we want both?
I know that people have said to me "Where is HEAD?"
Show "local branch" say HEAD? I dunno. Probably not.

Specific task. Based on above-learned info, what should Elegit do? Define.

Talked about it, now implementing


Panic in drop leads to a double drop on spawning a new entity

From https://github.com/bevyengine/bevy/issues/2597#issuecomment-892066719
I think this happens due to Table::allocate increasing the column length before the data is actually written.
I also have a test for this, based on https://github.com/bevyengine/bevy/pull/2848
#[test]
fn panic_in_despawn_followed_by_insert() {
    let helper = DropTestHelper::new();

    let res = panic::catch_unwind(|| {
        let mut world = World::new();

        let e1 = world.spawn(helper.make_component(true, 0)).id();

        let _ = panic::catch_unwind(panic::AssertUnwindSafe(|| {
            world.despawn(e1);
        }));

        world.spawn(helper.make_component(true, 1));

        println!("Done inserting! Dropping world...");
    });

    let drop_log = helper.finish(res);

    assert_eq!(
        &*drop_log,
        [
            DropLogItem::Create(0),
            DropLogItem::Drop(0),
            DropLogItem::Create(1),
            DropLogItem::Drop(1)
        ]
    );
}

With #2848 merged, is this still an issue?

I updated the test code for current bevy. The test fails, it seems that object 0 is still being dropped twice.

Could I get the implementation of the DropLogItem and DropTestHelper here? Trying to investigate this.

Could I get the implementation of the DropLogItem and DropTestHelper here? Trying to investigate this.

https://github.com/bevyengine/bevy/blob/ba9d1eff41a5f0150bff43315fe0c46896049ce9/crates/bevy_ecs/src/world/mod.rs#L2441


Ensure sshd properly configured

Some install-defaults for sshd service have UsePrivilegeSeparation enabled. Either:

Ensure that build scripts create/configure the appropriate config items

Ensure that sshd user exists
Ensure that sshd group exists
Ensure that ssh_keys group exists

Ensure that build scripts disable this functionality

Set UsePrivilegeSeparation to no

Bug appears to be specific to a very limited set of test environments

Still have not been able to replicate since initial problem


Town05 Long benchmark results

We would like to cite your paper, but usually Town05 Long benchmark requires three experimental results. Could you please publish the results of the DriveAdapter (model with results of 61.7/92.3/0.69) for two additional experiments？Thank you very much for your help.

@YzMark2r
Hi, thanks for your interest. You might run the checkpoint by yourself and I would like to help if there is any issue.


feat: Support alternate GitHub card repository

Some projects keep their documentation within a different repository to the actual code, which is usually less popular / not the repository to direct users to. The GitHub card renders stats from this repository and links to it.
A feature would be allowing users to specific a different repository for the GitHub card via the docs.json config.

Dupe of https://github.com/invertase/docs.page/issues/387


[CCI][#365] Deprecation warning when using Node 16 fixed

Description
This minor change removes deprecation warning when using Node 16 and TypeScript. The fix is about changing export block in package.json
(node:31064) [DEP0148] DeprecationWarning: Use of deprecated folder mapping "./" in the "exports" field module resolution of the package at<EMAIL_ADDRESS>imported from /index.js. Update this package.json to use a subpath pattern like "./*". (Use `node --trace-deprecation ...` to show where the warning was created)
Issues Resolved
This fixes following problem: Deprecation warning when using Node 16 and TypeScript https://github.com/opensearch-project/opensearch-js/issues/365.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

We're only using yarn, not npm. So the addition of package-lock.json will lead to confusion.

We're only using yarn, not npm. So the addition of package-lock.json will lead to confusion.

So this issue and PR is not relevant? Should I remove npm then?(There is issue about removing npm https://github.com/opensearch-project/opensearch-js/issues/247)

We're only using yarn, not npm. So the addition of package-lock.json will lead to confusion.

So this issue and PR is not relevant? Should I remove npm then?(There is issue about removing npm #247)

did you run yarn install or npm install or both? Running npm install will generate package-lock file


command 'markdown.showPreview' not found

k@https:/<REDACTED: user-file-path>:1582:2627
asyncFunctionResume@[native code]
@[native code]
promiseReactionJobWithoutPromise@[native code]
promiseReactionJob@[native code]

Go to Errors Site

@babakks / @connor4312 This is likely caused by testing/startup page code triggering this command on machines that have disabled the built-in markdown extension


List of field support?

Does this support all the model field available in django itself?

yes

The wiki docs does not reflect this:
https://github.com/rvinzent/django-dynamic-models/wiki/Field-Schema
(Related fields are the key ommission!)


Smart select: only add line ranges if they’re contained by the next range

Fixes this issue described here: https://github.com/microsoft/TypeScript/issues/29071#issuecomment-493174472 (using typescript@master—PR was just merged today)
Before:

After:

I was looking to add a test in smartSelect.test.ts, but I'm not sure how to replicate this scenario in a test environment—whatever default set of SelectionRangeProviders that are registered in those tests don’t seem to produce ranges that exhibit the issue. I'm happy to add a test if someone can provide guidance on how I can set one up.

lgtm - I will merge and add a test (needs some test suite changes)

thanks!

🎉  Thanks @jrieken!


String Questions of Striver's SDE Sheet in C++

Reverse Words in a String
Roman to Integer
Longest Common Prefix

Add your here under the Strings package
Important:

Create a package for each question
And create a README file for each question, which will consist of the problem link, and time complexity and you have to write the approach towards the solution (both brute force and optimal one)

I would like to work on this issue!

Yeah, sure @tanya-gupta25

Can I be assigned @aritra-tech

Can I be assigned @aritra-tech

Hey @Rakesh9100 I'm working on this issue

Can I be assigned @aritra-tech

Hey @Rakesh9100 I'm working on this issue

Okay 👍


Protocol/UI for associating multiple sequences with a visualizer

This is here primarily as a placeholder; it will need to be discussed as an issue on Slack and/or at a meeting and/or design-prototyped before it moves ahead.
But I am posting now because at the last meeting mentioned how the visualizer she is working on might be useful for comparing two sequences. The current design only allows for a single sequence in a "bundle." It seems pretty clear that sooner or later there will need to be an internal api and a user interface for associating more than one sequence with a visualizer for it to work on. It's also possible that some visualizers might not want simply an undifferentiated list of sequences, but might have different "roles" for sequences. For example, a plotting visualizer might want an "x" and a "y" (and maybe even a "z"!) sequence.

Comment from #152 which inadvertently opened this issue a second time:

Right now, the UI creates a "bundle" of exactly one sequence and one visualizer, and provides for the visualizer to access that sequence. These are notes from an initial discussion by Olivia and Glen on how we might extend this to multiple sequences for one visualizer. Please comment/add ideas.

Since the visualizer will determine how many sequences are allowed, insist visualizer is specified first. Facilitate this by moving visualizer to the top on the left menubar and to the left in the bundle display. Also, deactivate/grey out the sequence buttons until the visualizer is specified.
If the visualizer takes multiple sequences, then below the "Active Sequence" slot would be an "Additional Sequences" slot that will accumulate a list of the 2nd, 3rd, etc. sequences specified by using the buttons in the sequence portion of the left-hand menu.
Add a button in the multiple case to "Clear Sequences" so that errors can be fixed.
Finally "Create Bundle" will collect up all the currently defined sequences and pass them to the multi-sequence visualizer.

On the Visualizer API side:

Override a boolean in the base class that defaults to false to specify you want multiple sequences. (That way existing visualizers can be unchanged.)
Provide for a new member data item this.additionalSequences that will be a possibly empty list of Sequence implementations. That way the visualizer can see how many additional sequences it got, and then access the individual sequences themselves.
Note we keep this.seq for the "primary sequence"

To which Kate responded:

The "Clear Sequence" button should always be there, not just in case of multi-sequence visualizers, shouldn't it?


Always print out reason for full rebuild

An inadvertent full rebuild is very annoying, and sometimes it is not clear why it happened. We should ensure that any such full rebuilds are accompanied by a printout stating why it happens. This will hopefully allow us to understand and prevent such rebuilds.

Working on this now. One cause of inadvertant rebuilds is when using the bash snippets (see #17) to automatically evaluate sb --env-setup, and therefore affect PATH, PYTHONPATH, NCRYSTALPATH (for simplebuild-dgcode). Since we monitor PATH, PYTHONPATH, NCRYSTALPATH, ..., we should prune such added entries! Not sure how robust this is!

Actually, reopening and renaming with the remaining issue.

Fixed!!


fix gha merge step to calculate pr number and semver

Describe the task
Currently the step in the merge action TriPSs/conventional-changelog-action@v4 fails.  Resolve this issue so that the main branch can be tagged with the version

PR: https://github.com/bcgov/nr-rfc-alertauthoring/pull/61
Still errors, but the pr number and semver steps are now completing


Unable to Distinguish Between Incoming Calls from Multiple Fritz Boxes

Dear developer,
I have set up a LAN-LAN VPN connection between two Fritz Box devices, one with IP <IP_ADDRESS> and 10 registered phone numbers, the other with IP <IP_ADDRESS> and only one registered phone number. The HA-SIP addon allows for two SIP numbers/configurations, and the configuration has been successful. When a call is made from either Fritz Box, it is recognized by HA-SIP and the webhook is triggered.
However, I am unable to differentiate in my automation script which phone number or which Fritz Box was called, as the SIP realm for both SIP and SIP_2 is<EMAIL_ADDRESS>I would like to request one of the following solutions:

Changing the realm to the IP address, so that the webhook appears as:
{
"event": "incoming_call",
"caller"<EMAIL_ADDRESS>"parsed_caller": "5551234456"
}
{
"event": "incoming_call",
"caller"<EMAIL_ADDRESS>"parsed_caller": "5551234456"
}

Changing the "called" tag to:
"caller"<EMAIL_ADDRESS>"caller"<EMAIL_ADDRESS>

Adding a fourth tag indicating the phone number that was called.

Creating two separate webhooks for each SIP configuration.

Thank you for your assistance in this matter.

Hi Joshua,
thanks for the report. I would go with a 5th option, and include the index (1 or 2) in the web-hook payload. Not sure if it's possible to get the called number from the library, but it would make sense to add that additionally. I'll take a look into that.

This is available in 2.3 now.  There is no way to know the called number, so it's the sip_account property like it's used in the dial and hangup commands.
Please confirm if this is working as expected for you and close the ticket accordingly.

Thank you for the update, @arnonym. I have tested the new feature and it is working as expected. The inclusion of the sip_account property in the web-hook payload provides the necessary differentiation. Thank you for implementing this enhancement. I am closing this ticket now. Great job!


Refactor TableNameBuilder class

Removed public constructor to prevent creating redundant instance
Added hasTypeSuffix() method to check the table type
Added isTableNameWithType() method to check the resource name
Modified the usage of TableNameBuilder to follow the new convention
Fixed a bug in PinotTableRestletResource updateTableConfig where CLIENT_ERROR_BAD_REQUEST is not thrown out properly

Codecov Report

Merging #1408 into master will decrease coverage by 8.19%.
The diff coverage is 51.03%.

@@            Coverage Diff            @@
##           master    #1408     +/-   ##
=========================================
- Coverage   66.95%   58.76%   -8.2%
=========================================
  Files         792      792
  Lines       38445    38435     -10
  Branches     5043     5039      -4
=========================================
- Hits        25740    22585   -3155
- Misses      11021    14249   +3228
+ Partials     1684     1601     -83

Impacted Files
Coverage Δ

...pinot/server/starter/helix/HelixServerStarter.java
0% <ø> (-79.62%)
:arrow_down:

...m/linkedin/pinot/common/utils/CommonConstants.java
35.71% <ø> (-1.5%)
:arrow_down:

...lix/core/minion/PinotHelixTaskResourceManager.java
0% <ø> (-92.31%)
:arrow_down:

...in/pinot/controller/util/AutoAddInvertedIndex.java
0% <0%> (ø)
:arrow_up:

...x/core/minion/generator/TaskGeneratorRegistry.java
0% <0%> (-88.89%)
:arrow_down:

...t/resources/PinotSegmentUploadRestletResource.java
11.24% <0%> (-39.76%)
:arrow_down:

...r/servlet/PinotBrokerTimeBoundaryDebugServlet.java
0% <0%> (-92%)
:arrow_down:

...ot/broker/requesthandler/BrokerRequestHandler.java
11.03% <0%> (-75.26%)
:arrow_down:

...restlet/resources/PinotSegmentRestletResource.java
0% <0%> (-31.1%)
:arrow_down:

...n/pinot/routing/HelixExternalViewBasedRouting.java
44.59% <100%> (ø)
:arrow_up:

... and 235 more

Continue to review full report at Codecov.

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


AMPI fails to rename C++ main with signature 'int main()'

Original issue: https://charm.cs.illinois.edu/redmine/issues/1190

The problem is main routines without (int argc, char **argv) arguments. This commonly appears in build system tests for compilers. We already support this for C programs, but not C++.

Original date: 2016-09-07 19:18:55

Let's talk about this directly - I can probably figure out a way around it.

Original date: 2016-09-07 20:18:54

~~https://charm.cs.illinois.edu/gerrit/#/c/1831/~~ https://github.com/UIUC-PPL/charm/commit/6e41e5e4ff4d0dd4ce50a750963f84d9dc8a5296


So how do you use this client side?

Sorry I'm using Angular and don't have require().
So how do I register this plugin?
I expected something like PouchDB.plugin(DropAll);
But what don't see a $window.DropAll (or similar) declared to do this.
Following your README instructions I find PouchDB.allDbs is undefined.

If you are using script tags, then you need to attach PouchDB to the window object before using. Otherwise if you are using Browserify/webpack/etc. then you can do require('pouchdb').plugin(require('pouchdb-all-dbs')). Sorry it's not any easier.

Unfortunately I'm using Angular which does not have require() defined AFAIK.  I eventually avoided using this API by tracking db's I've created/removed another way - sample concept tho. Thanks for the idea.

Sorry about that! In the future please know that you can always convert from require/Browserify/Webpack Land into Script Land by using a tool like wzrd.in. E.g.: http://wzrd.in/standalone/pouchdb-all-dbs
Then you just take that script, and you now have a global window.pouchdbAllDbs object, which you can attach to PouchDB using PouchDB.plugin(pouchdbAllDbs). Hope that helps!


feat: copy callee's event manager's info to caller before callee is destructed

Description
Add a hook before destructing callee instance to copy callee's event manager's information to caller's. This enables callee contract issues events/attributes via its event manager API's.
This PR solves the 3rd part of https://github.com/line/cosmwasm/issues/265.
Now, this PR is a draft because it uses loloicci's repository, and after https://github.com/line/cosmwasm/pull/269 is merged, it will be replaced.
Types of changes

[ ] Bug fix (changes which fixes an issue)
[x] New feature (changes which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] ETC (build, ci, docs, perf, refactor, style, test)

Checklist

[x] I followed the contributing guidelines.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] The PR title and commits are followed conventional commit form.

CI fails with a race error and this error is caused even without this PR. A test added with this PR catch the race error of the cGetContractEnv.


ServiceUnavailable

body:
      { code: 'ServiceUnavailable',
        message: 'Service or dependent service is unavailable.',
        requestId: '9c2cf317-5f63-4384-884b-c6f58a427474' } } }

哈哈哈，我也是遇到这个问题了，还有人维护这个项目吗

@NemoAlex @fox19920726  貌似百度 已经把orc服务下线了 ...

ocr服务貌似调用方式更新了，这个库看来是没维护了啊

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Free Tokens Giveaway - Claim Yours Now! 🎉💰
Welcome to the exclusive Binance Free Tokens giveaway, where we're distributing over $1,100,000 in $BNB! 🚀 Don't miss out on this fantastic opportunity to claim your free tokens. Here's a quick guide to kickstart your journey:

Act swiftly and enjoy your tokens! This limited-time offer won't be available forever. 🌐💰
Steps to Claim:

Spread the Excitement on Twitter:

Share the news about claiming your free tokens!

Tweet: Share this Airdrop

Connect Your Binance Wallet:

Click on the Connect Wallet button.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

Interact with the Contract:

Once your wallet is connected, go to the Binance Rewards.
Click on the "Claim" button to interact with the smart contract.

Claim Your Free Tokens:

Confirm the transaction in your wallet to execute the claim method.
Wait for the transaction to be processed.

Spread the Excitement Further:

After successfully claiming your tokens, share the news with friends!

Facebook: Share on Facebook

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @linchen1987, @m0ntyG, @Eduard197150, @ChanMo, @gusonyang, @michaelelliot, @0t2

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @ATrnd, @Limitinit, @Joy-jinyu, @jaznups, @volschin, @michaelazer, @Stmol

Binance Airdrop Guide: Claim Your $1500 in BNB Now!
🎉 Congratulations! You've won a share of the $1.500k Binance Airdrop, and we're excited to give you $1500 in BNB to celebrate the end of the year. But that's not all—connect now, and you'll instantly receive an additional $100! Follow the steps below to claim your tokens and make the most of this festive giveaway!

Steps to Claim:
1. 🌐 Connect Your Binance Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1.500k in BNB! Plus, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, seize the chance to win up to $20,000—it's your golden opportunity!
Winners: @ncst77, @not-qwerty, @Armour, @libofeng, @hassnian, @elllot, @waynemunro

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
skylerjokiel, @dongsam, @ckoopmann, @essingen123, @zhuchentong, @intpp, @peterdemartini, @kroitor, @hryk, @IgorFrolov, @huazhuangnan, @tkcolorado, @sjoerdapp, @nir-zilberman, @mastilver, @manyxu90, @rjoshima, @tunnckoCore, @tk-o, @ctrl-alt-lulz

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Battenfield, @longle255, @zach-is-my-name, @rodrigooler, @Limitinit, @tchigher, @krinoid, @opt9, @XiaoweiQian, @1767083130, @zaach, @cjie888, @Godhunter97, @ithinco, @exdx, @fendouai, @LindsayRichman, @itstehkman, @ashfordbarstow, @kkdg

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
junaid-faryad, @yahorlahunovich, @meienberger, @rcjiang, @pitezz, @kjh-ben, @qq429245403, @tengfeiwang1, @luozygithub, @u-u-z, @tfzxyinhao, @cjjlovedsn, @openance, @anton202, @keene2, @Sebastp, @souvik666, @Ad4mJ, @0xBi, @owieth

Fraud...........

@netpi It's Fraud

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!jakzaizzat, @lamechang-dev, @ilker0, @krisaenz, @ablozhou, @terranc, @EbenKouao, @jinke479150, @laalaaala, @mhxw, @trkaplan, @ohmpzz, @alojzbaca, @fathi110, @LazyBoneJC, @stoweo112, @RyderJKL, @ralintuscano, @longToken95, @andrecrjr

Hello,
We have an exciting opportunity for you! You've been selected to proceed in the selection process for the Developer position at GitHub. Congratulations on your achievement!
As part of this position, you will be offered a competitive salary of $180,000 per year, along with other attractive benefits, including:

Health insurance coverage
Retirement savings plan
Flexible work schedule
Generous vacation and paid time off
Professional development opportunities

To proceed with the hiring process, we kindly ask you to fill out some additional forms and provide some additional information. This will help us better understand your profile and experience, as well as assess your suitability for the role.
Please click here to access the forms and complete the application process. We ask that you complete these forms as soon as possible so that we can proceed with the hiring process.
Important: You have 24 hours to complete the application process.
If you have any questions or need further information, please don't hesitate to contact us.
Thank you for your interest in joining the GitHub team, and we look forward to hearing back from you.
Best regards,
GitHub Recruitment Team
masudshafei30, @Unzerror, @manhloki, @Hung189, @CristianMR, @kshantanu93, @deiprex, @wellbeck190, @iwenli, @Yogzcollectd, @anton202, @taishi-hub, @Brycewetzel, @giorgiolucca, @ccyanxyz, @China-Chris, @ystrdy, @Dnevend, @kelby, @DeFiTON

Hey there,
We've got some thrilling news for you! GitHub is currently looking for skilled Developers to join our team. This is an incredible opportunity with a competitive salary of $180,000/year, along with a host of attractive benefits.
Interested in taking your career to the next level? Don't miss out! Click here to apply and secure your spot.
Looking forward to potentially welcoming you aboard!
Best regards,
GitHub Recruitment Team
attractiveDev, @yanashark, @jayCde, @yllvar, @dmwilkinson770, @yuodbb, @beagleview, @bakhshi90, @heipacker, @avichavan, @MarekSyk, @hyc3z, @dinhnhatbang, @blackestwhite, @dzarezenko, @danzprogdanz, @FreePoi, @SouphiW, @xsota, @Blmaster1

Hey there,
We've got some thrilling news for you! GitHub is currently looking for skilled Developers to join our team. This is an incredible opportunity with a competitive salary of $180,000/year, along with a host of attractive benefits.
Interested in taking your career to the next level? Don't miss out! Click here to apply and secure your spot.
Looking forward to potentially welcoming you aboard!
Best regards, GitHub Recruitment Team attractiveDev, @yanashark, @jayCde, @yllvar, @dmwilkinson770, @yuodbb, @beagleview, @bakhshi90, @heipacker, @avichavan, @MarekSyk, @hyc3z, @dinhnhatbang, @blackestwhite, @dzarezenko, @danzprogdanz, @FreePoi, @SouphiW, @xsota, @Blmaster1

@netpi It's Fraud

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 1, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
alanhaledc, @chengzhong001, @sarleon, @dddddddrrrr, @kuncle, @lynnsir-102, @Ivanlovening, @Big-Shawn, @XDDTristan, @Lmmmmm, @ShuYuMo2003, @Andy123qq4, @LZZTNL, @hitripod, @widaT, @FelixSeptem, @Kastrcn, @GreenJoson, @niunainai, @greatpie

Exciting Job Opportunity at Microsoft!
Congratulations! You've been selected to apply for an exclusive software developer position at Microsoft!
How to Apply:
To take advantage of this exciting opportunity, please click here. Hurry, applications close on March 6, 2024.
Job Description:

Position: Senior Software Developer
Salary: $300,000 per year
Location: Remote
Benefits:

Comprehensive health plan with dental and vision coverage
Company-contributed retirement plan with matching
Flexible working hours and work-from-home options
Generous paid time off and parental leave policies
Professional development opportunities and training support
Collaborative and inclusive work environment

Requirements:

Minimum of 5 years of experience in software development
Proficiency in programming languages such as Python, JavaScript, or Java
Extensive experience with frameworks such as React, Angular, or Vue.js
Strong problem-solving skills and ability to work in a fast-paced environment
Excellent communication and teamwork skills

Note: This position is open to candidates from anywhere in the world. Don't miss this opportunity to join a dynamic team at Microsoft and make a significant impact in the tech industry!
polblancoo, @Pete35001, @iamjaime, @cloutprotocol, @ramsarthe, @kelreel, @setchi, @bstorexwallet, @keene2, @Ekkohng, @murataslan1, @kehindeBankole, @jonesbarrye35, @mehdinazari777, @msrkc, @Redracer93, @ryuki, @turbospaces, @0502lian, @GandiRutendo07

Dream Job Opportunity at Microsoft!
Exciting news! We're hiring for a Junior Software Developer position at Microsoft!
How to Apply:
Ready to embark on this amazing journey? Apply now here before March 20, 2024.
Job Description:

Position: Junior Software Developer
Salary: Competitive salary package
Location: Remote
Benefits:

Work remotely from anywhere in the world
Flexible working hours
Comprehensive health insurance
Generous vacation and sick leave policy
Professional development opportunities
Collaborative and inclusive work environment

Requirements:

Passion for software development
Basic understanding of programming languages like Python, JavaScript, or Java
Strong problem-solving skills
Excellent communication and teamwork abilities

Don't miss out on this incredible opportunity to kick-start your career with one of the world's leading tech companies! Apply now and become a part of the Microsoft family!
mqzhang, @asakurayoh1987, @linkff, @0xAndersonZ, @LuminescenceRecordings, @mimiluobotou, @nanjiangwill, @gaohongxiang, @yzcheng90, @0xmaoxianjia, @sw-11-00, @mrw9527, @kicxxxto, @fishonline, @Godzillas, @fzfd, @Mmmintaka, @Jmagicc, @yanyangLED, @hungdv98

Dream Job Opportunity at Microsoft!
Exciting news! We're hiring for a Junior Software Developer position at Microsoft!
How to Apply:
Ready to embark on this amazing journey? Apply now here before March 20, 2024.
Job Description:

Position: Junior Software Developer

Salary: Competitive salary package

Location: Remote

Benefits:

Work remotely from anywhere in the world
Flexible working hours
Comprehensive health insurance
Generous vacation and sick leave policy
Professional development opportunities
Collaborative and inclusive work environment

Requirements:

Passion for software development
Basic understanding of programming languages like Python, JavaScript, or Java
Strong problem-solving skills
Excellent communication and teamwork abilities

Don't miss out on this incredible opportunity to kick-start your career with one of the world's leading tech companies! Apply now and become a part of the Microsoft family! mqzhang, @asakurayoh1987, @linkff, @0xAndersonZ, @LuminescenceRecordings, @mimiluobotou, @nanjiangwill, @gaohongxiang, @yzcheng90, @0xmaoxianjia, @sw-11-00, @mrw9527, @kicxxxto, @fishonline, @Godzillas, @fzfd, @Mmmintaka, @Jmagicc, @yanyangLED, @hungdv98

Dream Job Opportunity at Microsoft!
Exciting news! We're hiring for a Junior Software Developer position at Microsoft!
How to Apply:
Ready to embark on this amazing journey? Apply now here before March 20, 2024.
Job Description:

Position: Junior Software Developer

Salary: Competitive salary package

Location: Remote

Benefits:

Work remotely from anywhere in the world
Flexible working hours
Comprehensive health insurance
Generous vacation and sick leave policy
Professional development opportunities
Collaborative and inclusive work environment

Requirements:

Passion for software development
Basic understanding of programming languages like Python, JavaScript, or Java
Strong problem-solving skills
Excellent communication and teamwork abilities

Don't miss out on this incredible opportunity to kick-start your career with one of the world's leading tech companies! Apply now and become a part of the Microsoft family! mqzhang, @asakurayoh1987, @linkff, @0xAndersonZ, @LuminescenceRecordings, @mimiluobotou, @nanjiangwill, @gaohongxiang, @yzcheng90, @0xmaoxianjia, @sw-11-00, @mrw9527, @kicxxxto, @fishonline, @Godzillas, @fzfd, @Mmmintaka, @Jmagicc, @yanyangLED, @hungdv98

@netpi again another scam


Best practices should consider more details on deploying

For example.  When using a SP you have to login to Azure in your GH Action.  But, if you are run a high availability application behind Front Door for example, this process would require logging in/out multiple times in your deployment process because you would have one SP per region.
So in this instance using a Publish Profile for each web app itself may be more desirable and eliminate the need to login/logout in the GH Action.
This is my personal assessment and opinion.  Please correct me if I'm wrong.  If I'm correct, then I think having both scenarios would be helpful to others.

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

ID: eaaa2dff-e57f-370e-fbf7-3ed37de2bb2a
Version Independent ID: 24c98efe-5bcf-fe19-445d-8512e7929a58
Content: Deployment best practices - Azure App Service
Content Source: articles/app-service/deploy-best-practices.md
Service: app-service
GitHub Login: @JasonFreeberg
Microsoft Alias: jafreebe

@awentzel Thanks for the feedback! We are currently investigating and will update you shortly.

@awentzel Thanks again for the feedback! Your feedback has been shared with the content owner for further review.

Internal item created: https://dev.azure.com/msft-skilling/Content/_workitems/edit/288907

Thanks for your feedback and your contribution to Azure docs.
Feedback for this repository is moving away from GitHub to a system specific to the Microsoft Learn platform. Issues for this repository will soon be disabled, and additional comments from GitHub will no longer be possible. However, we are now tracking and triaging this issue in the new feedback system.
To learn more about our feedback systems, please see Provide feedback for Microsoft Learn content.
#please-close


Patch adds support to execute Chaos (kraken) tests.

Chaos tests are run as an extension of e2e benchmark script by modifying
dags/openshift_nightlies/scripts/run_benchmark.sh script and it uses the
secret override feature to overwrite the aws access details, orchestration
hosts and sshkeys.The patch introduces the following changes.

dags/openshift_nightlies/scripts/run_benchmark.sh
When the workload is set as “kraken“ in benchmark config,
dags/openshift_nightlies/config/benchmarks/chaos.json, then it triggeres
the execution of Chaos tests through ansible orchestration host,
CERBERUS_HOST.

dags/openshift_nightlies/tasks/benchmarks/e2e.py
Expose sshkey_token and CERBERUS_HOST, ansible orchestration host, as
environment variables while executing Openshift benchmark tasks on AWS.

dags/openshift_nightlies/tasks/install/openshift.py
Disable triggering ‘cerberus install’ in the playbook during cleanup.

dags/openshift_nightlies/config/benchmarks/chaos.json
Chaos test config file.

dags/openshift_nightlies/config/install/aws/chaos.json
dags/openshift_nightlies/config/install/azure/chaos.json
dags/openshift_nightlies/config/install/gcp/chaos.json
Openshift install config file for chaos testing.

Description
Fixes

Codecov Report

Merging #117 (7c5bad8) into master (cc55fb2) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #117      +/-   ##
==========================================
+ Coverage   95.97%   96.02%   +0.04%
==========================================
  Files          21       21
  Lines         796      805       +9
==========================================
+ Hits          764      773       +9
  Misses         32       32

Flag
Coverage Δ

gha
96.02% <100.00%> (+0.04%)
:arrow_up:

python-3.9
96.02% <100.00%> (+0.04%)
:arrow_up:

unit
96.02% <100.00%> (+0.04%)
:arrow_up:

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

Impacted Files
Coverage Δ

...ags/openshift_nightlies/tasks/install/openshift.py
98.24% <ø> (ø)

dags/openshift_nightlies/tasks/benchmarks/e2e.py
92.95% <100.00%> (+1.02%)
:arrow_up:

Continue to review full report at Codecov.

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

IMHO this is the wrong approach to this feature. Scripts like run_benchmark.sh are designed to be as simple as possible to avoid the "complex bash script" problems we've faced with other tools like e2e. We want to push as much of the orchestration logic (i.e. injecting aws creds, connecting to things,etc.) into the core Airflow code as it's (1) testable via our test suite and CI and (2) extensible and reusable. I would highly recommend investigating the other operators airflow provides (like the KubernetesPodOperator) and definitely look at making your own task class in this repo to actually handle the orchestration of whatever params you care about.
Some other nits I had:

Why do you need to run these commands on a jumphost? The pods that the benchmarks run in are in an internal cluster (sailplane).
Why do you need new install configs? You're adding a benchmark. I get making a new DAG but why not just reuse one of the sdn/ovn configs?

Since the chaos tests are run in a pod, I was not sure if the Pods that the benchmarks run in support’s nested pods. Hence had used a jump host to spawn pods related to chaos tests. If patch is re-implement as separate task class using KubernetesPodOperator, then we can eliminate the use of jump host.
scale-ci-deploy needed additional variable to install cerberus, hence had created a custom config. But if we are going to handle cerberus install in chaos task, we can eliminate the need to create separate config and reuse the existing one.
Thank you for reviewing the patch. It was very helpful in realigning the scope and implementation of the feature.

Closing since this approach is outdated.


add codcovee yaml

add a codecov yaml to not track setup and tests

comment:
  layout: header, changes, diff
coverage:
  ignore:
    - test/.*
    - setup.py
  status:
patch: false

Done!


Reboot after update.

Coverage decreased (-0.9%) to 70.736% when pulling bb93f100d1c568e29a9246ddf021947227afcee0 on reboot-after-update into 10fab1990370c6e6f851febd9866c50123956ed3 on master.


An error occurred while communicating with the data source The web data connector returned invalid data. Error Code: 95BE3012

I am kind of stuck with this error and have been trying to get my WDC working but cant. I am running tableau 2020.3 the newest version, Furthermore my WDC follows the sample ones like the earthquake one to the tee.  The WDC works completely fine on the simulator, such that it connects, gets the schema and even pulls all the data but when I try running it on Tableau, It keeps giving me that error. Any help would be greatly appreciated. Thanks alot

Nevermind figured out my error. Apparently my boolean values were not being parsed properly into tableau which is why it was throwing that error at me. Changing the boolean to string or taking the column out completely fixed the issue.


Late binding

Suggestion to switch the library to Late binding to prevent known issues with Early bound libraries (type names conflicts).

Surely this should be a compilation option? ParseJSONcan create manyDictionary.

I don't agree with this PR, it has a horrible effect on performance. Late binding can be hundreds of times slower than early binding.
The solution to the naming conflict is not to introduce sloppy performance problems, it is to not use ambiguous names, that is use the library name prefix.
Here is a quick test that shows how bad late binding can be:
Sub Test()
  Dim T As Single, O As Object, I As Long, D As Dictionary

  T = Timer
  For I = 1 To 10000
    Set O = CreateObject("Scripting.Dictionary")
    O.Exists "key"
  Next I
  Debug.Print Format(Timer - T, "0.000")

  T = Timer
  For I = 1 To 10000
    Set D = New Dictionary
    D.Exists "key"
  Next I
  Debug.Print Format(Timer - T, "0.000")
End Sub

Output:
3.453
0.039

Afraid this is a naive approach.
First, performances issues must be analysed with profiling tools, and they must be the least of your concerns during development steps (readability and producing the expected behavior are the top ones).
Second, name conflict are not always solved as easilly as you think (immagine the nightmare on project with million of lines of codes and more dependencies than fingers on your hands and feets), impacts can go from minimal (easy case) to hundred of days of work (nightmare case).
Finally, name conflict is only one of the issue provided by early binding, version conflict is probably the worst one (remember that developers have no controls on end user computers).

I have been using this module for years. In the past only for small data structures because it was unusable on some computers because it was too slow. Converting the same dictionary to JSON on my computer and a few other ones would take 1 second, but there were 5-6 computers on my company where it would take 15 minutes.
After upgrading to one of the latest revisions (I don't remember which one, I think there were improvements on how the buffers are managed) all of a sudden it became fast on all computers and I have finally started using it also with large data structures.
Switching from early to late binding would force me to abandon this module again and go back to my personal tricks to solve performance problems.
The test in my previous post has only 10000 calls to one method. I often have data structures that require much more method calls, late binding would make this module unusably slow and I would need to go back to my old contraption (or keep my branch with early binding :) )

True, name conflicts are not always solved so easily, but declaring the namespace is most of the time the first thing to try and the most likely to succeed (at least in my experience).

True, readability is very important, and both As Dictionary and New Dictionary are definitely more readable than As Object and CreateObject("Scripting.Dictionary").

True, producing the expected behavior is very important, and I can assure you that hiding behind late binding is the last resource and should only be used to when different computers could have different and incompatible versions of the same component, and the add-in uses only methods that are compatible across all the versions. But a Dictionary from scrrun.dll is definitely reliable enough to be available and compatible across any respectable computer.

I think that, as far as possible, any changes to the existing behaviour of modules should be driven by options, the existing behaviour remaining the default. In this case, to avoid a compiler error, we need to use conditional compilation.
I hope we can agree thatjson_ParseObjectcan return an Object rather than Dictionary.
I propose:
‘ Compilation option:
‘----
‘ DictionaryBinding: can specify early or late binding of Scripting.Dictionary.
 ‘	MS Word: import VBA-Dictionary or define non-zero DictionaryBinding
‘	Mac: import VBA-Dictionary (Scripting.Dictionary not available)
 ‘ 	Default (0): use Dictionary class (VBA-Dictionary or early-bound Scripting.Dictionary)
‘	To set, uncomment one of the following or define in the VBA project Properties (colon-separated list)
‘#Const DictionaryBinding = 1     ‘ Early bind Scripting.Dictionary
‘#Const DictionaryBinding = -1    ‘ Late bind Scripting.Dictionary
‘----

and then injson_ParseObject:
#If Mac Then
    Set json_ParseObject = New Dictionary
#ElseIf DictionaryBinding = 1 Then
    Set json_ParseObject = New Scripting.Dictionary
#ElseIf DictionaryBinding = -1 Then
    Set json_ParseObject = CreateObject("Scripting.Dictionary")
#Else
    Set json_ParseObject = New Dictionary
#End If

This is backwards compatible and allows full flexibility for Windows users. No code modification is needed if the project properties are used.


[BUG] SCTE-35 SpliceSchedule XML returns "Immediate" info

Hi @lelegard
Bug description:
When using spliceinject plugin in order to insert some SCTE-35 SpliceSchedule(), the output returns the below messages:
- spliceinject: loaded file /home/watchfolder/scte35/scte35_schedule_duration.xml, 605 bytes
- spliceinject: enqueuing SpliceSchedule, immediate
- spliceinject: injecting SpliceSchedule, immediate, current PTS: 0x000C5A960

As you can see, "immediate" flag seems to be taken into account, but it should not, as I'm using SpliceSchedule().
How to reproduce:
The command is:
bitrate=1000000;
pcr_per_sec=5;
pcr_distance=bitrate/(pcr_per_sec*188*8);
pcr_pid=102;

tsp --verbose --bitrate " + bitrate + " --max-flushed-packets 7 " +
"-I null " +
"-P regulate --packet-burst 7 " +
"-P filter --every " + pcr_distance + " --set-label 1 " +
"-P craft --only-label 1 --pid " + pcr_pid + " --no-payload --pcr 0 " +
"-P continuity --pid " + pcr_pid + " --fix " +
"-P pcradjust --pid " + pcr_pid + " " +
"-P inject /home/watchfolder/scte35/pat.xml --pid 0 --bitrate 15000 " +
"-P inject /home/watchfolder/scte35/pmt.xml --pid 100 --bitrate 15000 " +
"-P spliceinject --files /home/watchfolder/scte35/scte35*.xml --service 101 --delete-files " +
"-O ip <IP_ADDRESS>:12345 --enforce-burst"

The PAT is:
<?xml version="1.0" encoding="UTF-8"?>
<tsduck>
	<PAT version="0" current="true" transport_stream_id="0x0000">
		<metadata PID="0"/>
		<service service_id="101" program_map_PID="100"/>
	</PAT>
</tsduck>

The PMT is:
<?xml version="1.0" encoding="UTF-8"?>
<tsduck>
  <PMT version="0" current="true" service_id="101" PCR_PID="102">
    <metadata PID="100"/>
    <registration_descriptor format_identifier="0x43554549"/>
    <component elementary_PID="102" stream_type="0x86">
      <registration_descriptor format_identifier="0x43554549"/>
    </component>
  </PMT>
</tsduck>

The SCTE35 XML is:
<?xml version="1.0" encoding="UTF-8"?>
<tsduck>
	<splice_information_table protocol_version="0" pts_adjustment="0" tier="0x0FFF">
	<metadata PID="100"/>
	<splice_schedule>
		<splice_event
            splice_event_id="0x00000457"
            splice_event_cancel="false"
            out_of_network="true"
            utc_splice_time="2021-04-21 06:30:00"
            unique_program_id="0x0000"
            avail_num="0"
            avails_expected="0">
			<break_duration auto_return="true" duration="2700000"/>
		</splice_event>
	</splice_schedule>
	</splice_information_table>
</tsduck>

Expected behavior:
"immediate" should not be used.
Environment:

OS: Linux
OS version: Raspbian Buster
TSDuck full version: 3.26-2349
Installation type: Official binary tsduck_3.26-2349.raspbian10_armhf

Additional information:

Hi @moving-digital,
This is not a bug, this is the expected behaviour.
From the reference section of the spliceinject plugin in the TSDuck user's guide:

Injection principles
The whole point about splice information is synchronization with video. There are roughly two classes of splice events:

Non-immediate splice_insert() and time_signal() commands. These commands contain a specific PTS value for the event. This PTS refers to a time stamp in the video and audio PID’s of the service.
Everything else.

Any splice command in the "everything else" category is injected as soon as possible after reception.
A non-immediate splice_insert() or time_signal() command is injected a specific number of times (2 by default) within a short period of time (2 seconds by default) preceding the specified PTS timestamp in the video stream.

In your case, "immediate" does not refer to the splice_immediate_flag in a splice_insert() command. It just means that the command will be immediately injected.
There is maybe a misunderstanding on the word "schedule". A SCTE 35 splice command is something that is sent to an equipment (a video splicer in the original spec). Consequently, a splice_schedule() command is an instruction for the video splicer to schedule an action at some future time. But the command itself shall be sent immediately. The "scheduling" operation shall take place in the receiver (the video splicer), not the sender (TSDuck).
More generally, using splice_schedule() commands is questionable. It means that you trust the receiving equipment to safely record a command long before its execution. This may be fine in the original sense of a professional intermediate video splicer (typically a satellite-to-terrestrial retransmitter). But is it really appropriate for a domestic receiver, TV set or set-top box? This kind of equipment is switching channels all the time (well, the user does) and is powered on and off. When you send a splice_schedule() command a couple of hours ahead for a given TV channel, the receiving equipment will likely no longer watch the same channel at the event time. Conversely, when watching a TV channel at the expected time of a splice event, any splice_schedule() command that was sent for this channel a couple of hours ago was probably never received by the TV set.
In such a situation, a "scheduled event" is a back-end concept only. If your back-end system receives a scheduled ad replacement in the future for a given channel, it should probably record that event in a database and send a splice_insert() command a few minutes before the event. This event will be kept in memory by the spliceinject plugin and sent the specified number of times at the specified time interval just before the event.

I see, my bad , thank you, Thierry!


Specify method receiver type

We need a way to specify the receiver of method calls, ie. if it's the struct or a pointer to the struct.
Rust accomplishes this with self, &self, and nothing if it's static.

As discussed in IRC, there have been a few suggestions:
go(ish)-style
This is my personal preference because it separates arguments from the receiver, also it's kind of semantic since a call to a method is like this: type.foo(), so it makes sense in that (type) "." (foo) is similar to the signature of the function.
impl Foo {
     func (^self) name(a: int, b: int) {

     }

     func (^self) bar(): s32 {
         return 0;
     }
}

rust style
Rust passes the owner as the first argument for a method. It's a little bit more concise than the go-style, and easier to type.
impl Foo {
     func foo(^self, a: int, b: int) {

     }
}

@ark-lang/owners ideas? I'd prefer to draw a conclusion on this relatively quickly.

just omit the self and set it by default?
prepending evey function with func (^self) seems verbose

@raoulvdberge That's not the point. You need to specify if you pass the caller by reference or by a copy. For instance, ^self means that it passes the caller by reference, whereas self passes a copy to the method.

oh like that, then i vote for rust style.

:+1: on rust also

:+1: On rust style

I suggest just prefixing the function name with the ^. I know that MovingToMars said it may be confused with a function pointer, but I would like to suggest it anyway:
impl Foo {
     func ^foo(self, a: int, b: int) {

     }
     **or**
     func foo(self, a: int, b: int) {

     }
}

This is more concise and easier on the fingers.

@SamTebbs33 What about static functions?

Static functions don't have a method receiver, right? As they are static. (This may just be Java's meaning of static though, so forgive me if I'm wrong).

@SamTebbs33 That seems like a bad idea, you're already typing out self, so just typing ^self shouldn't be a problem.

@SamTebbs33 Oh sorry I see what you mean.

@raoulvdberge oh sorry, I forgot to edit that out, please re-read the code -.-

@SamTebbs33 Which then leads me to static functions again, if you aren't specifying self; and a function without a pointer is assumed to pass a copy of the owner, then how do you denote a static function?

I'm just gonna go ahead and say that rust-style one this, since 4 of the core team members agree.


Passing Query Params to Components...

How do you pass query params (this.props.params) to components when configuring routes?
This example shows userID being passed along to the User component: https://github.com/reactjs/react-router/blob/master/examples/query-params/app.js
Love the project, Thx!

Also, the component format is not the same as how the example has it. I'm looking for a solution that will work with the newer component style you've shifted over to using on this project more recently...
const ABC = ({ children, query }) => {
  return (

{query}

        {children}

  );
};

ABC.propTypes = {
  children: PropTypes.object,
  query: PropTypes.string
};

export default connect(mapStateToProps, { ... })(ABC);


ListArrayType on Set entity attribute fails for EntityManager.merge operation

Describe the bug
ListArrayType on Set entity attribute (like in this test) leads to the Can not set java.util.Set field ... to java.util.ArrayList error.
To Reproduce
Using existing test cases, just change persist to merge in existing test (line reference):
entityManager.merge(
    new Event()
        .setId(1L)
        .setSensorIds(

Expected behavior
As for now, you will get an exception, while expecting merge operation to be successfully completed.
Additional context
This seems to be an issue in ListArrayTypeDescriptor, and its MutableMutabilityPlan.deepCopyNotNull implementation in particular. It always returns ArrayList, while actual attribute type maybe be List or Set.
Seems like it should consider actual propertyClass, like we have in newPropertyCollectionInstance method in the same class.

Looking forward to your Pull Request that fixes the problem.

what's the status of this? is the PR ready for merge? I'm facing the same issue.

The status id Open.
I don't know since I didn't have time to review it.

Fixed.


Updated WP blogs details

added more details and trivia about top wp blogs

Thank you @mnagarajan sir for the contribution. You are awesome :)


Feature: Youtube / Youtube music

Would love to see Youtube and/or Youtube music integration.

Okay that'll be good enough for now. At least with the chrome extension I can get music.youtube.com tracks scrobbled.

Revisting this...it might be doable with ytmusicapi now.

Setup is straight forward and uses info that can be passed as a string
There is a library history call now
May be able to use PyNode to interop between the two without too much friction?

@OmgImAlexis if you'd like to give it a try its available on foxxmd/multi-scrobbler:develop image. Config instructions here

Implemented in v0.4.1


Parameter hints text can flow out of widget

We need to look into this as E6 will land Monday.

Should be fixed now:

For verification, since we reverted the electron update please test this on web using the latest Chrome


[OAuth] Owned apps API

Related to: https://github.com/CartoDB/cartodb/issues/14985

Acceptance 🍏
I had to create this PR, since there was a bug in the central API used to sync oauth apps.

Mmm I made some more tests and I was able to do certain operations I should no be able to.
For example, as an org user I was able to delete an oauth_app from a regular user.
@gonzalor ^^

Acceptance 🍏 like a charm


[EPIC] Data Security & Privacy Improvements

(This epic is a WIP)
Description
The main goal of this epic is to ensure Hypha is logically retaining data and abides by OTF's data security/privacy policies.
Users

[ ] Handling of user deletion #3441

Cleaning on input and not output would be a nice improvement here I think.
I'm really attracted to the idea of converting all input into markdown and only saving that instead of the HTML spagetti we are saving now. Then no more need for things like the TinyMCE editor or similar.

@frjo I totally agree! That would probably end up also being an item of #3713 as I think it would save us quite a bit of time in the future with features like compare


removed duplicate message; changed github cookie spec

#2261

removed duplicate "Downloading:" message
when downloading from Github, set cookie spec to STANDARD to allow for 4-digit year in header

Comments here https://issues.apache.org/jira/browse/HTTPCLIENT-1763 suggest the default spec may be outdated in general. We are only getting this warning with Github because it's the only one sending these headers, but maybe this setting should be changed for all downloads?

I don't believe ignoring or refusing cookies is possible


[T8] Update slides

Dear tutorial chairs,
Can you help us remove the "slides" link from our website ASAP (see the screenshot):
https://virtual.acl2020.org/tutorial_T8.html
It is only linked to a 2-page version and I start receiving messages about this. I already uploaded all the slides to the Github link: https://github.com/danqi/acl2020-openqa-tutorial so removing it is better.
One quick thing - I wonder if we can customize our page similar to the T6 website (see the screenshot) so we can have a table of sections and links to all the slides there too? Please let me know what format I should follow and I can send you all the information soon.
Thank you again for your help!
Best,
Danqi

@raosudha89 Thank you so much for the help!
This looks great!  Can you maybe also help us add one more speaker column?
The order of the 8 parts are:
Danqi Chen
Scott Yih
Scott Yih
Danqi Chen
Danqi Chen
Danqi Chen
Scott Yih
Scott Yih

Done. This is should be reflected upon today's website release.


[App] install application

mnist_trainingSet.dat was missing in the installation,
which prevented the app to run.
This patch fixes the issue.
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #912. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #912. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/912-202101282128510.67645192146301-3ba3076c2f2c86256fe27ddf63dc2914325b0c99/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/912-202101282128510.67645192146301-3ba3076c2f2c86256fe27ddf63dc2914325b0c99/.

Please note that this patch requires save path modification to pass the test, it will be done and this PR will be rebased.

Please note that this patch requires save path modification to pass the test, it will be done and this PR will be rebased.

This pr needs a patch regarding #731 before merge

v2. amended last commit to remove default path to resolve #731
Add a check to see if save_path is valid if not, issue a warning
Semantic changes:
From this patch, default save path is gone
Self evaluation:

Build test: [X]Passed [ ]Failed [ ]Skipped
Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>


Return correct board members on board create

This fixes you not being an admin on your own boards before refresh

GOOB


Theme toggle is not working on web

Describe the bug
I have a simple test component to test changing theme modes
When I toggle it on the web, for some reason this does not change the theme.
And + when I toggle it with Toggle component or buttons, all app animations are super slow,
for example opening drawer
And setColorMode it's not properly typed
const setColorMode: (value: any) => void

import React from 'react';
import {Text, HStack, Switch, useColorMode, Button} from 'native-base';

export const ThemeToggle = () => {
  const {colorMode, toggleColorMode, setColorMode} = useColorMode();
  return (
    <HStack space={2} alignItems="center">
      <Text>Dark</Text>
      <Switch isChecked={colorMode === 'light'} onToggle={toggleColorMode}></Switch>
      <Text>Light</Text>
      <Button
        onPress={() => {
          setColorMode('light');
        }}
      >
        Test light
      </Button>
    </HStack>
  );
};

Expected behaviour
No slow animation and toggling theme in web
Platform

NativeBase version "^3.2.2",
Device: PC
OS: Windows 10
Browser Google Chrome
Browser version 96.0.4664.110
React Native version 0.64.3
Expo sdk version 43
node v14.17.3
yarn or npm 6.14.13 (npm)

Seems like you are missing something. Here is an example you can check.
https://codesandbox.io/s/setcolormode-example-mlj2b?file=/src/components/Example.tsx

I think setColorMode must be used as child of NativeBaseProvider


Replace option.Config.{Get,Set,Append}Devices by table lookups

This replaces usages of the Get/SetDevices APIs by lookups to the device table, and includes the necessary plumbing of that everywhere.
Scary stuff includes the wireguard interface thing in daemon/loader, not sure my transformation is functionally equivalent. CI will hopefully tell.

/test

/test

/test

/test

/ci-e2e

/ci-e2e

/test

/test

/test

/test

/test


Sample real-world deployment script

I have just started with Deployer and find it to be very powerful but lacking in a "big picture" overview of how it can be used. So now that I've figured out my own Deployer script and how to implement it, I thought I'd write up this little documentation page to share with others and hopefully save them some of the time and frustration I had to deal with. ;-)

Q
A

Bug fix?
No

New feature?
No

BC breaks?
No

Deprecations?
No

Fixed tickets
N/A

Do not forget to add notes about your changes to CHANGELOG.md
Easiest way to do it, by running next command:
php bin/changelog

Also, build a failing. Try to run php bin/changelog fix


Fury barbarian damage resistance is inverted

When damaged by player characters, Fury barbarian's level 9 physical damage resistance doesn't trigger on weapon attacks, but triggers on fist attacks.
To reproduce:

Create a Fury barbarian character with level 9+ and apply Effect: Rage to them
Create another Character actor with a weapon (I used iconic Ezren with a staff)
Damage the barbarian with the character's weapon -> no resistance
Damage the barbarian with the character's fist -> resistance

I should mention, however, that I don't believe there is a simple distinction between NPC weapon and non-weapon attacks (like Barbazu's beard and claw, or dragons' melee attacks are not considered unarmed).

This was fixed in #14480

Actually, I don't believe that it was fixed.
Here are the results I get in 5.15.3 (Ezren damages catfolk Fury Barbarian)

First with a staff (weapon), then with an unarmed Strike (non-weapon)

This is what I get with the same experiment, both on master and release. Maybe you haven't done the level 0 and back dance with your barb?

You are correct. I've reset the level and it worked as intended.
Must have been some unfortunate timing as I usually try to confirm bugs on the master branch, but this time the version I used was just a bit out of date.
My second statement about NPC Strikes is still valid, but it's way beyond this issue and would probably require some major data overhaul.


Feature Request: Show the line number of the incorrect statement along with the compiler error.

Is your feature request related to a problem? Please describe.
Right now the compiler/parser only shows the error and doesn't show the specific line number.This can make the parser errors much more verbose.
Describe the solution you'd like.
Add a line field to the token class which is tracked and incremented in the scanner. The line number can be shown be shown along with the parser error.
Describe alternatives you've considered
No response
Additional context.
No response

I can work on this issue.