Re-add Statistics Panel in Web Version

Is your feature request related to a problem? If so, Please describe.
The statistics panel is useful for:

People to find if a category of interest that they're interested in is already in the system somewhere
1b) If so where it is
Finding out total counts of annotation per different categories
Useful for advertisement purposes

Describe the solution you'd like
I'd imagine there's several possible levels of progression and different features related to this.

As a first step, making it similar to what it was previously
Also not making it cover the global (non-user) training folder, but any dataset in user's public folders as well + anything globally shared
Adding in a synonym table that can be modified by admins (fixed initially)

And more longer term things I would see as not that import short term

User-specific stats panel based on what data they have access too
User uploaded synonym tables, improved specification

Old UI was kinda bad.  I was planning to replace it with a v-data-table just because it's easy.  Possibly using the expansion feature to show the associated datasets: https://vuetifyjs.com/en/components/data-tables/#expandable-rows
The table would be like this, and then you expand the fish row and get links to all 10 of the datasets with fish.
| Type | Number of datasets | Number of annotations |
| Fish | 10 | 3928 |

@mattdawkins, let us know if you have any objections to this. We're planning to go ahead with it since it's a simple and solid way of readding this feature which can be modified/expanded in the future if needed.

We should probably not do this.

One of the point of this to find if anyone is annotating similar categories on other data though. Searching just "published" data doesn't satisfy that (which isn't our responsibility to review everyone's data, and the term "published" is overloaded here as some people could think that means in research publications so I would advise against using that term at a minimum).


Update contribute calling commands page

Search first

[X] I searched and no similar issues were found

Description
I think it would be nice to update "Calling Commands" page as its description does not contain that many details and might not be very helpful for contributors.  It would be nice if we could explain the different components required in the new command frameworks or which things we need to take into account when performing a command call or when adding a new command to the framework.
Steps To Reproduce
N/A
Expected/Desired Behavior
Update "Calling Commands" page
Liquibase Version
No response
Database Vendor & Version
No response
Liquibase Integration
No response
Liquibase Extensions
No response
OS and/or Infrastructure Type/Provider
No response
Additional Context
No response
Are you willing to submit a PR?

[ ] I'm willing to submit a PR (Thank you!)

@kevin-atx maybe we can add this doc ticket also for the next sprint. What do you think?


Area resizing in GeneralizedRCNNTransform

Hello,
While working with the detection models released in 0.3, I noticed that in GeneralizedRCNNTransform.py, while the image, bounding box coordinates, mask and keypoints are resized accordingly, the area field of the target dictionary is not resized. Is there any reason for not doing it?
As far as I understand, not resizing the area while have an effect on the coco metrics.
Resizing the area could be done using the resized bounding box coordinates
https://github.com/pytorch/vision/blob/05ba3f53d1a40f497d4af4768428b7fb1a8dd550/torchvision/models/detection/transform.py#L75
        if "area" in target:
            target["area"] = (bbox[:, 3] - bbox[:, 1]) * (bbox[:, 2] - bbox[:, 0])

@juanmed great question!
The COCO evaluation takes the area into account in order to perform the small / medium / large separation. If you scale the area, this will affect the results of the metrics in an unwanted way (you want to evaluate on the original image size).
But this doesn't have any effect I believe, because we do not use the area inside the model, and we rescale the images to the original image size in the end of forward.

@fmassa Thanks for your explanation :) I understand then that resizing the area field is unnecessary, and adding would otherwise require to resize during postprocessing as well which seems unnecessary overhead.
I will close this issue. Thanks!


Cannot create security advisory

I want to create a bug-report/PR for a security issue but it seems I'm not allowed to create security advisories.
The fix is one line so I can email it if that is easier.

You could just create a PR?

That makes it public. Not good practice for security issues. Probably not a
big deal here though.
On Thu, 22 Oct 2020, 12:16 Max Williams<EMAIL_ADDRESS>wrote:

You could just create a PR?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/locustio/locust/issues/1602#issuecomment-714390502,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMCZSIWKYFHTTNPGA54ORLSMABBVANCNFSM4S27LLXQ
.

Probably not a big deal, but you can send a message https://locustio.slack.com/ if you want.

because all the code is public, everyone will be aware of the fix as soon as it is commited anyway, so a PR would be good enough

I think you need to invite me?
Best regards / Venlig Hilsen
Lars Hupfeldt Nielsen
Hupfeldt IT
Phone: +45 2060 3546
Den tor. 22. okt. 2020 kl. 12.49 skrev Lars Holmberg <
<EMAIL_ADDRESS>
Probably not a big deal, but you can send a message
https://locustio.slack.com/ if you want.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/locustio/locust/issues/1602#issuecomment-714408715,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMCZSLGHFXMRFVEZIXBEW3SMAE4ZANCNFSM4S27LLXQ
.

I think the idea of keeping it private is that you do not merge the fix until you are ready to release. But I will create a PR.

If it is critical, I can make a release right away

I didnt find a way to invite you, but no invitation should be necessary...

I don't think it is critical. But if you are ready to release, then I would personally appreciate it, our security department requires this to be fixed.

PR created
I have not attempted to unescape the use of host value in any places. I do not think html codes will be valid in any interpretation of the host value.

btw. I do not see any way to create an account on the slack server.

maybe you need to go here first https://slack.com/get-started#/find


Get-MailboxJunkEmailConfiguration Prefixes Error

When the following conditions are met:

you connect to Exchange Online via PowerShell as an Admin
you import cmdlets with prefixes using Import-PSSession
you run Get-MailboxJunkEmailConfiguration against some other mailbox

You get the following error:

Error on proxy command 'Get-MailboxJunkEmailConfiguration<EMAIL_ADDRESS>to server
DM6PR14MB2460.namprd14.prod.outlook.com: Server version 15.20.0841.0000, Proxy method RPS:
The WinRM client cannot process the request. The connection string should be of the form
[://][:][/] where transport is one of "http" or "https". Transport, port and suffix are
optional. The host may be a hostname or an IP address. For IPv6 addresses, enclose the address in brackets - e.g.
"http://[1::2]:80/wsman". Change the connection string and try the request again.
[Server=BN7PR14MB2209,RequestId=23756254-7e1d-47a7-9c55-fb19832416ad,TimeStamp=6/13/2018 12:45:51 PM] .
+ CategoryInfo          : NotSpecified: (:) [Get-MailboxJunkEmailConfiguration], CmdletProxyException
+ FullyQualifiedErrorId : Microsoft.Exchange.Configuration.CmdletProxyException,Microsoft.Exchange.Management.Stor
eTasks.GetMailboxJunkEmailConfiguration
+ PSComputerName        : ps.outlook.com

If you run the same cmdlet Get-MailboxJunkEmailConfiguration against your own mailbox, everything works just fine.
Please kindly advise.

@YuriySamorodov, at the risk of being too basic, you're connecting using the official Exchange Online PowerShell connection instructions here? I connected to an E3 organization and ran Get-MailboxJunkEmailConfiguration -Identity <SomeOtherMailbox> and I received results and no errors (there was quite a long pause, however).
And I presume your computer meets all of the prerequisites as described in the Connection topic?
There were reports of PowerShell connection issues back in December (the error was different "Server Error in '/PowerShell-LiveID' Application. Runtime Error") but that was fixed by January.
Is that the only cmdlet that's giving you errors?

@YuriySamorodov, I didn't pick up on the fact that you were using prefixes. I connected again using prefixes on the session ran the command again, and it still worked (Get-abcMailboxJunkEmailConfiguration -Identity <SomeOtherMailbox>). If you're using prefixes, are you connecting to multiple PowerShell environments at the same time? If so, what are they, and if you connect only to Exchange Online PowerShell, does the command work?

@chrisda
Hello Chris! Thank you for the heads up. Indeed I am using my own script to connect to Office365. You may want to take a look:
https://github.com/YuriySamorodov/Misc/blob/master/New-Office365Session.ps1
I dug a little bit further and noticed the following in the error message:

Proxy method RPS:
The WinRM client cannot process the request.

In fact I have implemented "ProxyMethod" parameter earlier this month to overcome an issue where you would not be able to set user photo while connected with PSWS. It looks like that that I faced an issue like this: https://support.microsoft.com/en-us/help/3067263/remote-powershell-cmdlet-fails-in-an-exchange-server-2013-environment

This issue occurs because the access token of the current Exchange administrator is so large that it exceeds the connection string length limitation in the Windows Remote Management (WinRM) component. The connection string length limitation is hard-coded to 2,048 bytes.

I guess I have to create a PR make a note somewhere in the article:
https://docs.microsoft.com/en-us/powershell/module/exchange/antispam-antimalware/get-mailboxjunkemailconfiguration?view=exchange-ps
However, should get-mailboxjunkemailconfiguration be working via PRS?

@YuriySamorodov, yes definitely. All of the Exchange workloads are based on remote PowerShell (it's the only way to connect to cloud-based services or on-premises servers), so all cmdlets are expected to work.
We have a topic that describes how to connect to all Office 365 services from a single Windows PowerShell window: Connect to all Office 365 services in a single Windows PowerShell window. Perhaps you can use the information in your script?


Blank screen + "webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing" on logs

Describe the bug
All of a sudden the application will just display a blank screen and the following warning on the logs:
webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.

On the console, I can tell that the app is performing an initial API call successfully.
I did look at #9300, but I'm not sure if they were experiencing the same issue.
Reproduction
I assume the only way to reproduce is to clone https://github.com/dezoito/ollama-grid-search into a Ubuntu 20.04 machine and trying to run it from there.
Expected behavior
The window should display the application as expected, or at least an error message stating why it can't be rendered
Full tauri info output
[✔] Environment
    - OS: Linux Mint 21.1 X64
    ✔ webkit2gtk-4.0: 2.44.0
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.78.0 (9b00956e5 2024-04-29)
    ✔ cargo: 1.78.0 (54d8815d0 2024-03-26)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 18.19.1
    - yarn: 1.22.22
    - npm: 10.2.4
    - bun: 1.0.2

[-] Packages
    - tauri [RUST]: 1.6.5
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.7
    - tao [RUST]: 0.16.7
    - @tauri-apps/api [NPM]: 1.5.5
    - @tauri-apps/cli [NPM]: 1.5.13

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
Finished dev [unoptimized + debuginfo] target(s) in 20.37s

** (ollama-grid-search:29842): WARNING **: 10:55:42.496: webkit_settings_set_enable_offline_web_application_cache is deprecated and does nothing.
Fetching models from http://localhost
Fetching ollama version from http://localhost:11434/api/version
[src/commands.rs:55] &response = Response {
    url: Url {
        scheme: "http",
        cannot_be_a_base: false,
        username: "",
        password: None,
        host: Some(
            Domain(
                "localhost",
            ),
        ),
        port: Some(
            11434,
        ),
        path: "/api/version",
        query: None,
        fragment: None,
    },
    status: 200,
    headers: {
        "content-type": "application/json; charset=utf-8",
        "date": "Sat, 11 May 2024 13:55:44 GMT",
        "content-length": "20",
    },
}

Additional context
No response

The warning message has nothing to do with the blank screen.
Can you try running it with the WEBKIT_DISABLE_COMPOSITING_MODE=1 or WEBKIT_DISABLE_DMABUF_RENDERER env vars?
WEBKIT_DISABLE_COMPOSITING_MODE=1 did the trick.
I know nothing about webkit and presumed the warning had something to do with the issue because it's not present in a different Linux machine where it works.
If you have the time, would you mind briefly commenting on how that fixes the problem?
Thank you.

WEBKIT_DISABLE_COMPOSITING_MODE=1 seems to do the trick fopr me.
After a freshly intiated project using tauri+solidJs on OpenSuse Tumbleweed. I was getting a blank screen (dark) from the app and message "eglExportDMABUFImageMESA failed" on the command line.


android 21, cannot resolve some class

hi , i
android 21 has some issue

cannot resolve import android.telephony.SubscriptionInfo;

cannot resolve construcot arraSet .....

thks

Please try with the latest version of hidden api, and let's see what happens?


Add Dark Theme toggle

I want to add a toggle to swap the website to a dark theme. There could also be an option to match the system theme too

@gmelodie can we start working on it?

Yes absolutely!

Done. Waiting for code review.


Write features tests for DeleteCourse and Reservation Pages

Writing tests for pages
I added the following changes in this branch:

Added tests for the following pages:

Delete Course Page
Reservation Page

Run npm test to test the frontend components
Feature Tests

Hi @tanveerisonline, all the tests are passing on my side. Would you please provide more information on the snapshot error you are facing?

Hi @tobuya
The attachments are the details of the error kindly check them and fix them thanks.


Add quick example usage to the readme

It would be nice to have a short section in the README that showed  a very basic example of how to use the buildpack. Just the basic pack command and the dependencies so this language family buildpack could be promoted to the python community without folks having to read a lot of other docs.

@andymoe Hopefully soon https://github.com/paketo-buildpacks/rfcs/pull/91 will pass and we can publish docs on the paketo website and samples in the samples repo

I added a link to the docs from the README - see https://github.com/paketo-buildpacks/python/pull/410
@andymoe does that work for you? It's consistent with other buildpack READMEs - adding a link without duplicating usage in the README.

I'll close this now that #410 is merged. Feel free to re-open if you don't think this is sufficient.


Cleaned up the App-Bar

PR Fixes:

1 Made the app bar cleaner by adding a Toggle Options

Resolves #[Issue Number if there]
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I assure there is no similar/duplicate pull request regarding same issue

Hey this has been fixed in #309

Please get rid of pnpm lock file

Ok on it

Please get rid of pnpm lock file
here is the fixed version
https://github.com/code100x/cms/pull/446#issue-2247005279


i18n(es): Update astro-components.md, layouts.md and astro-pages.md

What kind of changes does this PR include?

New or updated content

Description

update astro-components.md to match with latest changes in #787
update layouts.md to match with latest changes in #917
update astro-pages.md to match with latest changes in #895

LGTM! ✅ Fantastic work!

Thanks @kevinzunigacuellar and @agustinmulet, great work!! The Spanish team is on fire!! 🚀


Artifactory Tools Installer Task 1.10.3 throws error, 1.10.2 does not

Describe the bug
Ran my pipeline twice today, now throws error Error: Cannot find module 'azure-pipelines-task-lib/task'
To Reproduce
Run Artifactory Tools Installer Task
Expected behavior
No errors thrown, same as 1.10.2
Screenshots
Error (1.10.3):

Working (1.10.2)

Source:

Versions

Artifactory Azure DevOps extension version: 1.10.3
Agent operating system: Windows 10
JFrog Artifactory version: 6.18.1

Additional context
Working timestamp: 2020-09-30T09:05:16 UTC+2
Error timestamp: 2020-09-30T16:08:17 UTC+2

I could see the same happening with 1.10.4 as well.

I could see the same happening with 1.10.4 as well.

I pinned it to 1.10.2 as we're in the middle of getting a release out, atleast until it's confirmed to be resolved

How do you pin it in Azure Dev Ops?

We are getting this error over and over in our builds.

@Thacai and @AceHack,
We're working on resolving this issue ASAP.
We'll send out an update soon.

FYI, make sure you guys are running npm install before publishing your task.
https://github.com/microsoft/azure-pipelines-task-lib/issues/485

yaml you can pin it like:- task<EMAIL_ADDRESS>Can't remember if you can pin the minor/patch version on classic pipelines

How do you pin it in Azure Dev Ops?

This is happening for me in ArtifactoryGenericUpload@2
What should I pin that to?

Where can I find these version numbers

I just found the previous version by looking at the previous pipeline output:

Only in Yaml you can pin it. But in UI you cant

Version 1.10.5 was now released and the issue was fixed.
Please refresh or reinstall the extension if it doesn't automatically update.
We are incredibly sorry about the inconvenience caused by this issue.

Thanks you all for sharing this information.
I've just added a comment in https://github.com/jfrog/artifactory-azure-devops-extension/issues/207 summarising the issue. If needed, let's continue the discussion there.


#1472 remove adding unnecessary advanced filter specification even if doing nothing

Description
I didn't set an advanced filter but I found unnecessary advanced filter specification when saving configuration spec.
Related Issue : #1472

How Has This Been Tested?

Go to 'Dashbard' and Chart widget.
add the filter edit view on widget using "+" on filter panel
select any filter and crate any chart.
turn on developer tools and move the network tab
Save widget and you can see "/api/widgets" response

Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My code follows the code style of this project. it will be added soon
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document. it will be added soon
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Additional Context

run build
deploy to 3


Build with 'generateBundle' throws exception

What I ran:
./gradlew generateBundle
Result:

FAILURE: Build failed with an exception.

* What went wrong:
Could not initialize class org.codehaus.groovy.runtime.InvokerHelper

Hi @swiftech , can you tell me which version of Java you're using and which OS you're seeing this on?

@defano
oracle jdk-17.0.1
macOS Catalina version 10.15.7

Hi @swiftech , unfortunately WyldCard only supports Java 8 at this time. There are quite a few changes required to support Java 17 (mostly related to Google Guice) which I have not had time to implement.
You can run the program by using an older version of Java. I recommend utilizing SDKMan, then:
$ sdk install java 8.0.292.hs-adpt
$ sdk use java 8.0.292.hs-adpt
$ gradlew clean
$ gradlew run


fix(cache) don't use nightly build cache accidentally

the Kong container cache uses the sha of the kong source code. This means that when we set a non standard KONG_VERSION we accidentally use proper released Kong vs daily Kong or vice-versa

:tada: This PR is included in version 2.2.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Update live-unit-testing-faq.md

Update minimum supported version for the NUnit adapter

@drognanar : Thanks for your contribution! The author, @rpetrusha, has been notified to review your proposed change.

#sign-off


Update NIST inlined license text

This completes the update started in PR 118, 90f5c8c.
I intend to merge this after CI passes.


build: Use standard upgrade-python-requirements file

The upgrade-python-requirements file in this repo is outdated; it should use the standard template defined in the .github repo, under workflow-templates directory.
Note I have tried to replace the '$default-branch' variable with the (unquoted) name of this repo's master branch; if that did not happen correctly, do not merge this branch until it is fixed.

@e0d I don't know why it's failing; closing and re-opening PR should trigger a rerun of all the builds but it didn't.
Looking at this, it seems that maybe the coverage is buggy? https://app.codecov.io/gh/openedx/xblock-sdk/pulls
It says that the previous builds - which have the same or less coverage than mine - cause no change to coverage:

The file it says I decreased coverage on is sample_xblocks/filethumbs/filethumbs.py

It passes here: https://github.com/openedx/xblock-sdk/pull/243
Closing this one.

Oh - nope - it doesn't pass. Had all the green checks then not. I don't know.

I notice it's not actually comparing to the latest commit on master as well


Additional information on Evaluate

Is your feature request related to a problem? Please describe.
When evaluate runs, and fails, only the control IDs are output. More information would be helpful for debugging what actually failed, since the control satisfaction is often a function of many observations.
Describe the solution you'd like

Given assessment-results
When lula evaluate fails
Then list observation changes

Additional context
Thinking a decent solution would be:

Identify old -> new observation pairs by the observation.description text matching. Print out those with mis-matched relevant-evidence.description values (i.e., the result: not-satisfied/satisfied)
For any new observations that are not-satisfied without a previous old observation, print those.

This is just my idea for evaluate, but perhaps this rolls into a larger function to interrogate the assessment results more granularly and specific to individual controls.

From a user looking at lula evaluate output in CI, this would be super helpful to either expand the default information or provide a debug/verbose mode. For reference my current process to understand a failing evaluation is:

Get a list of control IDs from the CI/command output
Download the assessment results (in our case they are in CI artifacts)
For each control ID listed as not-satisfied, check the results to get a list of related-observations (worth noting at this point I only see that the control was not-satisfied, not necessarily which observations/evidence were not satisfied)
For each observation-uuid check the relevant-evidence to see if it was satisfied or not-satisfied
If not-satisfied, review the remarks

If lula evaluate output the specific not-satisfied observations, or even further the associated remarks that would hugely simplify this process.

@mjnagel - thanks for the feedback! Yeah agreed this process is not great and is like trying to untangle a spaghetti of uuids. The draft PR I'm working has the output listing all different observations and all new or missing ones for each failed control:

From a user perspective, if you have thoughts on how to make this more informative, cleaner, whatever lmk! Just trying to get the information in there as a first cut at solving this traceability problem.

Yeah I think that's a super helpful start. Two things that I would find useful:

Ability to filter out any observations that were satisfied - maybe not by default but if I could reduce the noise to just focus on what failed that would be great so that I don't have to read through all the observations (maybe I'm just misunderstanding the above screenshot and this is already true - I think the first observation block with satisfied is throwing me off).
Not really sure how to do this but if there were an easy way to link back/provide the details of the validation check that was used (i.e. the actual opa check) that could be helpful. This might just be (1) me getting used to the format and remembering that the UUID in the description test is the UUID in the oscal and (2) a bit of a short term issue as the validations are still maturing.

This looks great though and is exactly what I was hoping to see!

Yep, this is supposed to just show the ones that changed, that formatting is probably confusing - but the first in the list is like the old version (where it was passing + the "evidence" and the second is it's pair that is now failing - I feel like I could probably rearrange this to make it more obvious that's what's happening.
On the validation part, are you thinking you'd like to see the rego? and/or the input data? We have some other issues open to add like "human friendly" readme + composing that in the OSCAL, but that's something we would still need to implement but could possibly add the raw rego though...

Yep, this is supposed to just show the ones that changed, that formatting is probably confusing - but the first in the list is like the old version (where it was passing + the "evidence" and the second is it's pair that is now failing - I feel like I could probably rearrange this to make it more obvious that's what's happening.

Gotcha, maybe my examples are limited but I'm thinking most of the time I'd only care about the new evidence section, not necessarily seeing the "passing" version?

On the validation part, are you thinking you'd like to see the rego? and/or the input data? We have some other issues open to add like "human friendly" readme + composing that in the OSCAL, but that's something we would still need to implement but could possibly add the raw rego though...

I think the rego could be useful, but probably should should be part of a verbose mode flag or something like that since it could be a lot to log out by default. It's mostly just in the line of thinking "well this failed, I see the validation error message, but was that because the check needs an update?"
A good example related to your screenshotted validation - if we switched from our current sidecar implementation to a "native sidecar" implementation I'd expect that to fail the validation. The message would just say "Istio sidecar proxy not found..." but in reality the rego check is really the "problem"/thing that needs to be reviewed.


Android dead/killed app not receiving any notification, and in foreground/background banner now show

Helo, im moving from React Native Push Notification to this package because there is a lot of issue on that package.
i have several question here :

How to show the banner of notification on Android (Not Testing on IOS) ? since we can customize the layout but still i cannot understand how to implement this one https://github.com/wix/react-native-notifications/wiki/Android:-Layout-Customization

In dead/killed states, im not receiving any notirifcation until i open the application it self. how can i manage this ?

Code :
class App extends Component {
    constructor(props) {
      super(props);
      this.state = {};
      this.pushNotificationListener();

      //Testing Local Push Notification but still NO BANNER appear
      Notifications.postLocalNotification({
          body: "Local notification!",
          title: "Local Notification Title",
          sound: "chime.aiff",
          silent: false,
          category: "SOME_CATEGORY",
          userInfo: { }
      });
    }

    pushNotificationListener = async () => {
      Notifications.getInitialNotification()
      .then((notification) => {
        console.log("Initial notification was:", (notification ? notification.payload : 'N/A'));
        })
      .catch((err) => console.error("getInitialNotifiation() failed", err));

      Notifications.registerRemoteNotifications();

      Notifications.events().registerRemoteNotificationsRegistered((event: Registered) => {
          // TODO: Send the token to my server so it could send back push notifications...
          console.log("Device Token Received", event.deviceToken);
      });
      Notifications.events().registerRemoteNotificationsRegistrationFailed((event: RegistrationError) => {
          console.error(event);
      });

      Notifications.events().registerNotificationReceivedForeground((notification: Notification, completion) => {
        console.log(`Notification received in foreground: ${notification}`);

        completion({alert: true, sound: true, badge: true});
      });

      Notifications.events().registerNotificationOpened((notification: Notification, completion) => {
        console.log(`Notification opened: ${notification.payload}`);
        completion();
      });

      Notifications.events().registerNotificationReceivedBackground((notification: Notification, completion: (response: NotificationCompletion) => void) => {
        console.log("Notification Received - Background", notification.payload);
        // Calling completion on iOS with `alert: true` will present the native iOS inApp notification.
        completion({alert: true, sound: true, badge: false});
      });
    }
  }

What i have done so far ?

I have tried to use Master Branch to see the update for this one but got Error while Running :

Error :
bundling failed: Error: While trying to resolve module `react-native-notifications` from file `/Users/bobbyrinaldy/Project/React/Mobile/src/app.js`, the package `/Users/bobbyrinaldy/Project/React/Mobile/node_modules/react-native-notifications/package.json` was successfully found. However, this package itself specifies a `main` module field that could not be resolved (`/Users/bobbyrinaldy/Project/React/Mobile/node_modules/react-native-notifications/lib/dist/index.js`.

Enviroment 👍
    "@react-native-firebase/app": "6.7.1",
    "@react-native-firebase/messaging": "6.7.1",
     "react-native-notifications": "wix/react-native-notifications#master", // or "react-native-notifications": "^3.1.4",

@bobbyrinaldy

The problem about not showing notifications in drawer in a foreground mode.
If you want them, use the version without Channels. Check this out.
It's sounds like you don't have a dist folder inside lib folder. If you should install all modules inside react-native-notifications folder and then run yarn build

@bobbyrinaldy

The problem about not showing notifications in drawer in a foreground mode.
If you want them, use the version without Channels. Check this out.
It's sounds like you don't have a dist folder inside lib folder. If you should install all modules inside react-native-notifications folder and then run yarn build

Thanks for your references,
use the version without Channels you mean i can use master branch ? sorry for asking, because i cannot understand what you mean.
but for dead state not receiving any notification ? what should i do ?
how about the tutorial about this one ? https://github.com/wix/react-native-notifications/wiki/Android:-Layout-Customization

@bobbyrinaldy

you should use an older version or create a fork and revert this change
dead state not receiving any notification problem
I'm not a code owner, so can't say anything about the customization. Sorry

@bobbyrinaldy

you should use an older version or create a fork and revert this change
dead state not receiving any notification problem
I'm not a code owner, so can't say anything about the customization. Sorry

ahhh that clear for me, thanks for your time btw.
try to check if im can do something about it

@bobbyrinaldy i did 1).
Don't forget to generate and push into your fork dist folder (It's ignored in .gitignore) if you are not going to publish into npm.

@bobbyrinaldy i did 1).
Don't forget to generate and push into your fork dist folder (It's ignored in .gitignore) if you are not going to publish into npm.

allright, thank in advance, very helpfull for me

@bobbyrinaldy just got an answer from the author of the change i've mentioned.
I think it's easier to create a local notification when you are in the foreground mode to show it in a drawer.

Hi everyone, I don't find better solution than ask my question here.
It looks like I do something wrong with my android (ios works fine).
For me:

registerRemoteNotificationsRegistered
registerNotificationOpened
getInitialNotification
work good.
But:
registerNotificationReceivedForeground
registerNotificationReceivedBackground
have never triggered.

I think I put something wrong in AndroidManifest.xml (I have tried different variant but it still doesn't work).
Or problem occurs from using

react-native-notification
react-native-pusher-push-notifications
at the same time.

Please maybe someone have some ideas?
I use:

"react-native-notifications": "^3.2.2",
"react-native-pusher-push-notifications": "^2.4.0",
"react": "16.9.0",
"react-native": "0.61.5",

@nikita-filimonau i've learned that it's better all registration except registerNotificationOpened register as soon as possible. In my case i register they in an app constructor.

@anisimov74 Hi, I do it in explained way (register all in constructor). Also I have tried to remove registerNotificationOpened but it doesn't help.

@nikita-filimonau how do you send messages? As far as I know is a difference between data or notification. In my case there were no difference. I tried to send test messages from the server (data) and from Firebase Console. Did you try sending from Firebase Console?
It may at least give you an understanding what works and what doesn't.
I can also add that in  SplashActivity.java i had intent.putExtras(this.getIntent());. May be it can help.
This is my manifest part:
<meta-data
          android:name="com.google.firebase.messaging.default_notification_icon"
          android:resource="@drawable/notification_icon"/>

      <meta-data
          android:name="com.google.firebase.messaging.default_notification_color"
          android:resource="@color/notification_icon_color"/>

Ok, maybe it will be helpful for someone or just start some discussions )
Well, from my understanding the react-native-pusher-push-notifications handle notification first, so library react-native-notifications can't catch that.
Not the better decision but it will works before I find better solution.
I modified file PusherWrapper.java in react-native-pusher-push-notifications library to handle more information. The main problem was that library doesn't return info that send in data part of notification.
You can check changes here:
https://stackoverflow.com/questions/61985546/react-native-notification-foreground-messages/62093605#62093605
@anisimov74 Thanks for your support.

Yeah, just a note. When I have deleted react-native-pusher-push-notifications
The library react-native-notifications worked properly.

Hi, notifications work on some Android devices & some don't. Any clues ?


[Question] How to manage duplicate response headers

Describe the bug
We have an ASP.Net Core service which uses YARP to forward requests to multiple other services. We noticed recently that our responses have duplicate response headers, where the response headers from the proxy-forwarded destination are combined with the response headers of the service hosting YARP.
Below is an example of duplicated response-headers:

To Reproduce
Have a service setup which uses YARP to forward requests to other services. Service which is hosting YARP calls endpoints.MapReverseProxy() in startup and has a standard route config in appsettings with routes and match paths. The reverse proxy is added in the startup with
 services.AddReverseProxy()
            .Load(builder.Configuration.GetSection("ReverseProxy"));

Further technical details
I've been looking to see if anyone else has had a similar issue but can't seem to find anything. What I want to ask is what the best approach is to deal with this duplication. Is the best practice to tell the service hosting YARP to not include any response headers for reverse proxy routes? Is there some sort of response transform that allows me to merge the proxy response headers with the response headers of my service acting as the entry point? Or maybe there is something I'm missing.
Any sort of help/resources will be greatly appreciated!

How are you adding these headers in your service hosting YARP? Some middleware that automatically adds them to every response before invoking next?
There are two ways to approach this:
A) Prevent them from being added for routes that will be proxied. This would involve inspecting the matched endpoint to see if it's assigned to YARP.
B) Use a transform to filter out duplicates from the back end.
https://microsoft.github.io/reverse-proxy/articles/transforms.html#addresponsetransform

Exactly, the headers are being added by middleware. The headers are necessary in non-yarp calls (some endpoints are not proxied but are handled by the service directly).
I tried option B, but the transform removed the headers coming from the destination service, which may have information we need (like content-type for the payload). In other words I'd like to remove the headers added by the service hosting YARP and keep only the destination response headers, but I don't know if that's possible using transforms. It seems like transforms are only for transforming responses from proxy destinations.
I think we might have to go with option A, though not so desirable. It would mean adding custom logic for proxied routes to prevent the addition of headers. It may be the best option though.

Transforms can do almost anything to the response. With the defaults, the proxy response headers are copied and appended to the AspNetCore response headers. You could scan the AspNetCore response headers in the transform and remove duplicates.

Oh, or you just have a request transform that calls Clear on the response headers before proxying. That would get rid of any default app headers.

I will try the second option you mentioned, it seems the cleanest. How would clearing the response headers in a request transform ensure no default app headers are returned? I don't quite understand but I'll give it a go.
Thanks so much for your time and the speedy responses.

That depends on how the middleware are adding them? I assume they're being added on the way in. It's more difficult to add them later.

Alright I will try to remove them in the request transform. I'll close the issue for now since it's more of a question/behavior, I'll add my solution later on once I've figured it out (in case anyone else finds the same behavior in the future).
Thanks again!

Oh, or you just have a request transform that calls Clear on the response headers before proxying. That would get rid of any default app headers.

This solved my issue. I did the following transform:
services.AddReverseProxy()
    .AddTransforms((context) =>
    {
        context.AddRequestTransform(async requestContext =>
        {
            requestContext.HttpContext.Response.Headers.Clear();
            await Task.FromResult(requestContext);
        });
    });

And my issue was solved, only the destination response headers were included.

        context.AddRequestTransform(requestContext =>
        {
            requestContext.HttpContext.Response.Headers.Clear();
            return default;
        });

Have the same issue but I'm using a HttpForwarder.  It does not appear to have the AddRequestTransform option.  Is there another way to clear the response headers?

If you are already using the forwarder directly, you also have access to the HttpContext, so you can use that directly httpContext.Response.Headers.Clear();.
You also have control over the HttpTransformer used, and you can add extra logic there (see CustomTransformer in direct forwarding docs).
If you are running into more problems, please open a new issue.

That works.  Thank you!

From: Miha Zupan @.>
Sent: Friday, September 1, 2023 9:44 AM
To: microsoft/reverse-proxy @.>
Cc: Williams, Anna @.>; Comment @.>
Subject: [EXTERNAL]: Re: [microsoft/reverse-proxy] [Question] How to manage duplicate response headers (Issue #1971)
If you are already using the forwarder directly, you also have access to the HttpContext, so you can use that directly httpContext.Response.Headers.Clear();.
You also have control over the HttpTransformer used, and you can add extra logic there (see CustomTransformer in direct forwarding docshttps://urldefense.proofpoint.com/v2/url?u=https-3A__microsoft.github.io_reverse-2Dproxy_articles_direct-2Dforwarding.html&d=DwMCaQ&c=j9YNQVTYIohH8cYE_3mLmw&r=PaO4_Cax22BUWnXzINx4sDIBHr4tHn5X2SQTEimO2dw&m=WDihOBuIpcmF1lWgRqNoy34jg0XxrcQnkH8amJqq6pfPGPMSce5PE5YYa9_ScOZp&s=Pkgi3JC1p0Vu8CHLsAoVGy-ZERLwtzeYuYQ5OqmTCg0&e=).
If you are running into more problems, please open a new issue.
—
Reply to this email directly, view it on GitHubhttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_microsoft_reverse-2Dproxy_issues_1971-23issuecomment-2D1702772746&d=DwMCaQ&c=j9YNQVTYIohH8cYE_3mLmw&r=PaO4_Cax22BUWnXzINx4sDIBHr4tHn5X2SQTEimO2dw&m=WDihOBuIpcmF1lWgRqNoy34jg0XxrcQnkH8amJqq6pfPGPMSce5PE5YYa9_ScOZp&s=cz4wLaO-qPO1lvSmzd9F6fS1Yj2exqWuWqKueXv0kvc&e=, or unsubscribehttps://urldefense.proofpoint.com/v2/url?u=https-3A__github.com_notifications_unsubscribe-2Dauth_ABZ5MBOJVUJLYXQUKPTKBCTXYHRCVANCNFSM6AAAAAATE3PKZE&d=DwMCaQ&c=j9YNQVTYIohH8cYE_3mLmw&r=PaO4_Cax22BUWnXzINx4sDIBHr4tHn5X2SQTEimO2dw&m=WDihOBuIpcmF1lWgRqNoy34jg0XxrcQnkH8amJqq6pfPGPMSce5PE5YYa9_ScOZp&s=gj6ef_Kh_ErOVmv4VJf5O8ip7AUtBautXPF26pgGn34&e=.
You are receiving this because you commented.Message ID: @.***>

Removing headers with httpContext.Response.Headers works as shown below.  However, after clearing my browser cache I'm getting net::ERR_HTTP2_PROTOCOL_ERROR 200 on all resources using the proxy.
app.UseEndpoints(endpoints =>
{
endpoints.Map("/proxy.ashx/{**catch-all}", async (HttpContext httpContext, IHttpForwarder forwarder) =>
{
var error = await forwarder.SendAsync(httpContext, "targetUrl", httpClient, requestOptions,
static (context, proxyRequest) =>
{
var targetUrl = context.Request.QueryString.HasValue ? context.Request.QueryString.Value.Substring(1) : context.Request.GetEncodedUrl();
proxyRequest.RequestUri = new System.Uri(targetUrl);
proxyRequest.Headers.Host = null;
return default;
});
    // Check if the proxy operation was successful
    if (error != ForwarderError.None)
    {
        var errorFeature = httpContext.Features.Get<IForwarderErrorFeature>();
        var exception = errorFeature.Exception;
    }

    //Remove headers added by Proxy
    //httpContext.Response.Headers.Remove(HeaderNames.CacheControl);
    //httpContext.Response.Headers.Remove(HeaderNames.XPoweredBy);
    //httpContext.Response.Headers.Remove(HeaderNames.XXSSProtection);
    //httpContext.Response.Headers.Remove(HeaderNames.XContentTypeOptions);
    //httpContext.Response.Headers.Remove(HeaderNames.StrictTransportSecurity);
    //httpContext.Response.Headers.Remove("X-AspNet-Version");
});

});


Allow application code to be transport agnostic

This PR aims to provide ways of interacting with renet that are transport layer agnostic.
The basic additions in this PR are two bevy System Sets: RenetReceive and RenetSend.
These are the system sets where all transport layers should place their receive and send systems, allowing users to easily ensure that their systems run before/after Renet's transport layer systems run, rather than having to individually ensure that for each transport layer they care about.
The other addition in this PR is to move the Bevy run conditions from being implemented in each transport layer to making one single definition that uses RenetClient. This also means that each transport layer now has to update the RenetClient with the current state.
I also made quite a few methods private, specifically the methods that expose the internal connection status of the transport layers and the systems that previously marked when a transport layer would receive/send data. This was primarily done to help users migrating from previous versions notice that these shouldn't be used anymore, as well as not confuse new users.
If this change isn't desired (especially the one about the transport layer connection status), then I'm happy to revert this change.
Fixes #115

Also as an aside, I'm not entirely sure how you do the changelog, i.e. whether I should write the changelog here, or if you go through all the PRs with breaking changes when you draft a new release.


Question

Hallo Martin,
I would like to change to load raster instead of loading vector tiles, is it possible
Thank your help last time it work

This is geocoding project. Raster tiles are irrelevant. You probably have a wrong repo.


Update QSG steps

Update Quick Start Guide steps to run APK properly with latest changes.

Codecov Report
Patch coverage has no change and project coverage change: -2.68 :warning:

Comparison is base (417b800) 34.14% compared to head (32aa536) 31.46%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1104      +/-   ##
==========================================
- Coverage   34.14%   31.46%   -2.68%
==========================================
  Files         352       71     -281
  Lines       38954     9997   -28957
  Branches    12182      680   -11502
==========================================
- Hits        13302     3146   -10156
+ Misses      25412     6731   -18681
+ Partials      240      120     -120

Flag
Coverage Δ

adapter
26.85% <ø> (ø)

admin-domain-service
?

backoffice-domain-service
51.11% <ø> (+0.32%)
:arrow_up:

devportal-domain-service
?

idp-domain-service
79.18% <ø> (ø)

runtime-domain-service
?

Flags with carried forward coverage won't be shown. Click here to find out more.
see 283 files with indirect coverage changes

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


Updated Readme and added a few more snippets.

This is the same as #2 except with a cleaner git history.
@vokal/ios-developers anyone want to take another look and give any feedback?

Sorry Thought I figured out the git issues.  But apparently not.  I'm going to work to get to the bottom of it.


Add limit parameter to observation results API

To allow the plants dashboard to show statistics from the most recent
observation of a given planting site, allow the client to request a specific
number of results and change the result order so the most recently completed
observation always comes first. The client can thus pass in a planting site ID
and a limit of 1 to fetch the latest observation results for the site.
The default is still to return results from all observations.

Current dependencies on/for this PR:

main

PR #1201   👈

This comment was auto-generated by Graphite.


Unable to infer closure type in the current context (generateData)

When using generateData with the progress, I am getting an error that I couldn't solve for the life of me:
 let fileData = try PDFGenerator.generateData(document: batchPagesv2, progress: { (test) in
                            progressBar.progress = test
                        }, debug: true)

The error I am getting: Unable to infer closure type in the current context. I do have it implemented in a do/try/catch. Note that the plain ol generateData works flawlessly:
PDFGenerator.generateData(document: batchPagesv2)

I am pretty sure this is a usual Swift Compiler Error.
Sometimes the compiler gives us the wrong error message. At a glance I would guess it's happening because you are not using a self. before the progressBar.progress which is necessary to use in closures.
To debug, remove the progressBar.progress = test and replace it with a print(test). If it compiles fine, try it with the self..
Please clarify this issue still exists

Close due to inactivity, please reopen if necessary


bug: problem with "relist insold items"

Prerequisites

[X] I have searched for existing issues that already report this problem, without success.

Script Version
1.1.7
Platform
Webapp
Current Behavior
Bot forget option "relist unsold items" for any filters.
Expected Behavior
Fix
Steps to Reproduce

Additional Information
No response

fixed in the latest release


nerdtree-tabs panel shrinks horizontally

When I start my Vim session, nerdtree-tabs panel looks right. I reveal and hide it frequently via NERDTreeTabsToggle. But after a while it starts to shrink horizontally, to the point where it becomes unusable. The only way to fix it is to restart vim, which obviously isn't desirable. I'm open to any suggestions on how to fix it, or how to debug it.

Same problem. When opening new tabs, it shrinks very quickly. Whenever showing or hiding the panel the window shrinks more. It's really weird. This makes the plugin basically unusable for me right now, which sucks because I found it was just the thing for going through this huge codebase. It's weird because yesterday it seemed to work. I'm still figuring out why it's being like this.


Make CI green

Fixes #29
Decided to branch of #24 is imminent and already has some fixes.

Created https://github.com/NLeSC/python-template/issues/80 as it should not be job of template consumer to fix lint workflow.

Thanks


firstOf() ignores overridden fromStringLiteral(String)

The following grammar contains three rules. Each of these rules should match inputs "a" or "b", optionally followed by spaces.
rule1 explicitly matches the trailing whitespace with zeroOrMore(sp()). This rule matches the input "a".
rule2 implicitly matches the trailing whitespace by overriding fromStringLiteral(String) and adding zeroOrMore(sp()). That is: "x" matches this string; "x " matches sequence("x", zeroOrMore(sp())). This rule does NOT match the input "a". This is incorrect.
rule3 is the same as rule2 but also matches cr(). This slight change causes the rule to match the input "a".
Note: it seems that the actual change in rule3 is not important: If at least one non-String argument is present, the rule does match the input "a".
The issue seems to be that if all arguments of firstOf() are string literals, the overloaded fromStringLiteral(String) is ignored.
$ gradle
:compileJava
:processResources UP-TO-DATE
:classes
:run
rule1: true
rule2: false
rule3: true

BUILD SUCCESSFUL

Total time: 5.954 secs
$ cat build.gradle
defaultTasks 'run'

apply plugin: 'application'
apply plugin: 'java'

sourceCompatibility = 1.8
mainClassName = 'app.Main'

dependencies {
    compile 'com.github.fge:grappa:2.0.0'
}

repositories {
    mavenCentral()
}
$ cat src/main/java/app/Main.java
package app;

import com.github.fge.grappa.Grappa;
import com.github.fge.grappa.buffers.CharSequenceInputBuffer;
import com.github.fge.grappa.parsers.BaseParser;
import com.github.fge.grappa.rules.Rule;
import com.github.fge.grappa.run.ListeningParseRunner;

public class Main {

    public static void main(final String[] args) {
        final Parser1 parser = Grappa.createParser(Parser1.class);
        final CharSequenceInputBuffer buffer = new CharSequenceInputBuffer("a");
        System.out.println("rule1: "+new ListeningParseRunner<>(parser.rule1()).run(buffer).isSuccess());
        System.out.println("rule2: "+new ListeningParseRunner<>(parser.rule2()).run(buffer).isSuccess());
        System.out.println("rule3: "+new ListeningParseRunner<>(parser.rule3()).run(buffer).isSuccess());
    }

    public static class Parser1 extends BaseParser<Object> {

        public Rule rule1() {
            return firstOf(sequence(fromStringLiteral("a"), zeroOrMore(sp())), sequence(fromStringLiteral("b"), zeroOrMore(sp())));
        }

        public Rule rule2() {
            return firstOf("a ", "b ");
        }

        public Rule rule3() {
            return firstOf("a ", "b ", cr());
        }

        @Override
        protected Rule fromStringLiteral(final String string) {
            return string.endsWith(" ") ? sequence(super.fromStringLiteral(string.substring(0, string.length()-1)), zeroOrMore(sp())) : super.fromStringLiteral(string);
        }

    }

}

A better example for rule3 would be: firstOf("a ", "b ", NOTHING).


PHN Information is getting missed on Personal FOI Request

Describe the bug in current situation
System is not maintained information entered inside PHN for Personals requests
Link bug to the User Story
Impact of this bug
DATA LOSS or  DISPLAY missing for PHN or DATA NOT POPULATING on Front end - PHN
Chance of Occurring (high/medium/low/very low)
Pre Conditions: which Env, any pre-requesites or assumptions to execute steps?
Steps to Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Actual/ observed behaviour/ results
Expected behaviour
A clear and concise description of what you expected to happen. Use the gherking language.
Screenshots/ Visual Reference/ Source
If applicable, add screenshots to help explain your problem. You an use screengrab.

https://github.com/bcgov/foi-flow/pull/1219

This is fixed.
As discussed, the PHN (editable field only for the analyst) is not a field in the online form.


#296 add a puzzle for a java implementation

Adding a puzzle to continue resolving #296

@HDouss this pull request is too small, just 4 lines changed (less than 10), there will be no formal code review, see §53 and §28; in the future, try to make sure your pull requests are not too small; @paulodamaso/z please review this and merge or reject

@HDouss Perfect

@rultor merge

@rultor merge

@paulodamaso OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@paulodamaso Done! FYI, the full log is here (took me 14min)

Job gh:yegor256/jpeek#389 is not assigned, can't get performer

This job is not in scope


docs: update design/tradeoffs doc regarding scanner vuln reports #818

Description
Updates the tradeoffs section in the design documentation to accurately reflect copa's ability to work with or without vulnerability scanner reports.
The changes:

Remove outdated statements about scanner report dependencies
Clarify the package-based update model
Maintain information about package manager dependencies and platform limitations
Improve document structure for better readability

Changes

Replace outdated tradeoffs content with updated, accurate information
Add clearer section organization with numbered points
Update description of scanner integration to reflect optional usage

Closes #818

@pradhans0906 can we also add these changes to version docs starting from v0.7.0, since that was the release of the update all feature

@pradhans0906 thank you! looks like the commits need sign off again for DCO check

@pradhans0906 there are some merge conflicts, would you be able to rebase?


go get faild

Get https://stathat.com/c/consistent?go-get=1: x509: certificate has expired or is not yet valid

Sorry, can you try again?

The HTTPS certificate on stathat.com expired again, 9 days ago.
package stathat.com/c/consistent: unrecognized import path "stathat.com/c/consistent" (https fetch: Get https://stathat.com/c/consistent?go-get=1: x509: certificate has expired or is not yet valid)

Fixed

Thank you!

Expired again.
Would you please fix it? 🙇
$ openssl s_client -connect stathat.com:443 2>/dev/null | openssl x509 -noout -dates
notBefore=Jun 25 02:44:40 2018 GMT
notAfter=Sep 23 02:44:40 2018 GMT

doesn't work again, please fix the issue

04/01/2019   doesn't work again


bofa tile starter from TES + insanely small bugfix

https://github.com/uthuluc/TourGuide/blob/master/iotm2023BOFA

would help if i shared the bug huh

vamp masq is slightly janked up and also

the new _resolutionAdv pref is now double-counting somehow because reso adventures are being captured in some of ryo's useful pref fixes

new small bugfix via tes -- bottom delay counts the NC, top delay doesn't. just should be subtracting # of NCs remaining. this is actually annoying logic but it is solvable.


gax: cannot compile with references to SNAPSHOT of api-common

Local development of gax may fail if we are working with a SNAPSHOT of api-common (i.e. bazel build //gax:.... Maven installs work properly
This is because of dependencies.properties of gax pointing to an old released version.
If we change this version locally to our working snapshot, the bazel job will fail to find the snapshot because it only fetches from public servers.
This may cause problems with dependencies other than api-common
edit: adding info from a personal investigation (it references the outdated showcase bazel workflow)
Versions declared in the dependencies properties need to be available in the specified repositories. Inspecting the source of jvm_maven_import_external shows it doesn’t fall back to local servers as the maven command would do. It rather converts artifact coordinates into jar urls to be downloaded from the specified servers
Possible solutions
Try to remove api-common from Bazel files, e.g. in java_gapic.bzl
Since gapic-generator-java is now released as a jar with its own dependencies, it may be redundant to manually list dependencies such as common-protos or api-common
Use maven_install (example) with previous snapshot installed
This rule takes advantage of the availability of local repositories as an option. We would have to run mvn install on the whole repository to have local snapshots available. This doesn’t solve the problem of having a dependencies file in sync with the actual contents of the poms across the repo.
If we have to go with this approach, use release-please to manage the version of api-common.

cc: @blakeli0 @JoeWang1127 @suztomo
We may want to leave this as an item for the hermetic build

We may want to leave this as an item for the hermetic build

Sounds good to me.

it only fetches from public servers

What is "it"? Can you add an URL of the document that states so?

@suztomo I expanded the issue description with some findings of mine, plus I clarified what exactly fails to fetch the SNAPSHOT (the bazel resolution of dependencies)

Thank you. jvm_maven_import_external is old one. maven_install is better.

This is a valid issue but it is a niche use case. When developing locally, we can use Maven instead. For self-service client, they should always use a released version. Closing as not planned.


2.0 Timeline Nesting Issues

Some more issues with how the Timeline editor is completely messing up the trees.
Since I'm using converted timelines, just for reference I'll include 1.x screenshot of the same timeline as well in a couple of them for comparsion of what the expected behavior is:
Example A:
Timeline:

Expected tree from 1.x:

Result in timeline editor:

Example B, further down in the same timeline as Example A:
Timeline:

Expected behavior is obvious due to simplicity
Result in timeline editor, note the lines starting from the Text nodes and then just not continuing at all:

Example C
Timeline:

1.x expected tree:

Result in timeline editor:

Example D
Timeline, starts with an if:

Result in timeline editor:

this one was fixed, I believe by #1083 ?


How to encode object that contains meta

It might be due to my limited knowledge of this library, but I can't seem to find a way to encode object with meta field.
If I add meta property to object, it is encoded as attribute (i would say expectedly).
I can workaround this by manually inserting meta dictionary to encoded version of the object. But this is not very elegant.
I am using Codable extension.

Hi @jcavar, thanks for the report! This seems similar to https://github.com/infinum/Japx/issues/10
What we can do here is to check if object has data as nested object and in that case treat meta and included objects as JSON API objects as well.
We didn't want to automatically encode meta and included as JSON API objects since those can represent normal JSON objects in most of the cases.
Handling meta and included only when data is used as nested object seems like a least intrusive way of handling this case. Or we can use some config which could specify wanted behaviour? What do you think @Truba ?

We didn't want to automatically encode meta and included as JSON API objects since those can represent normal JSON objects in most of the cases.

Could you give an example of this? I thought when present, meta has to be JSON API meta object.

Not necessarily, I mean encoding JSON objects to JSON:API objects is not defined by any specification nor standard. So handling meta, included is left to implementation details of library.
For example:
{
    "type": "articles",
    "id": "1",
    "title": "JSON API paints my bikeshed!",
    "body": "The shortest article. Ever.",
    "created": "2015-05-22T14:56:29.000Z",
    "updated": "2015-05-22T14:56:28.000Z",
    "author": {
        "type": "people",
        "id": "42",
        "name": "John",
        "age": 80,
        "gender": "male"
    },
    "meta": {
        "type": "meta",
        "id": "2",
        "name": "Some name"
    }
}

it is unclear should we treat meta as included relationship or JSON:API meta information.
That's why we are considering using flags to let user choose the behavior

Hmm, I see. Yes, that makes sense.

Hi @jcavar ,
In encoder there was already a property additionalParams to add additional params to the root near the main data part. You can end up with something like:
{ "data": ..., additionlParam1: ..., additionalParam2: ... }
We've also added JapxEncodingOptions with  includeMetaToCommonNamespce property that would allow you to extract meta  at the same level as the attributes and relationships. It also allows you to extract relationship meta into resource identifiers.

Very nice, thank you!

This is released with 2.2.0, closing, thanks for the input @jcavar !


Bug(OCI8): $validDSNs regex for Oracle service names should support periods

PHP Version
8.3
CodeIgniter4 Version
4.5.3
CodeIgniter4 Installation Method
Composer (using codeigniter4/appstarter)
Which operating systems have you tested for this bug?
Linux
Which server did you use?
apache
Database
No response
What happened?
Recent changes to OCI8/Connection.php:
https://github.com/codeigniter4/CodeIgniter4/commit/99346b48aa0b8bdb8b491f640d27640091de95a8
Cause the $this->buildDSN(); function to get called now which exposes an issue (for me) with the protected $validDSNs .  The Oracle DSNs that I use contains a service name with periods, for example our DSN is something like //host:port/my.service which fails the $validDSNs check.
If the "ec" (Easy Connect) regex gets a period added to the service name part of the regex, it fixes the issue, currently the $validDSNs is:
    protected $validDSNs = [
        'tns' => '/^\(DESCRIPTION=(\(.+\)){2,}\)$/', // TNS
        // Easy Connect string (Oracle 10g+)
        'ec' => '/^(\/\/)?[a-z0-9.:_-]+(:[1-9][0-9]{0,4})?(\/[a-z0-9$_]+)?(:[^\/])?(\/[a-z0-9$_]+)?$/i',
        'in' => '/^[a-z0-9$_]+$/i', // Instance name (defined in tnsnames.ora)
    ];

Change the 'ec' one to include a period and that fixes the issue:
 'ec' => '/^(\/\/)?[a-z0-9.:_-]+(:[1-9][0-9]{0,4})?(\/[a-z0-9$_]+)?(:[^\/])?(\/[a-z0-9.$_]+)?$/i',
Steps to Reproduce
Set an Oracle database connection in CI4 to use a service name with a period, like //host:port/my.service, it will fail this part of the code in Connection.php (by "fail" I mean, it won't return true):
        foreach ($this->validDSNs as $regexp) {
            if (preg_match($regexp, $this->DSN)) {
                return true;
            }
        }

Expected Output
A DSN like //host:port/my.service should be considered valid.
Anything else?
No response

Thank you for reporting!
Please check #9006.


Refine color contrast for devtools dark mode

Originally posted by @Rien
I'd say currently color contrast is terrible. Excessive contrast can lead to eye strain.
See below:

https://github.com/vuejs/devtools/issues/677


http.get not work but http.post work...

hi. my cli version 1.6.8
proxy.js
const PROXY_CONFIG = [
{
context: [
"/api",
"/modules"
],
target: "http://dev.localhost.com/",
secure: false,
pathRewrite: {
"^/": "/"
},
changeOrigin: true,
logLevel: "debug"
}
]
module.exports = PROXY_CONFIG;
package.json
"start": "ng serve --output-hashing=all --aot=false --vendor-chunk=true --live-reload=false --sourcemap=false --proxy-config proxy.conf.js",
this poxy only http.post work and http.get not work
post console message
[HPM] Rewriting path from "/api/member/login.php" to "/api/member/login.php"
[HPM] POST /api/member/login.php -> http://dev.localhost.com/
but get is not work
I do not know why I have these symptoms.

Hello, we reviewed this issue and determined that it doesn't fall into the bug report or feature request category. This issue tracker is not suitable for support requests, please repost your issue on StackOverflow using tag angular-cli.
If you are wondering why we don't resolve support issues via the issue tracker, please check out this explanation.


bug: Traceback (most recent call last):

After adding the keys to the config.json file
When I run the program, this error appears

cx_Freeze: Python error in main script
Traceback (most recent call last):
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\Lib\site-packages\cx_Freeze\initscripts_startup_.py", line 120, in run
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\Lib\site-packages\cx_Freeze\initscripts\Console.py", line 16, in run
File "wit_transcriber\gui\app.py", line 20, in
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\site-packages\click\core.py", line 1130, in call
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\site-packages\click\core.py", line 1055, in main
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\site-packages\click\core.py", line 1404, in invoke
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\site-packages\click\core.py", line 760, in invoke
File "wit_transcriber\gui\app.py", line 10, in gui
File "D:\a\wit_transcriber\wit_transcriber\wit_transcriber\gui\main_window.py", line 56, in init
File "D:\a\wit_transcriber\wit_transcriber\wit_transcriber\gui\preferences.py", line 13, in init
File "D:\a\wit_transcriber\wit_transcriber\wit_transcriber\gui\preferences.py", line 16, in load_preferences_file
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\json_init_.py", line 346, in loads
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\json\decoder.py", line 337, in decode
File "C:\hostedtoolcache\windows\Python\3.10.6\x64\lib\json\decoder.py", line 353, in raw_decode
json.decoder.JSONDecodeError: Expecting property name enclosed in double quotes: line 3 column 1 (char 48)

OK

Something is wrong with your JSON file, can you please paste it here and censor you token?

I know the error is in the json file
Specifically because I added more than one value within one dictionary
Perhaps the dictionary only accepts one value
For this you must add the feature of adding a token from within the program
Also put the expected error inside except:

انا عدلت ملف json بالشكل الصحيح
وحاليا بجربه مع ملف صوتي english
ومنتظر النتيجة


Integrated terminal copies only the visible lines

VSCode Version:
Version 1.11.2
Commit 6eaebe3b9c70406d67c97779468c324a7a95db0e
Date 2017-04-13T08:03:11.395Z
Shell 1.4.6
Renderer 53.0.2785.143
Node 6.5.0

OS Version: 10.0.14393

Steps to Reproduce:

Open the Integrated terminal
Run a command with a longer enough output to cause part of the output to not be visible (you'll have scroll bars)
Scroll to the beginning of your output, select 1-2 lines
Scroll to the bottom of the output
SHIFT+Click to select all output
Right-click to copy the output to your clipboard
Paste your clipboard content somewhere else
In my tests with Code and Insiders, only the visible part of the output is copied: one would assume the "hidden" output is still selected and therefore copied to the clipboard but that does not seem to be the case

Duplicate https://github.com/Microsoft/vscode/issues/6755


Replaced relative link with absolute links and remove locale

The PR is to turn on the link check flag.

Disable the relative links.
Remove locale "en-us" from link.

Pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=542176&view=logs&j=0874ffeb-2919-5b4b-20de-16a97970b94c

Thanks for looping me in @xirzec
@sima-zhu, @weshaggard,
This PR should not have included the Track 1 data plane packages that are auto-generated. Next time these are updated via the code generator, these changes would be lost. Please log an issue in https://github.com/Azure/autorest.typescript/ to request the changes you want in the readme file in auto-generated packages. Please ensure to mention that this change should happen in both v4 and v6 versions of the code generator.
I also agree with @xirzec that it would have been preferable if the removing of locale was in a separate PR than the one that had the absolute link changes

Sorry @xirzec I missed your comments last night when I was trying to get these link update PRs in, they were causing some build storms due to the number of files touched so I was trying to get them in quickly.
After this change our link checker will start to fail for any links that are broken or that fail our link guidance (i.e. are relative, or contain locale).
As for track 1 we don't have a great way to exclude those from our link checker and we were already fixing everything else so we decided to fix them as well. We didn't realize the code-generation aspect of the MD files. @sima-zhu please follow-up to see what it would take to get the generated MD files fixed and if not we need to figure out a way to filter them in our link validation checks.
@xirzec @ramya-rao-a sorry about the misunderstanding with the track 1 files and let us know if there is any fallout because of that and we will help deal with it.

No fallout, we will make sure the code generator is updated appropriately.
I have reached out to @deyaaeldeen and @joheredi offline

Thanks @xirzec and @ramya-rao-a pointing this out! Please feel free to reach out to me if we need any extra handling for track 1 library.


[Bug] Fix flaky sample YAML tests

Why are these changes needed?
test-raycluster-sample-yamls-nightly-operator becomes very flaky recently. #1556 introduces a new YAML file for a RayCluster with GCS FT. As a result, the sample YAML tests have become flaky. There are two YAMLs, ray-cluster.external-redis.yaml and ray-cluster.external-redis-uri.yaml, for GCS FT-enabled RayCluster custom resources. If the Redis Pod from the first YAML isn't deleted in time, the RayCluster from the second YAML will connect to the terminating Redis. Consequently, the RayCluster crashes when the Redis Pod is eventually deleted.
Related issue number

Checks

[ ] I've made sure the tests are passing.
Testing Strategy

[x] Unit tests
[x] Manual tests
[ ] This PR is not tested :(

cc @rueian

Hi @kevin85421, I am sorry about that.
I thought the whole kind cluster will be recreated before each run of yaml. Wasn’t that the case?

Hi @kevin85421, I am sorry about that.
I thought the whole kind cluster will be recreated before each run of yaml. Wasn’t that the case?

No need to apologize. It's quite common, and I also overlooked that part during the code review. I cc'd you primarily because you're planning to improve CI, and I wanted to ensure you have enough context for the change. In compatibility-test.py, the Kind cluster is recreated for each test class, but the sample YAML tests are not.

Out of curiosity can this situation happen in real life outside of CI? (delete one raycluster and start another one very quickly, and the second one fails because it connects to the first one's redis)

Out of curiosity can this situation happen in real life outside of CI? (delete one raycluster and start another one very quickly, and the second one fails because it connects to the first one's redis)

Yes, you can try to run both ray-cluster.external-redis.yaml and ray-cluster.external-redis-uri.yaml consecutively.


Deliverables for v1.3

Created a stackpane showing number of days left to the user's event
Created EditEvent command and its parser
Added tests for DeleteEvent and EditEvent commands as well as Event Model
Updated add, delete and edit commands to add_guest, delete_guest and edit_guest.

Closes issues #220, #164, #163, #109, #103, #101.

Pull Request Test Coverage Report for Build 328

71 of 135 (52.59%)  changed or added relevant lines in 10 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.8%) to 54.957%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/main/java/seedu/address/logic/parser/AddressBookParser.java
0
1
0.0%

src/main/java/seedu/address/ui/MainWindow.java
0
1
0.0%

src/main/java/seedu/address/model/event/Event.java
2
8
25.0%

src/main/java/seedu/address/ui/StatusBarFooter.java
0
6
0.0%

src/main/java/seedu/address/model/event/EventDate.java
14
22
63.64%

src/main/java/seedu/address/logic/commands/EditEventCommand.java
50
69
72.46%

src/main/java/seedu/address/logic/parser/EditEventCommandParser.java
0
23
0.0%

Files with Coverage Reduction
New Missed Lines
%

src/main/java/seedu/address/ui/StatusBarFooter.java
1
0.0%

Totals

Change from base Build 327:
0.8%

Covered Lines:
1591

Relevant Lines:
2895

💛  - Coveralls


Update README for Improved Structure and Engagement

This PR updates;

Table of Contents for easy navigation
sets clear separation of resources and suggested materials

Hi @SalemTracey
Please examine this one too.


Revisit FakeBackend and FakeJob

In qiskit-experiments we have our own manifestations of FakeBackend and FakeJob, which are different from the classes with the same names that exist in Terra. We inherit directly from the base classes and not from the Terra classes. Do we really need our own implementation, can't we just use Terra's? If no then remove and use Terra. If yes then:

Change the names to something like FakeExperimentBackend - the identical naming is confusing.
Consider to inherit from the Terra classes.
Document why separate classes are required, and why they can't inherit from Terra (in the case that they continue to inherit from the base classes).

Also, for the class FakeJob, it would be nicer if it was defined in a file named fake_job.py, instead of utils.py.

Note that in our code we import both types of FakeBackend.


fix(clerk-js): Correct initial ref value for form feedback

Description

Checklist

[x] npm test runs as expected.
[x] npm run build runs as expected.
[ ] (If applicable) JSDoc comments have been added or updated for any package exports
[ ] (If applicable) Documentation has been updated

Type of change

[ ] 🐛 Bug fix
[ ] 🌟 New feature
[ ] 🔨 Breaking change
[ ] 📖 Refactoring / dependency upgrade / documentation
[ ] other:

Packages affected

[ ] @clerk/clerk-js
[ ] @clerk/clerk-react
[ ] @clerk/nextjs
[ ] @clerk/remix
[ ] @clerk/types
[ ] @clerk/themes
[ ] @clerk/localizations
[ ] @clerk/clerk-expo
[ ] @clerk/backend
[ ] @clerk/clerk-sdk-node
[ ] @clerk/shared
[ ] @clerk/fastify
[ ] @clerk/chrome-extension
[ ] gatsby-plugin-clerk
[ ] build/tooling/chore

Closing this one as we have pushed the commit in the main-v4

This PR has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


python3Packages.testpath: fix tests on Darwin

Motivation for this change
Works around https://github.com/jupyter/testpath/issues/24.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[x] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

@SuperSandro2000 mind taking another look?

@ofborg build python39Packages.testpath

python3Minimal fails on staging so it is quite hard to validate if this change works or not.

python3Minimal fails on staging so it is quite hard to validate if this change works or not.

Yes I just found that as well locally when testing unrelated things. Seems like a patch fails to apply.

I think it may be that both https://github.com/NixOS/nixpkgs/pull/146477 and https://github.com/NixOS/nixpkgs/pull/145752 were merged in staging, but I don't think Python 3.9.9 needs the bpo-44689 patch.

https://github.com/NixOS/nixpkgs/pull/148519 likely fixed that problem.
@ofborg build python39Packages.testpath