Allow to exclude/skip tasks from command-line

Why this is needed:

Reasons :smile:
Currently setup.py proxying to ./build.py install cannot do simple package/install and runs all compliance and other tests.  This takes forever when doing pip install git+git. There should be a way to disable everything without compromising the consistency of the build.

For example, install depends on package as a requirement, package depends on compile as a requirement, but test, analyze, integrationtest are optional for it.
This requires:

@depends to allow to specify required and optional dependency tasks.
additional command-line option "-x"  (for excluded) specifying a comma-separated list of tasks to skip
changes to Reactor build plan

If plan resolves and no required dependencies are missing then everything runs as usual skipping excluded optional tasks.
If the requested build tasks cannot be executed without excluded tasks, then PyB complains and quits.
For backwards compatibility, all @depends tasks that are not optional are required preserving original behavior.
@mriehl, thoughts?

Sounds good. Things that could be optional are all the QA plugins I guess.
Also like the proposed command line switches.

Maybe another way to look at it would be blacklisting plugins when starting. Like pyb -x python.unittest_plugin. Much easier to implement and builds on the consistency we already have.

Blacklisting specific plugins is another feature, I think. For custom plugins that provide multiple tasks or add before/after actions, you may want to keep some and get rid of the other.

I agree with you. I would also add a --x-force though (so users can force exclude tasks at their own risk).

Interesting. But how would --x-force behave in your mind?
Let's say X depends on B depends on A. I force-exclude B, is a transitive dependency on A preserved?

Tough call... respecting the transitive dependencies would be more of a best effort thing (eG really just skip this exact task) but OTOH avoiding to resolve it's dependencies is simpler and more likely to succeed. I like the approach in #175

Thanks! Do you want to release a new version? I think we should get all these improvements out to the users, we can always do a later release with more features.

I want to knock down the final cleanup as well before we release, #173


Original JPEG to overlay with PNG does not work

I have an original image in multi-format (JPEG, GIF, PNG)
Watermark file is a transparent PNG.
$img1  = new SimpleImage($image_full_path);
$img2 = new SimpleImage(null, 560, 292, '#FFF');
$img2->overlay($img1->best_fit(560, 292), 'center', 1, 0, 0);
$img2->overlay('watermark/background.jpg', 'center', 0.3, 0, 0);
$img1 is a JPEG file.
Result: overlay doesnt show.

I just have this problem solved.
The cause for the problem was that, the original PNG image was compressed using tinypng.com therefore, some information must have been lost.
Once I put the original PNG file, the above code works fine.

Strange. Not sure what TinyPNG is doing to the image but obviously GD doesn't like it.


Traefik does not work as ingress behind an AWS ELB

Do you want to request a feature or report a bug?
Bug
What did you do?
I created a service as loadbalancer on port 80, which is the Traefik proxy port and the node got automatically registered to it. If i hit the elb i get the proxy 404 which is OK because no service is registered yet
I then created a nodeport service for the web-ui. targeted port 8080 inside the pod and 80 on clusterip. I can curl the traefik ui from inside the cluster and it retruns traefik UI
I then created an ingress so that when i hit elb/ui it gets me to the backend web-ui service of traefik and it fails. I also have the right annotations in my ingress but the elb does not route the path to the traefik ui in the backend which is running properly
annotations:
kubernetes.io/ingress.class: traefik

What did you expect to see?
Traefik web UI
What did you see instead?
404 of the proxy
Output of traefik version: (What version of Traefik are you using?)
Latest

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Træfik!
We dedicate the issue tracker to bug reports and feature requests only.
If you have questions and need community support, you can join our Slack workspace and reach out to us on the #support channel.
Another option is to use Stack Overflow and tag your question traefik.
Of course, double checking Træfik's documentation is always a good idea :sweat_smile:

@vahidfar7  IF you running on private subnets. you have to include annotation
annotations:
"service.beta.kubernetes.io/aws-load-balancer-internal": "<IP_ADDRESS>/0"


Collections: copy-write scope support

In order to provide the copy/rename write operation used by collections, Gaia needs to support a new copy-write scope.

PRs merged into develop. Can we close or should we wait until deployed to master & prod?

Let's close since it's been merged.


Modular Assert

This changeset requires #3582.
Moving on with the modularization by adding HPX.Assert. HPX.Assert has HPX.PP and HPX.Config as dependencies, which are included in this PR.
The assert implementation has been improved to not evaluate the expression to assert on when assertions are turned of (similar to the optional message). Documentation has been added to all three modules.

@sithhell what's the plan for this and #3629?

Closing in favor of a cleaned up version coming up soon.


Add @aaronlehmann to maintainers

:tada:

LGTM congrats!

LGTM, ping @aaronlehmann

:up: :+1:

LGTM

LGTM 🐹

LGTM!

LGTM :congratulations:

Thanks everyone!

LGTM


feat: maci-signup-flow

[x] adding useMaci hook
[x] adding button to signup to maci in ConnectButton.tsx
[x] adding NEXT_PUBLIC_MACI_ADDRESS in .env.example and update the configs

problems:
../maci/node_modules/.pnpm/@nomicfoundation+solidity-analyzer-darwin-x64<EMAIL_ADDRESS>Module parse failed: Unexpected character '�' (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
(Source code omitted for this binary file)

Import trace for requested module:
../maci/node_modules/.pnpm/@nomicfoundation+solidity-analyzer-darwin-x64<EMAIL_ADDRESS>../maci/node_modules/.pnpm/@nomicfoundation+solidity-analyzer<EMAIL_ADDRESS>../maci/node_modules/.pnpm/hardhat@2.19.5_ts-node<EMAIL_ADDRESS>../maci/node_modules/.pnpm/hardhat@2.19.5_ts-node<EMAIL_ADDRESS>../maci/node_modules/.pnpm/hardhat@2.19.5_ts-node<EMAIL_ADDRESS>../maci/node_modules/.pnpm/hardhat@2.19.5_ts-node<EMAIL_ADDRESS>../maci/node_modules/.pnpm/hardhat@2.19.5_ts-node<EMAIL_ADDRESS>../maci/contracts/build/ts/deploy.js
../maci/contracts/build/ts/index.js
../maci/cli/build/ts/commands/airdrop.js
../maci/cli/build/ts/commands/index.js
../maci/cli/build/ts/index.js
./src/hooks/useMaci.ts
./src/components/ConnectButton.tsx
./src/components/Header.tsx
./src/layouts/DefaultLayout.tsx
./src/pages/projects/index.tsx

Not sure what's the main reason here. I thought it was caused by importing hardhat modules, but I checked my past repos, they still work well even with hardhat dependencies 🤔
We also tried to remove calling defaultSigner() and defaultNetwork() (linking local package), but it still not works.

close because it's been implemented and merged.


feat(BSC): CW-3614 add BSC segment script

Checklist:

README.md includes:

[ ] The details of signing data and transaction data, this includes parameters.
[ ] Official docs or white paper.
[ ] Website or api can query assets and broadcast transaction.

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

Task linked: CW-3614 Modify coin-bsc to support two different modes of signing payload


setLayerType

setLayerType  in android 2.3,not use,how to use this in android2.3

setLayerType was first introduced in Honeycomb. It's not available in 2.3.


create openpublishing.redirection.json

create openpublishing.redirection.json

Docs Build status updates of commit c149b90:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 003ad94:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


ledger_device_sdk::testing::debug_print causes hangs on nanos device

In an app, which is a fork of this repo,
using https://github.com/LedgerHQ/app-boilerplate-rust/blob/main/src/handlers/get_public_key.rs#L61 causes hangs on nanos device, which sometimes, after repowering the device, starts initial sequence of recovery phrase input, and sometimes, causes it to go into booting mode.
i've changed the Cargo.toml in this app to
[features]
default = []
speculos = ["ledger_device_sdk/speculos"]

and annotated each usage of  debug_print with cfg:
#[cfg(feature = "speculos")]
testing::debug_print("something\n");

It feels like testing::debug_print was only intended for use within speculos emulator,
so it might be nice (a mere suggestion), if the function were made a no-op in ledger_device_sdk, when speculos feature is disabled:
#[cfg(not(feature="speculos")]
pub fn debug_print(s: &str) {
}

So that there's no need to add #[cfg(feature = "speculos")] in ledger_device_sdk client code.

Hello and thanks for the detailed report! I believe it is an oversight and should be removed instead https://github.com/LedgerHQ/app-boilerplate-rust/pull/48


De-dup in Mangadex chapter list

Why/User Benefit/User Problem
With this feature, we can remove the duplicate chapters from the list (duplicate chapters means same chapter uploaded by different scanlators ) and updates of the manga if the new chapter is already uploaded by another group.
What/Requirements
This feature focuses on the chapters instead of the group which are translating.
A toggle/filter option in the manga filter, where we can enable with below behavior

Remove the duplicate chapters from the manga list where oldest chapter will have high priority.
There won't be any manga updates if the chapter is already available (If ch333 is available, and the same chapter is uploaded by a different group, it will be excluded).

i think this feature would make the app from great to awesome. hopefully waiting

also got a request similar to this but prioritizing a group

also got a request similar to this but prioritizing a group

This covers somewhat but the second option
If the chapter is already read and other groups uploads the same chapter(it will redownload the chapter), can this be implemented as recently for some of the series some groups are republishing from beginning and there is no need of downloading those

quick test on it, at it seemed to work as expected! thanks a lot!
it tries the similar source first, if there isn't it checks other source instead of "just" continues to next row in list of chapter.


Editable/develop install with spaces in path results in unusable #!

As I dig deeper I get a bit more confused but it seems that pip install --editable installs are not creating sensible #!s for POSIX when there are spaces in the path.
--editable
#!"/home/altendky/very_sneaky/venv with spaces/bin/python3"

regular
#!/bin/sh
'''exec' "/home/altendky/very_sneaky/venv with spaces/bin/python3" "$0" "$@"
' '''

The undesired results seem to come from:
https://github.com/pypa/setuptools/blob/7be2d14dcd669d6010621a8e5db23763a63cf55e/setuptools/command/easy_install.py#L2047
From what I can tell the regular result is built by distlib (vendored in pip).
https://bitbucket.org/pypa/distlib/src/3b0fd333c8fb15bc04e570a23ee4836caefb7951/distlib/scripts.py#lines-139:168
    def _build_shebang(self, executable, post_interp):
        """
        Build a shebang line. In the simple case (on Windows, or a shebang line
        which is not too long or contains spaces) use a simple formulation for
        the shebang. Otherwise, use /bin/sh as the executable, with a contrived
        shebang which allows the script to run either under Python or sh, using
        suitable quoting. Thanks to Harald Nordgren for his input.

        See also: http://www.in-ulm.de/~mascheck/various/shebang/#length
                  https://hg.mozilla.org/mozilla-central/file/tip/mach
        """
        if os.name != 'posix':
            simple_shebang = True
        else:
            # Add 3 for '#!' prefix and newline suffix.
            shebang_length = len(executable) + len(post_interp) + 3
            if sys.platform == 'darwin':
                max_shebang_length = 512
            else:
                max_shebang_length = 127
            simple_shebang = ((b' ' not in executable) and
                              (shebang_length <= max_shebang_length))

        if simple_shebang:
            result = b'#!' + executable + post_interp + b'\n'
        else:
            result = b'#!/bin/sh\n'
            result += b"'''exec' " + executable + post_interp + b' "$0" "$@"\n'
            result += b"' '''"
        return result

The details are provided from Linux.  The original issue was reported to me from macOS.
Recreation Details
 ~/very_sneaky   master ●  virtualenv -p python3 venv\ with\ spaces
Running virtualenv with interpreter /home/altendky/.pyenv/shims/python3
Using base prefix '/home/altendky/.pyenv/versions/3.7.2'
New python executable in /home/altendky/very_sneaky/venv with spaces/bin/python3
Also creating executable in /home/altendky/very_sneaky/venv with spaces/bin/python
Installing setuptools, pip, wheel...
done.

 ✘  ~/very_sneaky   master ●  git clone https://github.com/ambv/black
Cloning into 'black'...
remote: Enumerating objects: 5, done.
remote: Counting objects: 100% (5/5), done.
remote: Compressing objects: 100% (5/5), done.
remote: Total 2494 (delta 0), reused 1 (delta 0), pack-reused 2489
Receiving objects: 100% (2494/2494), 3.00 MiB | 3.93 MiB/s, done.
 Reason:
The file 'venv with spaces/bin/black' does not exist or could not be executed.

 ✘  ~/very_sneaky   master ●  head venv\ with\ spaces/bin/black
#!"/home/altendky/very_sneaky/venv with spaces/bin/python3"
# EASY-INSTALL-ENTRY-SCRIPT: 'black','console_scripts','black'
__requires__ = 'black'
import re
import sys
from pkg_resources import load_entry_point

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(

 ✘  ~/very_sneaky   master ●  venv\ with\ spaces/bin/pip freeze --all
appdirs==1.4.3
attrs==19.1.0
-e git+https://github.com/ambv/black@cea13f498418784e22f8fbd78db3f9240a2bad11#egg=black
Click==7.0
pip==19.0.3
setuptools==41.0.0
toml==0.10.0
wheel==0.33.1

 ~/very_sneaky   master ●  cat venv\ with\ spaces/bin/pip
#!/bin/sh
'''exec' "/home/altendky/very_sneaky/venv with spaces/bin/python3" "$0" "$@"
' '''
# -*- coding: utf-8 -*-
import re
import sys

from pip._internal import main

if __name__ == '__main__':
    sys.argv[0] = re.sub(r'(-script\.pyw?|\.exe)?$', '', sys.argv[0])
    sys.exit(main())

As a separate issue but with a (possibly) similar fix, doing a develop install in a virtualenv that has been created in a deeply nested directory can result in a script with a shebang that's too long. Using distlib (or at least distlib's method of generating the shebang) would also solve this problem.


Twitter API docs links in Readme are outdated

Seems like Twitter API docs have moved, it be nice to have correct, working, links in there.

The links are the path of the resource but if you would like documentation it can be found at https://developer.twitter.com/en/docs/api-reference-index


Using workflow custom function on AWS lambda

I am trying to convert a a legacy workflow step to the new custom function in AWS lambda, but do not see any documentation on this.
The closest is https://api.slack.com/automation/functions/custom-bolt and https://api.slack.com/tutorials/tracks/bolt-custom-function, but both are using SocketModeHandler and have no mention of FaaS, like AWS lambda.
Is the feature compatible?

Yes, it should be no problem using any adapter of your choice. At the end of the day, custom functions are invoked by Slack sending a function_executed event to your app. How the event is delivered (socket mode or HTTP) is up to you to decide via your app configuration.


Add reference time series logical file type to composite resource

This should be easy since referenced time series is now represented by a simple JSON file. An example such file is attached here. Note that the actual resource will have extension is yet to be determined. We may want to use ".json.refts" to help apps understand it.
timeseriesLayerResource.json.txt

@dtarb , @danames and @alvacouch I have noted the requirements (see above) for implementing this file type based on the discussion we had today. If I have missed any requirements please add/modify the note I have above.

Answers to questions, as I recall them from the phone call are:

Yes one json file
Yes validate that the json file has needed elements
No metadata editing except for file level keywords.  The json file is not edited as it reflects the contents of the reference resource that cannot be changed.  Keywords from the json file are copied into the Django file level keywords on initial load, but a HydroShare user is able to change them, resulting in changes in the Django db and XML metadata, but not json file.
Yes, display json file
Yes store contents in Django db.
We did not answer this question.  Can we use a format similar to stored time series.

Need to test after HIS work is done

More specifically, once the Resource Creator app is finished and posted to Apps, then we can test this by finding resources in data.cuahsi.org and then turning them into referenced time series JSON files in a composite resource.

Tested today and found the following small shortcomings.

When a .json.refts file is set to refts type and the resource title has not yet been entered, it needs to take the value from the title entry in the refts file.
Editing refts file type title should change the title entry in the refts file (or provide the option for this, similar to sync operations in netcdf and sqlite time series)

Also are there API functions to

load a file into a composite resource
set the file to Reference Timeseries file type

If (once) these are done, I think this issue should be closed and work on apps that access this resource type managed in separate issues.

Tested and working on release candidate 1.13.


Shastarnaama mala ਮਾਤਰਾ differences

ShasterNaam maala is different here
Check iGurbani app or Sundar Gutka app
Please select which platform you are using:-
Web Version
Feedback Type
Mistakes in ਮਾਤਰਾ
What went wrong?
ShasterNaam Mala here in your website is different from iGurbani app , Sundar Gutka and Isher Micro Media(IMM) app.
Please checkCorrect it, if it is different
What should have happened instead?
Correction needed
How can the issue be recreated by our team?
Reffer those app as mentioned aboveSpelling mistakes .
Which web browser are using?
Chrome 74.0.3729.157
Operating System
Microsoft Windows
Name
Parmjot  Singh

@gurjeetsingh can you take this up?

@gurjeetsingh - pls quickly compare the differences on this screenshot. See if our version is different from what's published by SGPC.

Yes, sttm is missing almost all adhaks and nasal bindia

@gurjeetsingh can you please submit the corrections to CP .. I believe we typed ours up out of the buddha dal gutka

@pdvsingh did you ever get the source to @gurjeetsingh


Add search page

Addition of a /search page, as part of the spike to add G6 filters.
The filters for this page were meant to be built on top of a static data source but this wasn't available so we just have the page and a sample data source to be built on top of later.

npm install is dying in Travis...


feat(px-3991): sticky stacking

Closes: PX-3991
The Problem
For the first time, on the partner profile we have two stickies in the same viewport. Previous implementation only assumes the existence of the header, so they overlap at the same offset.

The Solution
Register each sticky in a context and calculate the correct offset.

This seems fine to me! Feel free to merge when the conflicts are fixed!


JSON-LD Parsing - missing exception with invalid @id

Current Behavior
Parsing invalid "@id" values in a JSON-LD document like in the following example just resulted in no statements.  (via RIO and ContextStatementCollector)
{
  "@context": {
    "ical": "http://www.w3.org/2002/12/cal/ical#",
    "my": "http://example.org#"
  },
  "@type": "ical:Vevent",
  "@id": "1234",
  "ical:summary": "Lady Gaga Concert"
}

Result:  {statements=[], namespaces={}} (from ContextStatementCollector)
The following example is valid and works
{
  "@context": {
    "ical": "http://www.w3.org/2002/12/cal/ical#",
    "my": "http://example.org#"
  },
  "@type": "ical:Vevent",
  "@id": "my:1234",
  "ical:summary": "Lady Gaga Concert"
}

Result {statements=[ (http://example.org#cal124121323, http://www.w3.org/1999/02/22-rdf-syntax-ns#type, http://www.w3.org/2002/12/cal/ical#Vevent),  (http://example.org#cal124121323, http://www.w3.org/2002/12/cal/ical#summary, "Lady Gaga Concert")],  namespaces={}}
The following example is also valid and works
{
  "@context": {
    "@base": "http://www.example.org",
    "ical": "http://www.w3.org/2002/12/cal/ical#"
  },
  "@type": "ical:Vevent",
  "@id": "1234",
  "ical:summary": "Lady Gaga Concert"
}

Expected Behavior
I am not exactly sure about the expected behaviour. According to the spec, the "@id" has to be an IRI. Leaving the prefix should require at least "@base" definition in the "@context" (even though the json-ld playground considers it to be valid and injects its own "@base")
{
  "@context": {
    "ical": "http://www.w3.org/2002/12/cal/ical#"
  },
  "@id": "1234",
  "ical:summary": "Lady Gaga Concert"
}

results in
<https://json-ld.org/playground/1234> <http://www.w3.org/2002/12/cal/ical#summary> "Lady Gaga Concert" .
This might work (e.g. have a default namespace set when a base namespace is missing), but I think an exception makes most sense here.
Steps To Reproduce
Here's my code
...
RDFParser parser = .. from ParserFactory for JSON-LD
ContextStatementCollector collector = new ContextStatementCollector(simpleValueFactory);
try (InputStream is = dataBuffer.asInputStream(true)) {
   parser.setRDFHandler(collector);
   parser.parse(is);
...

``

### Version

4.0.0-M1

### Are you interested in contributing a solution yourself?

Perhaps?

### Anything else?

Here's the source code where the issue is happening: https://github.com/bechtleav360/eagl-service-graph/blob/main/src/main/java/com/bechtle/eagl/graph/config/converter/RdfDecoder.java

I'm rusty on my JSON-LD but is it possible that this is because you're using a JDON-LD 1.1 feature? I think our current support (which relies on jsonld-java) only covers 1.0.

The relevant part in the spec about node identifiers  didn't change, as far as I can see. The @ID must be a valid URI/IRI, either fully qualified or resolvable through the default namespace (base).


✨ Move selected lines up and down

Description
Users should be able to move lines up or down with ⇧ ⌘ [ and ] or by going to Editor > Move Line Up and Move Line Down.
Screenshots

@austincondiff I would like to work on it, however would need some guidance on where the files located? QQ: Its in CodeEditSourceEditor project?


No APNS error when requesting token

Hi, every time I try to request the device fcm token I get this error message.
2023-12-30 12:19:55.624090+0200 My firestore[20248:337188] 10.16.0 - [FirebaseMessaging][I-FCM002022] APNS device token not set before retrieving FCM Token for Sender ID '238435558784'.Be sure to re-retrieve the FCM token once the APNS device token is set.
2023-12-30 12:19:55.624209+0200 My firestore[20248:337188] 10.16.0 - [FirebaseMessaging][I-FCM002022] Declining request for FCM Token since no APNS Token specified
FirebasePushNotifier is initialized
Error while getting token: Error Domain=com.google.fcm Code=505 "No APNS token specified before fetching FCM Token" UserInfo={NSLocalizedFailureReason=No APNS token specified before fetching FCM Token}
TOKEN : null

@tz2006
1)As shown in ios Setup part did you add this part of code to AppDelegate's didRegisterForRemoteNotificationsWithDeviceToken function?
2)Can you please log that onNewToken function is called or not?
import SwiftUI
import shared
import FirebaseCore
import FirebaseMessaging

class AppDelegate: NSObject, UIApplicationDelegate {
  func application(_ application: UIApplication,
                   didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {

      FirebaseApp.configure() //important
      NotifierManager.shared.initialize(configuration: NotificationPlatformConfigurationIos.shared)

    return true
  }

  func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
        Messaging.messaging().apnsToken = deviceToken
  }

}

@main
struct iOSApp: App {

    @UIApplicationDelegateAdaptor(AppDelegate.self) var delegate

    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

Closing this issue due to inactivity. If this is still an issue or need a help, please feel free to reopen the issue and provide additional context or updates. Thank you.

I'm also getting this error :
Error while getting token: Error Domain=com.google.fcm Code=505 "No APNS token specified before fetching FCM Token" UserInfo={NSLocalizedFailureReason=No APNS token specified before fetching FCM Token}
The local notifications work perfectly.
This is my app delegate code :
class AppDelegate: NSObject, UIApplicationDelegate {

    func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey : Any]? = nil) -> Bool {
        FirebaseApp.configure() //important

        //By default showPushNotification value is true.
        //When set showPushNotification to false foreground push  notification will not be shown.
        //You can still get notification content using #onPushNotification listener method.
        NotifierManager.shared.initialize(configuration: NotificationPlatformConfigurationIos(showPushNotification: true, askNotificationPermissionOnStart: false, notificationSoundName: nil))

        return true
    }

    func application(_ application: UIApplication, configurationForConnecting connectingSceneSession: UISceneSession, options: UIScene.ConnectionOptions) -> UISceneConfiguration {
        // Called when a new scene session is being created.
        // Use this method to select a configuration to create the new scene with.
        return UISceneConfiguration(name: "Default Configuration", sessionRole: connectingSceneSession.role)
    }

    func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
          Messaging.messaging().apnsToken = deviceToken
    }
    func application(_ application: UIApplication, didDiscardSceneSessions sceneSessions: Set<UISceneSession>) {
        // Called when the user discards a scene session.
        // If any sessions were discarded while the application was not running, this will be called shortly after application:didFinishLaunchingWithOptions.
        // Use this method to release any resources that were specific to the discarded scenes, as they will not return.
    }
}

@planasmultimedia maybe you didn't added apn certificate to Firebase? Also Push Notifications capability should be added in ios as well


Consider stripping the crate version when building dependencies

Originally discussed in https://github.com/ipetkov/crane/issues/281
The crux of the issue is that we automatically inherit the crate's version attribute (from Cargo.toml) as the version of the buildDepsOnly derivation. The value is also not stripped when cleaning the Cargo.toml file. This unfortunately means that when a crate's version is updated (e.g. to publish a new release) it will invalidate the cache and require building all dependencies from scratch.
A more cache-friendly solution would be to replace version with a static placeholder value (both when cleaning the Cargo.toml and when setting the buildDepsOnly derivation's version attribute).
One possible downside of this is if a project uses a build command which somehow relies on the version of the crate (e.g. tries to parse something like cargo tree mycrate@x.y.z). I think there should be an escape hatch (such as doNotStripVersion = true; or equivalent) which would bring back the previous behavior if required

Some more observations on this: changing the versions of any Cargo.toml [package] definition would also need to subsequently change the respective Cargo.lock definitions as well, otherwise cargo will complain about the lockfile being out of date (since we pass in --locked)


RFC: Deprecating NNG

We're carving this out as a separate topic...
@jeremyandrews:

Just an FYI: I am in the process of removing the dependence on nng and reworking the Manager-Worker logic on top of raw Tokio sockets, the same as the controllers are currently implemented. The underlying functionality will be the same, though this will allow me to address a number of known Gaggle (distributed loadtest) bugs and increase flexibility.

Hmm, color us skeptical on removing NNG.
Message passing/distributed computing is hard.
We cut our teeth on MPI and we've watched RabbitMQ, ZeroMQ, nanomsg, magoes, etc. etc. and its evolution.
There are a ton of hard lessons learned accumulated in those libraries.
Most importantly the things not to do are not in those libraries, and patterns that are more pain than they are worth are either not supported or difficult to pursue.
Can you point to which of the patterns in these categories Goose uses or is configured for?

Reliable request-reply patterns
Advanced Pub-Sub Patterns
Advanced request-reply patterns

We understand the NNG reference manual likely contains updated best practices, but we don't have that and the above are publicly available links to refer to.
If you do decide to replace NNG can you consider the option of making it a plug-able component?
This way people can use what they use.
We don't underestimate the work involved in introducing an abstraction that allows plug-able  components.

The NNG dependency adds some complexity to building Goose, which is why it's currently wrapped in a future - by re-implementing it with Tokio sockets I can remove the feature which simplifies development and testing a bit.
We're using the request-reply pattern. (See here: https://github.com/tag1consulting/goose/blob/main/src/worker.rs#L61 which is documented here:  https://docs.rs/nng/1.0.0/nng/enum.Protocol.html#variant.Req0)
I recently added a Controller:

https://github.com/tag1consulting/goose/blob/main/src/controller.rs
https://github.com/tag1consulting/goose/blob/main/tests/controller.rs

The plan is to make it possible to control the Gaggle through the controller socket, where the Workers make a connection to the Manager and then we maintain a reasonably simple state machine.
Fundamentally, a Worker is the same as a Standalone Goose instance, except it also pushes metrics data to the Manager. The other main driver of replacing NNG is to allow the Controller to control a distributed Gaggle, not just a Standalone instance.
We currently support two protocols (telnet and WebSockets) via Traits. So in theory you could plug in a third protocol by implementing these traits. Offhand however I don't think that's flexible enough to re-implement with NNG.

Fundamentally, a Worker is the same as a Standalone Goose instance, except it also pushes metrics data to the Manager

Yes. we were puzzled about why NNG would be causing runtime headaches.
It sounds like the headaches are purely build time. Correct?

We currently support two protocols (telnet and WebSockets) via Traits. So in theory you could plug in a third protocol by implementing these traits. Offhand however I don't think that's flexible enough to re-implement with NNG.

Not sure I understand.  I was asking about making the messaging/distributed-communication component plugable. The controllers would simply have their messages handed over and passed by whatever messaging plugin was in place.
We had no real headaches building in gaggle, and what hiccups there were are purely documentation issues.
We can envision Gaggle use cases becoming quite demanding - but we can imagine them exceeding the capabilities of nng, etc.
Is this really your sweet spot? We don't know.
We hope you aren't offended by this, we do appreciate all the work and effort put in:
But, if this was being led by Martin Sustrik or Garrett D'Amore we would say no worries - however we'd still be hesitant and stick with the current release until it generated errors the new version fixed.
Can you point to the issue reports that have NNG as the root cause, and at least a discussion of how what's being proposed with Tokio would fix that.
Right now, we're very nervous about ripping out a foundational piece of battle tested fabric (that gives considerable head-room), for something home brewed.

The plan is to make it possible to control the Gaggle through the controller socket, where the Workers make a connection to the Manager and then we maintain a reasonably simple state machine.

Sounds great.  The controller appears to be local only right now, and it seems one of the goals/rationales for NNG's was to make custom protocols less painful to address.
From here:

The other, most critical, motivation behind NNG was to enable an easier creation of new transports

then we maintain a reasonably simple state machine.

We'd advocate going the other direction... of trying to make the Gaggle stateless as possible.  As we indicated in the discussion around CO-mitigation (comment link to come), where the challenge posed as to ensure Requests were being made at fixed intervals. Specifically there you don't want every member of the gaggle starting at exactly the same time, but rather staggered at some known interval.
The choices as we saw them were (from memory): 1) some messaging system 2) some agreed convention.
The more we get into this the more we think the end state (pun intended) to aim for is a Gaggle that is as stateless as possible.

It sounds like the headaches are purely build time. Correct?

Correct, from this blog:
"On most linux distributions you have to add cmake and openssl-dev."
(And for a time it was impossible to build the Gaggle feature on Apple's M1 Silicon amd64 architecture: fortunately this was fixed with NNG 1.0)

We'd advocate going the other direction... of trying to make the Gaggle stateless as possible.

Yes, as noted above, Workers are primarily Standalone load tests that are sharing metrics with the Manager. But with the Controller they still have to maintain a general state of the load test, what is internally referred to as the AttackState.

to ensure Requests were being made at fixed intervals

Coordinating the timing of Requests across a distributed Gaggle is not on my roadmap FWIW: the intent is that while the Manager can Start/Stop/Configure/Shut-down the Worker, when actually running a load test the Workers are essentially standalone and therefor not impacted by the communication channel with the Manager.

Right now, we're very nervous about ripping out a foundational piece of battle tested fabric (that gives considerable head-room), for something home brewed.

Fair. We'll see how it goes, it's possible as I find the time to work on this I may conclude we're better off working with NNG. I certainly don't deny the rich history and experience that it brings.
That said, the only significant traffic in a Gaggle is pushing Metrics from the Workers to the Manager (and this is fundamentally what is already happening within Goose as well as each [GooseUser] is passing Metrics up to the parent process for aggregation and reporting).

It sounds like the headaches are purely build time. Correct?

Correct, from this blog:

Good to know. In out experience, these sorts of issues tend to be transitory.

Performing a staggered start is in scope. Maintaining a staggered request timing is not.

No problem.  For a CO fix the effect of an intra-user schedule will dominate by orders of magnitude the effect of any inter-user schedule.

Right now, we're very nervous about ripping out a foundational piece of battle tested fabric (that gives considerable head-room), for something home brewed.

Fair. We'll see how it goes,

Thanks.

That said, the only significant traffic in a Gaggle is pushing Metrics from the Workers to the Manager

Undertood.  We can envision long running processes monitoring SLA's and the connection recovery management isn't straight forward.


Support canceling remote processes via context.Context

Hi Brice,
I would like to have public access to the err member of the Command struct. This would make it possible to reimplement the Client.Run* methods out of package in a way that supports canceling via context.Context. Would you consider a PR to this effect?

Sorry for the very late answer, but I would prefer to have a PR that adds support for passing a context.Context.

Okay, fair enough.
How do you want to go about this?

expansion of the interface with new functions (RunWithContext)?
change the existing interface (which would probably mean going for v2?)
similar to how http.Request does it (...WithContext()). However this seems to be getting out of favor with the go community, as you have to store the context in the struct.

I think the RunWithContext would be enough for this small library. Internally, it's just a matter of checking if we have a context and calling the WithContext whenever needed.

Is this what you had in mind?
The external interface is unaffected, but for all exposed functions we now have an alternative that takes a context.Context as first argument.

@masterzen Would you be interested in a PR, where we pass the context to the http request as well with http.NewRequestWithContext, so we can control cancellation of the entire process.

@masterzen Would you be interested in a PR, where we pass the context to the http request as well with http.NewRequestWithContext, so we can control cancellation of the entire process.

Hi Paul, I toyed with that as well, however canceling the program on the remote machine requires a successful HTTP REST call, so that did not work out for me.

Hi Paul, I toyed with that as well, however canceling the program on the remote machine requires a successful HTTP REST call, so that did not work out for me.

Hi Klaus-Georg, that's a good point. We should absolutely try not to leave processes hanging in the remote host.
I still think it's an issue that we can't cancel requests, though. If the remote host doesn't respond to http requests we have to wait for the os to give us an io timeout.
Just spitballing, but maybe if we split up the interface, so users could run each step separately with it's own context, so we're not lumping multiple requests into the same call.
Maybe this should be considered a separate issue?


Added support for llama 3.1 models

Changes made :

Added support for the following models :

llama-3.1-70b-Versatile
llama-3.1-8b-Instant

Thanks for the PR! I made some changes in #6 that makes the models list dynamic. Will close this PR.


Account creation fails for a custom network

I am using Stellar Laboratory to test a private Stellar network however the account creation step does not seem to be able to create and fund accounts on the network.
Steps to replicate:

Select custom network and add the Horizon URL and Network Passphrase
Account creation step 1: Generate custom key pair
Account creation step 2: Fund the account using the Friendbot
Laboratory indicates account is successfully funded but the Horizon logs on our network indicate no request was ever received.
Use the Laboratory endpoint explorer to check the account ID. Horizon logs show the request is received from Laboratory but of course Horizon returns 404 because the account was never actually created.

Expected outcome:
Account creation step 2 sends request to custom network Horizon URL and account is created within the custom network allowing it to be used with the endpoint explorer and the other tools of Stellar Laboratory.

You need your own friendbot service for custom networks. What you could do is just create account from a master account (secret of the master account = sha256(network_passphrase, it's also displayed when you run stellar-core --newdb) .


Delete Files and Rename Directory

Do the following:-

Delete file named
LOGISTIC REGRESSION from root directory
There are two folders for ”Gradient Descent”. Merge them into one

seems easy enough

Feel free to create a PR 🎉

Done @iam-abbas

Done @iam-abbas

@sukhwal13 Its already been closed


Add cloud-dot-redhat tests

Codecov Report

Merging #55 (762c8bb) into master (5702978) will decrease coverage by 0.36%.
The diff coverage is 60.00%.

@@            Coverage Diff             @@
##           master      #55      +/-   ##
==========================================
- Coverage   85.24%   84.88%   -0.37%
==========================================
  Files           9       10       +1
  Lines        1159     1250      +91
==========================================
+ Hits          988     1061      +73
- Misses        112      123      +11
- Partials       59       66       +7

Flag
Coverage Δ

unittests
84.88% <60.00%> (-0.37%)
:arrow_down:

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

Impacted Files
Coverage Δ

crhchttp/http_cloud_dot_redhat.go
80.21% <60.00%> (ø)

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 5702978...762c8bb. Read the comment docs.

ping: a kind reminder to review this as well. :smile_cat: :dog: :eyes:
Thanks

ping: a kind reminder to review this as well. :smile_cat: :dog: :eyes:
Thanks

ping @abaiken @maskarb can you please review this?
Thanks

ping @abaiken @maskarb can you please review this?
Thanks

Sorry we haven't gotten to it sooner @boaz0 but, we will get to this PR. We're just trying to get the next release out, and this PR will come after that.

Sorry we haven't gotten to it sooner @boaz0 but, we will get to this PR. We're just trying to get the next release out, and this PR will come after that.


PowerShell Core Enter-PSSession not connecting from MAC to Windows.

Hello,
Could you please help on this issue. I am unable to PS Remote from Mac to Windows 10.
I have have configured all requirements in Windows. Please help me.
PowerShell Core for MacOS
PowerShell Core installed on the Windows server
The Win32 OpenSSH build installed on the Windows
The SSH client session has ended with error message: The SSH transport process has abruptly terminated causing this remote session to break.
At line:1 char:1

Enter-PSSession -HostName <IP_ADDRESS> -UserName<EMAIL_ADDRESS>...

  + CategoryInfo          : ResourceUnavailable: (:) [Enter-PSSession], PSRemotingTransportException
  + FullyQualifiedErrorId : System.Management.Automation.Remoting.PSRemotingDataStructureException,Microsoft.PowerShell.Commands.EnterPSSessionCommand

PS />
PS Core Version:
PS /Users/gowrish> $PSVersionTable
Name                           Value

PSVersion                      6.2.1
PSEdition                      Core
GitCommitId                    6.2.1
OS                             Darwin 18.6.0 Darwin Kernel Version 18.6.0: Thu…
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Do you see the issue with latest PowerShell 7.0 build?

I have the same problem
macOS powershell
PS /Users/zero> $PSVersionTable
Name                           Value

PSVersion                      7.0.3
PSEdition                      Core
GitCommitId                    7.0.3
OS                             Darwin 19.6.0 Darwin Kernel Version 19.6.0: Thu Jun 18 20:49:00 PDT 2020; root:xnu-6153.141.1~1/RELEASE_X86_64
Platform                       Unix
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0


[FEATURE] Support Health and Readiness Probes in flagd

Overview
In production environments, feature flags may be considered a mission critical service that must be available. It's important for flagd to expose a means for Kubernetes to know when the container is ready to perform flag evaluation. Also, needs to be aware if flagd is in an unhealth state so that it can take corrective measures. These settings should be configurable so that a Kubernetes cluster administrator can decide various error conditions should be handled.
Requirements

[ ] Conduct research on the pros and cons of adding health and readiness probes and submit an OpenFeature Enhancement Proposal (OFEP).
[ ] Add health and readiness probes to flagd to monitor the state of the services.
[ ] Update the OpenFeature Operator to automatically configure the health and readiness checks.
[ ] Provide configuration options in the OpenFeature Operator to customize the probes.
[ ] Document the new behavior and configuration options in the flagd documentation.

Resources

https://kubernetes.io/docs/tasks/configure-pod-container/configure-liveness-readiness-startup-probes/

I had a look into this topic. We can re-use the HTTP server created for serving Prom metrics for the probes. This simplifies the implementation. Mind that K8s has a basic behavior regarding health probes: when it fails, it restarts the POD. Hence, we should not add any fancy configuration for this.
For the ready probe, I propose splitting the current ISync interface into two functions: Init(Context) and Sync(Context, chan). This would also make a cleaner implementation for providers such as gRPC.


fix(Slider): control when updates happen better

componentWillReceiveProps was doing a check on object vs object. Even if
the objects had the same props, it would always return false because
JavaScript. Doing a very simple toString-like check is a better check
For more info, read https://reactjs.org/blog/2016/01/08/A-implies-B-does-not-imply-B-implies-A.html
updatePosition changed too much state and fired onChange too much as
well. It would fire on every mouse move, even if the value didn't
actually change
Fixes #329
Test case below. Check the console, it will continuously fire
class Comp extends Component {
  constructor(props) {
    super(props)
    this.setNodes = this.setNodes.bind(this)
    this.state = {node: null}
  }

  setNodes (e) {
    console.log(e.value);
    this.setState({nodes: e.value})
  }

  render() {
    return <Slider id="slider" value={50} min={0} max={100} step={1} labelText="Slider Label" onChange={this.setNodes} />
  }
}

Hey @eddiemonge , could you update this PR so we can get it reviewed and merged in? Thank you!

Updated

For checking prop equality, we'd want to use http://npmjs.com/package/lodash.isequal versus JSON.stringify, I think.

Updated to use lodash.isEqual

Works great, thanks for this fix @eddiemonge! 👍 ✅


Checkup: Use container disk image instead of PVC

Currently, the VMI spec is using a PVC as the storage of the VMI.
This was a temporary in order to start the development process.
Replace the PVC volume with the checkup's custom container disk image [1].
Add the vmUnderTestContainerDiskImage parameter to the user-supplied ConfigMap.
[1] quay.io/kiagnose/kubevirt-realtime-checkup-vm

Tested against an OpenShift Virtualization 4.15 cluster.

Change: Remove leftover PVC params from e2e test.


Added new use case to index.md

I added Club Brugge to the index.md file as a use case
Type of PR

[ ] BUG
[ ] FEAT
[ ] MAINT
[x] DOC

PR Checklist

[x] Added documentation for changes
[ ] Added feature to example notebooks or tutorial (if appropriate)
[ ] Added tests (if appropriate)
[ ] Updated CHANGELOG.md (if appropriate)
[ ] Made changes based off the latest version of Splink
[ ] Run the linter
[ ] Run the spellchecker (if appropriate)

Yeah no problem, thank you for developing this software, it was a huge help!


Update dapr-test.yml

@yaron2 my command works. please see the below

@yaron2 my command works. please see the below

This is not the command in the yml.

The test that just ran with the previous PR failed with:
error: the server doesn't have a resource type "describe"
##[error]Process completed with exit code 1.


hyperspy

http://hyperspy.org

HyperSpy is an open source Python library which provides tools to facilitate the interactive data analysis of multi-dimensional datasets that can be described as multi-dimensional arrays of a given signal (e.g. a 2D array of spectra a.k.a spectrum image).
HyperSpy aims at making it easy and natural to apply analytical procedures that operate on an individual signal to multi-dimensional arrays, as well as providing easy access to analytical tools that exploit the multi-dimensionality of the dataset.

I/O, file format(s)

You may also like to note this: https://github.com/pyxem/pyxem which also builds on hyperspy for scan and record a diffraction pattern at every probe position type experiments.


Error 404 found on selecting About from nav bar

Is it a ?

[X] Bug Report

[ ] Feature Request

[ ] Chore

Bug Report
Actual Behaviour
After creating event, on selecting about from nav drawer, 404 is being shown on the logs

Expected Behaviour
No error
Steps to reproduce it
Create a event
Select about from nav drawer
Would you like to work on the issue?
Yes

@iamareebjamal Please review

Not an issue. Copyright isn't present so 404 will be thrown obviously


FEATURE: added a datepicker module(#237)

Adds #237
Right now it only had the value prop, but I will add more as per comments.

Thanks for taking this on a couple things. The library seems to be react-datepicker does your code work locally. You will also need to add this library to our package.json
As for props and events
-In addition to onChange we should support onSelect
More props can be these but snake case: closeOnScroll, dateFormat, startDate, endDate, minDate, maxDate, isClearable, placeholderText, showWeekNumbers, shouldCloseOnSelect

I have added the new props. However, should the date values be of datetime type? Or the framework handle it on its end.
I ahve not tested locally. I am working in a Codespace. The tests are running fine.

Looking good thanks for the changes, can you add comment and doc strings like our other components also can you text to see if it runs locally. https://github.com/pynecone-io/pynecone/blob/main/pynecone/components/datadisplay/datatable.py

I have added the docstring.
I am trying to test locally but I getting a ReferenceError: date_picker_state is not defined. I am following the wrapping docs quite literally. Do I need to define the state separately in the components?
here is my code.
class DatePickerState(pc.State):
    date = "1/1/2001"

def index():
    return pc.center(
        pc.vstack(
            pc.heading(DatePickerState.date),
            date_picker(on_change=DatePickerState.set_date),
            pc.box("Get started by editing ",
                   pc.code(filename, font_size="1em")),
            pc.link(
                "Check out our docs!",
                href=docs_url,
                border="0.1em solid",
                padding="0.5em",
                border_radius="0.5em",
                _hover={
                    "color": "rgb(107,99,246)",
                },
            ),
            spacing="1.5em",
            font_size="2em",
        ),
        padding_top="10%",
    )

# Add state and page to the app.
app = pc.App(state=State)
app.add_page(index)
app.compile()

It looks like you're passing the wrong State class to your app.
You probably want to do
app = pc.App(state=DatePickerState)

Or if you meant to use substates, you need to make sure your new class subclasses your base state rather than pc.State:
class State(pc.State):
    """"Base State"""

class DatePickerState(State):
    date = "1/1/2001"

Going to close this pr seems inactive.


Weird color change with V's shield during combat

Describe the bug
Seemingly animation dependent shield color changes.
To Reproduce
Equip V's shield and go fight a Basilisk Knight, possibly in the same gear as in the gif.
Screenshots

I think this bug boils down to some vertices from the projectile's model exactly overlapping with some vertices on the shield for one frame, making them affect the surface normals enough to make the following piece of code add some extra brightness to the symbol on the shield: https://github.com/117HD/RLHD/blob/8ba2f6aa3f704941324c0c58d4fac5ebd0b491c0/src/main/java/rs117/hd/model/ModelPusher.java#L608-L630
Since these normals are calculated internally in RuneLite, this isn't something we can really fix currently. Plus, it may kind of fit thematically I think.


Suggestion: Interactive mode for init-branch or clone --with-branches

I have a branch structure in TFS that looks like this:

In the Source Control Explorer the folder structure on the server looks like this:

Notice that each of the three TFS branches (Main, Dev, and Release) are all under the Source folder in my TFS repository.
When I use the impressive --with-branches flag on git-tfs clone (which delegates through to the init-branch command so I assume that the behavior is the same) I get the following output:

and the following structure in my local git repository:

that is awesome.
Notice, however, that while the init-branch command generates reasonable names for my remote branch ids, they are a bit clumsy given the structure of my TFS branches.

For
Rather than
I'd prefer

trunk
master
main

branch 1
Source/Dev
dev

branch 2
Source/Release
release

so here's what I propose:

Split the fetch part of InitBranch.CloneBranch out and integrate it into the git-tfs fetch command such that a git-tfs fetch -a (or -all) will loop through the tfs remotes and fetch them all;

this leaves InitBranch responsible for creating the remotes and linking them to the appropriate changeset in the local git repo (such that a fetch or pull from that branch should complete the fetch of that TFS branch changesets as expected) so CloneBranch maybe becomes CreateBranch;

Add an -i (or -interactive) option to InitBranch (and friends) that loops through each found TFS branch, prints out the suggested branch name (as calculated today), and asks for the desired git branch name to use.

If this sounds good I'm happy to develop it; wanted to have the discussion first before investing to make sure the concept is agreeable.
Please advise.

We are trying to clean up old/stale issues. As this issue hasn't seen any updates (or progress with pull requests) in quite a while, the issue will be closed. In case further information is provided, we can revisit that and reopen the issue again.


Deleting an image affects the containers that were created from it

Distribution: Ubuntu:xenial
Distribution version: 16.04
Kernel version: 4.4.0-28
LXC version: 2.02
LXD version: 2.02
Storage backend in use: ZFS

Launch a new container from an image, delete the image and the container now appears to be 'broken'
$ lxc launch my-image andrew
$ lxc image delete my-image
$ lxc restart andrew
error: Error calling 'lxd forkstart andrew /var/lib/lxd/containers /var/log/lxd/andrew/lxc.conf': err='exit status 1'
Issue appears resolved when ZFS is remounted.
$ lxc stop andrew
$ zfs mount -a
$ lxc start andrew
$ lxc exec andrew /bin/bash
I'm a new user here so, with my limited knowledge my main concern is if containers are indeed linked to their original images and therefore should not be deleted? If someone could tell me that they are actually completely separate and isolated, that would be great.
Cheers Steven

Similar issue here.
http://askubuntu.com/questions/774097/lxd-managed-containers-on-zfs-vanish-after-deleting-a-different-one

stgraber@castiana:~/data/code/lxc/lxd (lxc/master)$ lxc launch my-image andrew
Creating andrew
Starting andrew
stgraber@castiana:~/data/code/lxc/lxd (lxc/master)$ lxc image delete my-image
stgraber@castiana:~/data/code/lxc/lxd (lxc/master)$ lxc restart andrew
stgraber@castiana:~/data/code/lxc/lxd (lxc/master)$ lxc stop andrew

That's on LXD 2.0.4. In 2.0.3 we did add logic to mount the zfs volume if it's unmounted for whatever reason, so that probably fixed this issue.
I'm going to close it based on that and my testing. If you still run into it on 2.0.4, then we'll have to get a more reliable reproducer to look into this.


fails when derivedDataPath is set on xcodebuild

i have an Xcode project that pulls private Swift packages. if i don't set a derivedDataPath then pulling the packages work. but if i do use a derivedDataPath (which i need to generate code coverage), it fails. i guess the .ssh folder is then not written in a correct place? i can't seem to find any option to change where the keys should be located. thanks.

Have you been able to resolve this?

if i'm not wrong it seems like it yeah. needed a bit of dirty stuff but ultimately it did work. see below:
    - uses<EMAIL_ADDRESS>      with:
        ssh-private-key: ${{ secrets.GHA_PRIVATE_SSHKEY }}
    - name: build, test and upload coverage
      env:
        CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
      run: |
        xcodebuild -scheme "All Tests CI" -configuration "CI Testing" -usePackageSupportBuiltinSCM -derivedDataPath $GITHUB_WORKSPACE -enableCodeCoverage YES clean build test
        cd $GITHUB_WORKSPACE/Build/ProfileData
        cd $(ls -d */|head -n 1)
        directory=${PWD##*/}
        pathCoverage=$GITHUB_WORKSPACE/Build/ProfileData/${directory}/Coverage.profdata
        cd ../../../../
        xcrun llvm-cov export -format="lcov" -instr-profile $pathCoverage "$GITHUB_WORKSPACE/Build/Products/CI Testing/kindaVim.app/Contents/MacOS/kindaVim" > info.lcov
        curl -Os https://uploader.codecov.io/latest/macos/codecov
        chmod +x codecov
        ./codecov -t $CODECOV_TOKEN

Could you please try if the setting described at https://github.com/webfactory/ssh-agent#using-deploy-keys-with-swift-package-manager works for you as well?
And what is usePackageSupportBuiltinSCM? I could not find any meaningful documentation regarding this switch.

@mpdude it has been renamed in later versions of Xcode (from xcodebuild -help):
-scmProvider   which implementation to use for Git operations (system/xcode)

Generally when running on CI, you want -scmProvider system.

oops sorry for the late answer. missed the notification somehow.
yes, @tonyarnold is right.

So, the documentation at https://github.com/webfactory/ssh-agent#using-deploy-keys-with-swift-package-manager is right and up to date and we can close this one here?

well said in my second post, i had to add a bit more stuff than what's in the docs. i haven't been able to try exactly what's in the docs after i've solved this, because i've switched my app to require Monterey minimum and GitHub Actions still don't support it. but when i'm back to it, i can try again and open an issue/update the doc if necessary. so yeah i think we can close this for now. thanks!


add bcgovr attribution footer to template files

Thoughts on wording? Trying to keep it basic. I have also opted not to include the mini bcgovr logo as I think it adds a little too much overhead to a potential project using bcgovr.

Looks great to me!
Maybe "using" instead of "by"? Definitely a good call not including the image, too much overhead and room for failure given the simplicity we're trying to achieve.

@ateucher Good suggestion. Change made.


"instance-level probability map" generation code

I'm working on your YNet architecture. Could you please share the code for instance-level probability map generation? In the recent repository, only  instance-level segmentation mask generation code is available but no instance-level probability map code.
Thanks in advance.

If you look at stage2, the models generate two outputs, one for segmentation and other for classification. From the output of classification branch, you can compute probability by first applying softmax and then pick the maximum probability value. To have instance probability map, you can create a tensor with the same size as input and then fill it with the probability that you computed earlier.
Hope this helps!

Thanks!

@monjoybme ,
hey, did you remember how to get the instance probability map?  I don't know how to fill it to a tensor

Please check the answer discussed above.

Yes, I have checked. But I don't know how to fill the tensor with the probability while the output size of classification branch just [1, 5]


Fix func and add tests

cc @bjodah. It was not a SymPy error, it was an error here.

Nice catch. So I guess sub-classing had no effect on .func.


fix: use local guild & channel

Fixes the crashing bug mentioned in #8

Wouldnt this mean that the message must be in a guild to use the class?


Size Small for Textfield

Description
Is it possible to use a sizeS for textfields? The documentation does not mention being able to apply CSS to reduce the size of the textfield, and it currently creates inconsistency with other widgets.
Screenshots

@Andres6936 You're correct: currently there is no way to use --sizeS in the TextField component. We're currently in the process of migrating our components to a new tokens system, and the updated version of TextField will support t-shirt sizing after that component is migrated.
We have a PR open for that work here: https://github.com/adobe/spectrum-css/pull/1544 - we hope to have that PR merged soon.


feat: Add numeric and date support for search and filter

Implement search functionality for numeric values
Implement search functionality for date values
Enhance ordering to handle numeric and date data types Note: Backend enhancements required for ordering by nested properties (e.g., bookNavigation.credit) and sorting by date.

@Mr-Som3a Please review this commit and make sure you choose the "approve" option before merge it.
Thank you for your attention to this matter.
Best regards,


[uma-auth] prevent styles from being inherited in uma-connect-button

In the shadow dom, styles are actually still inherited; it's just selectors that don't work,
e.g.
span {
    color: blue;
}

would not affect elements in a shadow dom.
But if, for example, text-align: center; is specified in an element containing the shadow dom element, that style is still inherited.
The general recommendation seems to be just setting all: initial; on the host element (in this case the web component)

#181  👈
develop

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @bsiaotickchong and the rest of your teammates on  Graphite

Merge activity

Oct 8, 4:59 PM EDT: @bsiaotickchong merged this pull request with Graphite.


Release 1.6.3

Modified

Fixed an issue where MAL links for manga were directing to anime links instead
Removed invite command in favour of the built-in Discord invite button

Merging anyways as ESLint issues are pre-existing to this release PR.


Content request boxes on upcoming pages

Add pages that don't have the content yet and under content write "coming soon" or have a box "What content would you like here?" Submit button

Thinking this through to build a spec:
I'm thinking of a snippet in the CMS (e.g. {{ cms::partial::shared/feedback_form:networking }}) that could be added to any page to insert a text field and submit button. The form data would then be visible on a tab in the admin panel at bizport.longbeach.gov/admin
Would this be a good approach?

@lisaratner ^^

@rossettistone sounds good!

So I think when we closed this a few days ago during the planning meeting, our reason was that we figured the "use Intercom to suggest content" method that we added on those empty pages was sufficient, and we weren't going to spend the effort to build a more complex feedback system. My bad for not putting that into the story when we closed it.
Does that reason still stand, or should we reopen this issue and discuss what work remains to be done?


fix: get nodes from indy vdr

Summary of Changes
Get a list of notes to check for firewall access from Indy VDR rather than selecting candidates from the Ledger JSON file.
Related Issues
n/a
Pull Request Checklist
Tick all boxes below to demonstrate that you have completed the respective task. If the item does not apply to your this PR check it anyway to make it apparent that there's nothing to do.

[x] All commits contain a DCO Signed-off-by line (we use the DCO GitHub app to enforce this);
[x] Updated LICENSE-3RD-PARTY.md for any added dependencies or vendored components;
[x] Updated documentation as needed for changed code and new or modified features;
[x] Added sufficient tests so that overall code coverage is not reduced.

If you have any questions to any of the points above, just submit and ask! This checklist is here to help you, not to deter you from contributing!
Pro Tip 🤓

Read our contribution guide at least once; it will save you a few review cycles!
Your PR will likely not be reviewed until all the above boxes are checked and all automated tests have passed.

PR template adapted from the Python attrs project.

This is on hold for the time being as it may not be needed.


Use tcpip connection for DAP protocol tests too

2 benefits:

It can avoid/reduce random broken pipe error:

https://github.com/ruby/debug/runs/5750847945?check_suite_focus=true
https://github.com/ruby/debug/runs/5729199865?check_suite_focus=true
https://github.com/ruby/debug/runs/5785039496?check_suite_focus=true
All of them came from DAP's socket connection.

We can unify the scenario execution logic.

Now UNIX Domain socket is default debug port to connect with VSCode so it is not acceptable.

It can avoid/reduce random broken pipe error:

It should be fixed respectively.


Point to maven repository folder for current release

Please write a description in this text box of the changes that are being
made.

Add version number variables to site documentation, used them in getting started guide.

Please ensure that you have written units tests for the changes made/features
added.

Tested by downloading https://hub.docker.com/repository/docker/sameerz/jekyll , running with command docker run --rm -it  --volume="$PWD:/srv/jekyll" -p 4000:4000 sameerz/jekyll:0.1 jekyll serve in cloned gh-pages branch.

Let me try putting the _data folder under docs to see if we can make gh_pages more aligned with our other branches.  I will also make the changes jlowe pointed out.

After discussion with @jlowe and @abellina we decided to remove variables for now.  Just changed the pointer to the accelerator and cudf jars, and adding favicon.ico (as before).

@sameerz looks like you need to upmerge your branch.

@sameerz looks like you need to upmerge your branch.

I upmerged it @revans2.

build


Formatting issue with '"'

Whenever i have the '"' literal in my code, it can compile but I get weird formatting issues
All the comments i have inline in the file freak out and comment out the next line
Here is an example. Just format this file in vs code and it will move the comment to the next line and comment out the let c:
import Text "mo:base/Text";
module {
    public func A(){
        let a = '\"';
        let b = Text.fromChar(a); // Convert to text
        let c = 1;
    }
}

If i switch the literal to '\u{22}' it works fine

This should be fixed in version 0.9.3 of the VS Code extension. Cheers!

So quick. Cheers!


Initialized the Bookstore application with components

Added:

[x] Book component that displays a single book
[x] A Navigation bar with a logo and navigation links
[x] Routing using the react-router-dom library
[x] the Books page and the Categories page
[x] Form that adds a new book
[x] Button to remove a given book
[x] Great styles

Status: Invalid 🔴
Hi @ 🙋♀,
While you made a great effort in this project, I can't review your code.
Invalid Code Review Request
You have submitted a project that has a README that is not professional. Here are key points to consider when documenting your README.

Kindly delete the live demo section if the application is not deployed. If project requirements say to deploy the project, the section should be restored and the link updated. ✖

Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers 🥂  and Happy coding!!! 👯
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Remember to tag me @KDlamini  in your question so I can receive the notification.
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

Invalid Code Review Request does not count into the code reviews limit.


#3798 No images found on explore tab

Description (required)
Fixes #3798
What changes did you make and why?

prefix with "Category:"

Tests performed (required)
Tested ProdDebug  on Nexus5x with API level 27
Screenshots (for UI changes only)

Codecov Report

Merging #3800 into master will decrease coverage by 0.00%.
The diff coverage is 0.00%.

@@             Coverage Diff             @@
##             master   #3800      +/-   ##
===========================================
- Coverage      8.50%   8.50%   -0.01%
  Complexity      366     366
===========================================
  Files           309     309
  Lines         12428   12430       +2
  Branches        994     995       +1
===========================================
  Hits           1057    1057
- Misses        11302   11304       +2
  Partials         69      69

Impacted Files
Coverage Δ
Complexity Δ

...w/commons/category/CategoryImagesListFragment.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

.../nrw/commons/category/SubCategoryListFragment.java
0.00% <ø> (ø)
0.00 <0.00> (ø)

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 b7ba1f0...3e9a74d. Read the comment docs.

fixed in https://github.com/commons-app/apps-android-commons/pull/3824


Fix incorrect logic in output resource handling

The storage handle should place outof the loop which for output resource.
With current code, the mutiple output resrouce will not work, only the first resource could be handle.

Changes

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
Describe any user facing changes here, or delete this block.

Examples of user facing changes:
- API changes
- Bug fixes
- Any changes in behavior

I'm amazed no test failed on this change, are there any that test this? Maybe one of https://github.com/tektoncd/pipeline/pull/1482 or https://github.com/tektoncd/pipeline/pull/1481 would do it?

/test pull-tekton-pipeline-integration-tests

#1630

@vincent-pli could you update the commit message to include the issue this closes #1630?

But otherwise this is great! Thanks for the fix @vincent-pli :tada: :heart:
/approve

@bobcatfish
Added, thanks


Errors about continue training using own dataset

Hi,
This is an amazing project, I am quite interested in your project.
I would like to play with the pretrained model and continue train the model using my own dataset, but I found there are some errors when I fine tune the model.
I am trying to fine tune the model using my own dataset from the checkpoint downloaded (using your link in readme.md).
I followed the guide in the readme file, processing data, and I modified the training sript:
`#!/bin/bash

while read line;do
eval "$line"
done < config.sh
while read line;do
eval "$line"
done < vocab.sh
for model training
if [ $BPE -eq 0 ]; then
DATA_BIN=linear_${MAX_POS_LEN}_chord_hardloss${IGNORE_META_LOSS}
else
DATA_BIN=linear_${MAX_POS_LEN}_chord_bpe_hardloss${IGNORE_META_LOSS}
fi
DATA_BIN_DIR=data/model_spec/${DATA_BIN}/bin
N_GPU_LOCAL=$(nvidia-smi --query-gpu=name --format=csv,noheader | wc -l)
UPDATE_FREQ=$((${BATCH_SIZE} / ${MAX_SENTENCES} / ${N_GPU_LOCAL}))
NN_ARCH=linear_transformer_multi
CHECKPOINT_SUFFIX=${DATA_BIN}_PI${PI_LEVEL}
CUDA_VISIBLE_DEVICES="0,1,2,3,4,5,6,7" PYTHONWARNINGS="ignore" fairseq-train    ${DATA_BIN_DIR}
--seed ${SEED}
--user-dir src/fairseq/linear_transformer
--task symphony_modeling --criterion multiple_loss
--save-dir ckpt/syn-taobao10w --restore-file ckpt/checkpoint_last_linear_4096_chord_bpe_hardloss1_PI2.pt
--arch ${NN_ARCH} --sample-break-mode complete_doc  --tokens-per-sample ${MAX_POS_LEN} --sample-overlap-rate ${SOR}
--optimizer adam --adam-betas '(0.9, 0.98)' --adam-eps 1e-6 --clip-norm 0.0
--lr ${PEAK_LR} --lr-scheduler polynomial_decay --warmup-updates ${WARMUP_UPDATES}  --total-num-update ${TOTAL_UPDATES}
--dropout 0.1 --weight-decay 0.01
--batch-size ${MAX_SENTENCES} --update-freq ${UPDATE_FREQ}
--max-update ${TOTAL_UPDATES} --log-format simple --log-interval 100
--checkpoint-suffix _${CHECKPOINT_SUFFIX}
--tensorboard-logdir logs/${CHECKPOINT_SUFFIX}
--ratio ${RATIO} --evt-voc-size ${SIZE_0} --dur-voc-size ${SIZE_1} --trk-voc-size ${SIZE_2} --ins-voc-size ${SIZE_3}
--max-rel-pos ${MAX_REL_POS} --max-mea-pos ${MAX_MEA_POS}  --perm-inv ${PI_LEVEL}
2>&1 | tee ${CHECKPOINT_SUFFIX}_part${RECOVER}.log`
However I got an error:

RuntimeError: Error(s) in loading state_dict for LinearTransformerMultiHeadLM:         size mismatch for decoder.wEvte.weight: copying a param with shape torch.Size([1125, 512]) from checkpoint, the shape in current model is torch.Size([176, 512]).         size mismatch for decoder.wTrke.weight: copying a param with shape torch.Size([44, 512]) from checkpoint, the shape in current model is torch.Size([17, 512]).         size mismatch for decoder.wRpe.weight: copying a param with shape torch.Size([199, 512]) from checkpoint, the shape in current model is torch.Size([71, 512]).         size mismatch for decoder.wMpe.weight: copying a param with shape torch.Size([5361, 512]) from checkpoint, the shape in current model is torch.Size([393, 512]).         size mismatch for decoder.proj_evt.weight: copying a param with shape torch.Size([1125, 512]) from checkpoint, the shape in current model is torch.Size([176, 512]).         size mismatch for decoder.proj_trk.weight: copying a param with shape torch.Size([44, 512]) from checkpoint, the shape in current model is torch.Size([17, 512]).         size mismatch for decoder.proj_ins.weight: copying a param with shape torch.Size([133, 512]) from checkpoint, the shape in current model is torch.Size([33, 512]).
I know this may because the mismatch of dictionaries. But how to use your pretrained dictionary?
May be you can update your readme.md, to write some guides of how to use the pretrained model to fine tune.
Also when I process data in the bpe step, I got this error:
Traceback (most recent call last):   File "src/preprocess/get_bpe_data.py", line 165, in <module>     subprocess.run(['./music_bpe_exec', 'learnbpe', f'{MERGE_CNT}', output_dir+'ori_voc_cnt.txt'], stdout=stdout, stderr=stderr)   File "/apdcephfs/share_1213607/yanpeishi/software/Anaconda/lib/python3.8/subprocess.py", line 493, in run     with Popen(*popenargs, **kwargs) as process:   File "/apdcephfs/share_1213607/yanpeishi/software/Anaconda/lib/python3.8/subprocess.py", line 858, in __init__     self._execute_child(args, executable, preexec_fn, close_fds,   File "/apdcephfs/share_1213607/yanpeishi/software/Anaconda/lib/python3.8/subprocess.py", line 1706, in _execute_child     raise child_exception_type(errno_num, err_msg, err_filename) PermissionError: [Errno 13] Permission denied: './music_bpe_exec'
Is there any idea about the above two questions?
Thank you very much.

Hi,
Were you able to find a solution. I am getting the same error. Thanks in advance.


Semantic Segmentation Code and pretrained weight file

Thank you for your amazing work.
Could you provide the Semantic Segmentation cod and its pretrained file plz? Thx again!

@Amshaker Thanks for your effort.
I would like to know if the backbone used for segmentation and object detection was generated using distillation loss.

Hi @helonin ,
Thanks for your interest in our work. The segmentation code and weights will be released later.

Hi @jihwanp ,
Yes, the backbones are generated with distillation loss.


projen:upgrade fails

A local yarn projen:upgrade looks like this:

Which fails in CI with this error:

That's using TypeScriptProject

Yes. That's pretty annoying. I've been seeing those too.
Any ideas?

Any ideas?

Just run npx projen@latest would be the easiest, but has drawbacks for major version changes of course
Reading the currently locked version from the lockfile (e.g. yarn list | grep projen)
Use another token (e.g. https://github.com/tibdex/github-app-token) - but that Github App would be quite an overhead

Other ideas?


WIP Allow properties to be set when run.

We have properties that we want to be configurable when we run stacks.
I think the easiest way is command line arguments, but env vars would
also work.
We also want these to be set as tags on the stack so probably want a
way to specify which properties are "tags".

LGTM


New Rule + fixer: Use a list instead of calling split with string literals

I've seen this pattern a handful of time:
"""
	itemA
	itemB
	itemC
""".split()

or
"a,b,c,d".split(",")

And I'd like a rule to transform usages of join with literals into actual inline lists without the overhead of calling "join". My two examples above would become:
[
	"itemA",
	"itemB",
	"itemC",
]

or
["a", "b", "c", "d"]

I don't think this rule exists in any linters that I'm aware of.
The exact details of how this gets formatted isn't important to this rule. Probably just rewrite everything on a single line and let formatting/other rules take care of the rest.

Great suggestion, I think it's worth adding. With autofix this adds to developer experience as writing the comma-seperated pattern is sometimes just more convenient.
Real-world examples:

https://github.com/apache/fury/blob/main/java/benchmark/analyze.py#L246
https://github.com/alibaba/AliceMind/blob/main/VECO/NLU/evaluate.py#L103
https://github.com/microsoft/DirectXShaderCompiler/blob/main/utils/hct/hctdb.py#L261
https://github.com/pandas-dev/pandas/blob/main/pandas/tests/reshape/merge/test_merge_asof.py#L61
https://github.com/numpy/numpy/blob/main/numpy/f2py/tests/test_return_real.py#L91

For posterity, @AlexWaygood noticed that this rule exists in flake8-simplify:
https://github.com/MartinThoma/flake8-simplify/issues/86 (SIM905)


Use of undeclared identifier 'M_PI' only on simulator

@matej
Hi there,
I included the MBProgressHUD .h and .m file to my source code.
It builds successfully when I use a real device but it fails when I select an iPhone simulator in Xcode with this error: Use of undeclared identifier 'M_PI'
MacOS: 10.14.6 Mojave
Xcode: 11.0
Cocoapods: 1.8.4
I also included/imported <math.h> but it failed again.

It is fixed when I upgraded to Xcode 11.3.1.


Cannot play Tween created via create

This appears to apply to v3.17 through master. You cannot play a Tween created via create. Here's a codesandbox demo that uses master branch, or some portable copy & paste code:
const tween = this.tweens.create({
  targets: {x: 0},
  x: 600,
  duration: 1000,
  onStart: () => console.log("Started!")
});
tween.play();
// Will not log started

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Thanks! Verified the fix is working in my tests.


Reset select:disabled opacity for Chrome

Fixes #33089

@mdo This only tackles the opacity mismatch in Chrome, not the select:disabled color thing. We may open another PR but this one won't be enough to close the issue.

As highlighted by @tkrotoff in #33089 comment, this should be backported to v4.

@ffoodd This now properly addresses the color and opacity.

@ffoodd Oh I'm a dummy, thanks! Wasn't even thinking that it was our doing lol.

Rebased and modified this with a new commit. Instead of removing the variable entirely, this null-ifies it. Prevents backward compatibility issues and should still fix the issue at hand.

Why keep backward compatibility ($form-select-disabled-color) since v5 is not released? Removing it now will save your team from having to deal with it the for the entire life of v5.
Less code is always better :)

Technically, we shouldn't land any further breaking changes during the beta stage :)

This was labeled as a backport, but near as I can tell, v4's .form-control class resets opacity already. And, we don't reset the color.


Websocket communication troubleshooting - Lobby

Fix settings component
Make sure JSON objects are sent/received correctly
Fix stompClient send destinations

closed with commit: 82570de


event doesn't cover all days in month view when work with momentLocalizer in some time zone

Check that this is really a bug

[X] I confirm

Reproduction link
https://codesandbox.io/s/react-big-calendar-example-forked-n4c3k7?file=/src/App.js
Bug description
Init Calendar localizer by momentLocalizer by default time zone specified as following:
moment.tz.setDefault('pacific/Fiji'); //UTC+12
var localizer = momentLocalizer(moment);

Prepare a event:
  {
    id: 1,
    title: 'Long Event',
    start: new Date("2015-04-12T08:10:00Z"),
    end: new Date("2015-04-14T08:40:00Z"),
  }

When your client is in a time zone which utc-offset is less than pacific/Fiji utc-offset, I am working on UTC+8 , this event will only display on 4/12, 4/13, not cover 4/14, the event on pacific/Fiji local time should be 4/12/2015 20:10 - 4/14/2015 20:40.  Seems momentLoalizer/browserTZOffset make an incorrect compensation.
Expected Behavior
No response
Actual Behavior
No response
react-big-calendar version
1.8.1
React version
17.0.2
Platform/Target and Browser Versions
windows 11 edge
Validations

[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.
[X] Make sure this is a react-big-calendar issue and not an implementation issue

Would you like to open a PR for this bug?

[ ] I'm willing to open a PR

still no answer?


java release notes for the 2023-03 release

This is an automated pull request to gather the java release notes for the 2023-03 release. See Producing Release Notes for details of the processing.

@weshaggard This PR was failing due to a broken C++ link to the Key Vault Administration package (for which we stopped a release). Should I revert the removal of the package in this commit and instead just merge main into the branch?


Matt needs to add a header onto img_processor.py

Check out what he added here: a559038
We don't want another merge issue lol

Not sure why it caused an issue though, since i'm doing everything on my own branch

@MattGuptil so you want that data:image/base64; whatever thing in the base64 string?


wincmd H/J/K/L doesn't respect 'winfixwidth' and 'winfixheight'

Tested in 8.0.0344 and 7.4.1689.
For the problem with winfixheight, there has to already be two vertical windows.  This is not an issue if there are only only horizontally stacked windows.
:vs
:split | resize 10 | set winfixheight | wincmd J
:split | resize 10 | set winfixheight | wincmd J

Screnshot: https://share.esdf.io/EWMaajBW9I/
In the case of winfixwidth, there are no prerequisites:
:vs | vertical resize 20 | set winfixwidth | wincmd L

The first time the above commands are run, the windows are equal widths.  Repeating it creates smaller windows to the far right, but never the width I expected until there isn't enough room to spread them out.
Screenshot (after three runs): https://share.esdf.io/y9erLk1KaI/

I think #931 may be related.


[Feature request] Inlining wasm binary

For some Node.js runtime environment such as AWS Lambda, it would be nice to have a pure JS implementation without extra file access like a wasm file because some bundling process doesn't recognize such extra files automatically.
Could you provide another package like re2-wasm-inline by inlining the wasm binary as a Buffer so that the extra wasm file isn't required?
Or, if your licensing term allows, I can also create such a package and publish it to npmjs on behalf.
Let me know your opinion!
See https://github.com/awslabs/smithy-typescript/issues/733
This could also solve https://github.com/google/re2-wasm/issues/15

Let me craft a PoC package.

This simple script worked:
const fs = require("fs");

fs.rmSync("build", { force: true, recursive: true });
fs.cpSync("node_modules/re2-wasm/build", "build", { recursive: true });

const wasm = fs.readFileSync("build/wasm/re2.wasm").toString("base64");
const js = fs.readFileSync("build/wasm/re2.js", { encoding: "utf8" });

fs.writeFileSync(
  "build/wasm/re2.js",
  `
var Module = {
  wasmBinary: Buffer.from("${wasm}", "base64"),
}
${js}
`
);

fs.rmSync("build/wasm/re2.wasm");


NIFI-4217: Retain original DDL in CaptureChangeMySQL

The DDL contents were being "normalized" to check for certain keywords like "alter table". However this normalized version was being passed on, instead of the original DDL.
For all changes:

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

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

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

[x] Is your initial contribution a single, squashed commit?

For code changes:

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

For documentation related changes:

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

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

Reviewing...

+1, code LGTM, build OK, merging to master, thanks @mattyb149 !


Stop passing down template references

Now that we can use require, there's no need to load all the templates in dashboard.js and pass them down. Instead, we should require them in the module that they're needed in.
Follow up to #873

I think this is already done?

Oops, yes, this was fixed in https://github.com/BuoyantIO/linkerd/pull/889


Update installation instructions

Resolves: https://jira.duraspace.org/browse/FCREPO-2346

@dannylamb @bseeger let me know if you think these changes to the installation instructions are suitably clear.

Defnitely not a blocker here, but maybe you want the badges to be at the very top of the README?  https://github.com/fcrepo4-exts/fcrepo-camel-toolbox/pull/122/files#diff-04c6e90faac2675aa89e2176d2eec7d8R7

@dannylamb w/r/t the badges, do you mean put the badges above the title "Fedora Messaging Application Toolbox"? at present, they're just under brief description, which seems like a pretty good place for them.

If you like where they are, then that's where they should be.  Just making sure they're not there by accident.

These changes look good to me.  I've no opinion on the badge location other then to say I never really paid attention to them before and didn't know what you were referring to when you referenced the Maven Central badge (not that it was hard to figure out).  Either I'm now in the loop that everyone else is in, or others might be confused as well. Not sure which is true for most folks.

@acoburn @bseeger It feels silly to wait for Travis on a README pull, but I'll merge once Travis turns green.  :+1:

I'd say that a significant number of people who may want to use this code won't know what "Maven Central" is, and yet if we refer to the releases page on github, there's nothing to download (other than source code that would need to be compiled -- which is certainly no better). I think the balance I was trying to strike was this -- if you are familiar with the typical Java build/dependency infrastructure, you'll know what's being described, and if you're not, you can just look at the specific commands. In my mind, it's kind of like making reference to OSGi -- that really isn't going to mean anything to most people, and that's probably a good thing :-) But if you do know what OSGi is all about, you would probably want to know. I also see the README as a constant work in progress, and we should keep working at making it clearer (without being too verbose).

@acoburn It's tricky when you're building on top of technologies that go deep like OSGi and Karaf.  You can't be on the hook for a full tutorial on them, but you at least need to give them a nod.


[MM-25264] [MM-25265] Create and apply filter component to user grids

Summary

Adds the newly created Filter component to the admin console

Ticket Link

https://mattermost.atlassian.net/browse/MM-25264
https://mattermost.atlassian.net/browse/MM-25265

Related Pull Requests

https://github.com/mattermost/mattermost-redux/pull/1190

Screenshots

@michaelgamble you can login with the system admin credentials listed above and view the filter component on the team management page (https://mattermost-webapp-pr-5882.test.mattermost.cloud/admin_console/user_management/teams/kxhoegfh4jbuxpozodfrojfrfy), unfortunately you wont be able to test functionality (only the visuals of the component itself since the server branch isnt being picked up for some reason)

@hahmadia @mkraft Kind note for reviewers that feature complete for v5.26 is this week Friday July 17th. Let me know any concerns,

@srkgupta This is to be reviewed with https://github.com/mattermost/mattermost-server/pull/14998 & https://github.com/mattermost/mattermost-redux/pull/1190

The last two issues are actually stories that are to be implemented. They will be addressed later.
https://mattermost.atlassian.net/browse/MM-26969
https://mattermost.atlassian.net/browse/MM-26970

@srkgupta the issue related to guest access is now resolved


suggestion: add per game config option

Is your feature request related to a problem? Please describe.
Some games ( all DOA games for example ) require changes to the xenia config file which would negatively impact other games if set permanently in the default config file.
Describe the solution you'd like
Depending on how xenia manager accesses xenia this could be done in 2 ways:
either add an option to just create a custom config ( copy of the default config.toml file ) under config/titleid.config.toml or if the way xenia is accessed is through cli, ceate the file but also add --config titleid.config.toml to the parameters ( + path )
Additional context
Per game config would simplify settings a lot

This is already implemented. In Xenia Settings, "Default Profile" is only used to create new config files for every new game, nothing else. You can click on it and change to whatever game you want to change something.

This is already implemented. In Xenia Settings, "Default Profile" is only used to create new config files for every new game, nothing else. You can click on it and change to whatever game you want to change something.

regarding different versions of xenia, can you implement this as it was with the config when each game has its own config file

regarding different versions of xenia, you can implement this as it was with the config when each game has its own config file

Don't think I understand what you meant.

regarding different versions of xenia, you can implement this as it was with the config when each game has its own config file

Don't think I understand what you meant.

you have game settings for each game you can also make each game have its own version of the emulator

I understand, but the whole point of this program is to keep everything up to date.

Thank you for the feedback, I confirm the configs get created.
I missed that
The topic can be closed as it's already implemented

I understand, but the whole point of this program is to keep everything up to date.

some games on xenia canary needs different build


Feature/regexp policy matcher

Addresses directly this issue.
Reworked from prefix matching to regexp matching, while trying to preserve the current behavior.
Our motivation is due to Metronome prefixing task_name with a unique id, hence breaking the simple prefix matching.
2019-08-28: Run full tests and all pass.

Some thoughts/considerations:

By trying to make existing syntax work the "rules" as to what to put where become rather loose

E.g:
"mesos": {
  "regexp": "mesos:framework:\\.*",
  ...
}

Is equivalent to:
"mesos:framework:*": {
  ...
}

Is equivalent to:
"mesos:*": {
  "regexp": "framework:\\.*",
  ...
}

Can't honestly say whether this is a feature or a bug, but generally would lean that if we want to enforce one set of rules then no wildcards at all at the key level - either a an exact matching path and no regexp defined, or some placeholder key e.g. <re> and then regexp must be defined (but that then defeats the radix tree...)...

Previously the * was in fact a prefix-matching. Currently there is no enforcement of that, but at least adding this would be trivial (regexp.Compile("^" + v.Regexp)).

Of course this in current state would make the rules even more "non-intuitive".

Thanks for the contribution! When I first saw #76 I was a bit perplexed on how I would design this feature. I think your approach is a bit more powerful, but also more "optional" and has resulted in a cleaner design than what I was thinking.

Can't honestly say whether this is a feature or a bug, but generally would lean that if we want to enforce one set of rules then no wildcards at all at the key level - either a an exact matching path and no regexp defined, or some placeholder key e.g.  and then regexp must be defined (but that then defeats the radix tree...)...

I thought about this, while I don't like the fact that there are multiple ways to specify a rule and I prefer prefix matching, I understand that the regex matching is necessary and that we should prefer one way of doing things. However, to your point about leaning towards regex, I would argue the other way. Introducing regex also means introducing a couple more footguns; an improper regex can mean you accidentally make a policy too broad. If someone wants to be conservative, it's easier to do that with prefix matching.
I prefer how you've currently implemented things - use prefix matching where appropriate (which I believe is most cases), and dropdown to regex if you need something more powerful and opt into the footguns. If your problem isn't solved by prefix-matching, then falldown into regex - hopefully you don't need to, but if you do it's there and if you don't there's a more straightforward, less powerful to accomplish a more general task.

Of course this in current state would make the rules even more "non-intuitive".

Maybe at first. But after you do a few, then it's straightforward.

I thought about this, while I don't like the fact that there are multiple ways to specify a rule (...) and that we should prefer one way of doing things.

I definitely see this concerns as a feature. You can achieve the same outcome in multiple ways, so you can choose the one that suits your case the most.

I understand that the regex matching is necessary

Definitely. In addition to #76 I already have a few other use cases that require either wildcard/glob inside the rule or regular expression to work, like giving a set of policies to all services inside a group.

an improper regex can mean you accidentally make a policy too broad. If someone wants to be conservative, it's easier to do that with prefix matching.

I think you shouldn't be too protective for the users. It's they decision on what and how they want to use. Vault policies could be abused on their own - one can just allow anything and then just match mesos:* in Gatekeeper 🤷♂

@nemosupremo Well put argument for "explicit path match, then wildcard, and only then if really needed use a regexp". Thought it over and it is indeed saner than "explicit path match or regexp". So :+1: on this point.
With the above said I don't see any straightforward way to "enforce" "either this way or that way", so I'm personally OK with "you can do the same in (at least) three ways, if you wish".
I was a bit surprised that you've already merged :) I still see as outstanding:

Should we enforce the prefix-matching behavior? By always prefixing v.Regexp with ^? I don't have enough experience to tell if this may be a problem or not (somewhere down the line...).
The test case I did was copy&paste, there could be more and definitely cleaner.
Didn't touch the documentation.

I think I should be able to find time to do a PR for 1 and/or 2 if there is a consensus. As from the POV of our business needs the current state is already good enough though.


Add additional columns to inference output

See #507

(Let me know when it's ready to merge.)

Should be good to merge.