feat(handler-consistency): use the same handler style across the code base

Once I get the green light on the proposed changes, I'll add them to this PR.
Implementation done:

[x] button
[ ] checkbox
[ ] input
[ ] menu
[ ] pagination
[ ] popover
[ ] radiogroup
[ ] select
[ ] tag
[ ] textarea
[ ] toast

@schnerd yeah, that's what I am planning on, I'll add the code changes to this PR

Also have some concerns around blasting this change to the other event handlers i.e. onMouseEnter- since they already don't do much except propagate the normal even. Let me know if this isn't the best place to discuss that.

Why even include them in the public APIs in the first place, if they don't do much (and users could propagate them down themselves)?
How do we ensure users won't be confused between these and other event handlers they could pass in?

@abmai I think that's a very valid question, and we can definitely discuss here
to start with addressing your second question - as I see, if we provide the same change handler interface to all components we can eliminate any confusion (hopefully). and that I think leads to the answer to your first question  - if we wouldn't include them in the public API, we could not provide the same change handler interface
what do you think?

Why even include them in the public APIs in the first place, if they don't do much (and users could propagate them down themselves)?
I agree, in some places we are exposing these handlers when we probably don't need to (since people could just pass in via overrides). Removing those handlers in this PR might be outside its scope though.

How do we ensure users won't be confused between these and other event handlers they could pass in?
I'm also slightly concerned about this. That said, it doesn't seem like we're passing ...props into the root element in any of our components, so I don't think people will be able to pass an extra onMouseLeave etc as a top-level prop. They'll be forced to use overrides, which should probably make them think twice and realize they need a normal event handler.

One option is we could just start with the onChange–style handlers (ones that fire when some state changes), and leave the other onMouseEnter, onFocus, etc DOM-related handlers as-is for now?

One option is we could just start with the onChange–style handlers (ones that fire when some state changes), and leave the other onMouseEnter, onFocus, etc DOM-related handlers as-is for now?

it we'd do that, won't we end up with the same inconsistent API? for some of the change handlers one would use the onChange({event, value}) syntax, and for others it would be `onChange(event)

I have a similar concern with @abmai.
There's too much code bloat if we provide wrap around all the handlers in the name of consistency throughout our API.
Why don't we just change onChange to do this:
onChange={(event, value) => {
}}

The second parameter is always the value or values (for multiple select).

that makes sense - also it seems like most other react component libraries do the that
I am happy to change this PR in favor pf that. Thoughts David, Nadiia, Oleg, Anh?

I still think there's value in doing onSomethingChange({event, value}) in cases where we implement our own logic inside the handlers. It's that when we're just overriding a handler that should otherwise be pass-thru, it can be confusing.
Again, worth calling out that from looking at the surface area of change, there are two categories of handlers we're documenting in our public API:

Custom handlers, or handler overrides with additional logic (i.e. onChange(event, params))
Pass-thru handlers, (many cases of onChange, all cases of onMouseEnter, etc.)

Having an object-style params for the first case further differentiates that these are custom handlers, which is a good thing in my opinion. In the second case, I don't think we should even document it, but should properly propagate those handlers through. Therefore, we wouldn't even need to change them. Another argument for doing proper pass-thru is that the full list of events that a component should support is pretty big: https://reactjs.org/docs/events.html and it's odd if we choose to document only some of them even though we don't do anything on top of the raw handler.
With that said, those changes are out of scope of this PR. My suggestions for going forward:

Keep this PR, but scope the changes to only custom and overriden handlers.
Open a separate PR that will remove all pass-thru handlers, and implement correct props pass-thru for those components.

Thoughts?

I'm on board with what Anh suggested.
Seems like that would mean only updating the following handlers in this PR:
Accordion - onToggle
File Uploader - onChange
Menu - onItemSelect
Pagination - onPageChange
ProgressSteps - onClick
Select - onChange
Slider - onChange
Tag - onActionClick
I'm still unclear about the following:
Button Group - onClick - needs index to be useful
Everywhere else we'd just use onChange((event) = > {})?
@gergelyke thank you for making the RFC changes, I think that helped visualize how this would look across the codebase.

I like that too - let me update the PR tomorrow, and let’s continue from there

@gergelyke thank you for making the RFC changes, I think that helped visualize how this would look across the codebase.

Agreed, this helped a lot! Thanks, @gergelyke!

Seems like that would mean only updating the following handlers in this PR:
Accordion - onToggle
File Uploader - onChange
Menu - onItemSelect
Pagination - onPageChange
ProgressSteps - onClick
Select - onChange
Slider - onChange
Tag - onActionClick
I'm still unclear about the following:
Button Group - onClick - needs index to be useful
Everywhere else we'd just use onChange((event) = > {})?

Yes, thanks for surfacing these @gergelyke. This is a really helpful PR!
Generally I think using onChange to do our custom events is good so long as it doesn't create ambiguity to the existing DOM element's onChange. I think terms like RadioGroup and Pagination are not part of DOM and I don't expect it to have the same signature as the DOM's onChange. In this case, I wouldn't overwrite Input's onChange due to DOM also having an input. We should document our custom onChange with an extra icon or label, I have a feeling it would confuse a new comer.

closing in favor of https://github.com/uber-web/baseui/pull/372

I'm more inclined to make the args consistent across all handlers on the top level props. And avoid passing through the props - anything extra should be passed through overrides. There would still be a confusion when a component reused as a subcomponent of another one. That would create a mix of handlers on the overrides.
A good documentation would be required for any approach we choose to clear all the differences handlers args.


Error when using inttypes.h for PRImacros for esp_err_t (IDFGH-10042)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
release/v5.1
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
Development Kit.
ESP32C3-DEVKIT
Power Supply used.
USB
What is the expected behavior?
Unsilenced the warning for -Wno-format and replaced %d with %"PRId32" for esp_err_t and size_t. It should work with out typecast
What is the actual behavior?
Unsilenced the warning for -Wno-format and replaced %d with %"PRId32" for esp_err_t. But still, I am getting build errors with the below codes
Example 1: Getting error
#include <inttypes.h>
void app_main(void)
{
    esp_err_t esp_error = ESP_OK;
    ESP_LOGD(TAG, "esp_err = %"PRId32"", esp_err);
}

Example 2: No error after typecast to int32_t
#include <inttypes.h>
void app_main(void)
{
    esp_err_t esp_error = ESP_OK;
    ESP_LOGD(TAG, "esp_err = %"PRId32"", (int32_t)esp_err);
}

Example 3: Getting error
#include <inttypes.h>
void app_main(void)
{
    size_t required_size = 0;
    ESP_LOGD(TAG, "required_size = %"PRIu32"", required_size);
}

Example 4: No error after typecast to uint32_t
#include <inttypes.h>
void app_main(void)
{
    size_t required_size = 0;
    ESP_LOGD(TAG, "required_size = %"PRIu32"", (uint32_t)required_size);
}

What data types are defined for esp_err_t and size_t in esp idf v5.1? Does the application need to typecast for these values to fix the build errors?
Steps to reproduce.

Step
Step
Step
...

Debug Logs.
No response
More Information.
No response

I think esp_err_t is defined as int in all IDF versions, so it doesn't need the PRI- (exact width) integer format specifiers in this case. You can simply print it as %d.

Sorry if the recommendation in the docs wasn't formulated clearly. We don't recommend replacing all the format specifiers with the PRI-based ones.
inttypes.h specifiers should only be used for fixed-width integer types. See the "Format macro constants" section over at that page, various PRI* macros are used for different types defined in stdint.h, such as uint32_t, uintmax_t, intptr_t, and so on.
For other types, refer to the documentation of printf family of functions. For example, for size_t the format specifier should be %zu.
One note regarding %zu is that when "nano" formatting implementation is used in Newlib (CONFIG_NEWLIB_NANO_FORMAT=y), there is no support for z format modifier. For that reason, we don't use z modifier a lot in IDF, since we generally have to stay compatibly with "nano" formatting implementation. If you aren't using it in your project, though, you can use z modifier for size_t, which is better for portability.

One note regarding %zu is that when "nano" formatting implementation is used in Newlib (CONFIG_NEWLIB_NANO_FORMAT=y), there is no support for z format modifier. For that reason, we don't use z modifier a lot in IDF, since we generally have to stay compatible with "nano" formatting implementation. If you aren't using it in your project, though, you can use z modifier for size_t, which is better for portability.

So you are aware that this issue needs fix: https://github.com/espressif/esp-idf/issues/9631

@AxelLin yes, we are aware of that one and a few others.

@aggaddam We clarified the migration guide a bit. It will be available on master soon.

closing considering migration guide was udated


--auto-sub-langs

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.05.18 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
Please add a flag for automatic sub languages separating it from the main sub Lang's. I want to download all original created subtitles if It excists and live chat, but not all translations of the auto subtitles. Also please append .auto to the auto subs.
Verbose log
NA

duplicate of https://github.com/yt-dlp/yt-dlp/issues/2262


Morphed Gateways loose Input/Output and Extension Properties

Reproduce:

Add Input/Output parameter and extension properties to a gateway
Morphe gateway to another type

Problem:
Input/Output parameter and extension properties lost

The following properties are now kept as https://github.com/camunda/camunda-modeler/commit/2415cf9ba925b1b303923187c3556db468a0db0f /<EMAIL_ADDRESS>are integrated:

extension properties
listeners

Whether input and output should be kept is not clear. Based on the offical Camunda extension docs these are not allowed at all.


roadmap: fully functional Elasticsearch IR

[ ] #2657 finish initial elasticsearch IR implementation

initialise Elasticsearch
invenio.ext.elasticsearch
query parser to Elasticsearch
remove json_producer and friends that are not needed anymore

[ ] #2718 introduce index configurations

first with native analysers

[ ] pluggable Pythonic value enhancers (custom tokenisers)

e.g. name permutations

[ ] remove deprecated xapianutils/solrutils
[ ] remove native search engine (@jirikuncar)
[ ] command to index everything from scratch again in Elasticsearch

useful in case of crashes

[ ] plug record upload -> send signal -> catch and enrich JSON in enhancers -> send to Elasticsearch
[ ] add rank/sort options

push number_of_citations as a field
"more like this"

[ ] investigate second-order queries

refersto/citedby
all papers by e.g. French institutes (inspirehep/invenio#231)
parent-child indexing via record linking (but currently both parent and children need to live on the same Elasticsearch shard)

Addressed in Invenio 3.


docs(base.html): remove link to Deis 1.0 docs

I think the distracting big red banner about "You're viewing the latest release...for 1.0 click here" can be scrapped now that 1.0 has been in maintenance mode for a while. But maybe I'm jumping the gun? ping @slack.

I think enough time has passed - LGTM1

The flow into Deis v2 docs from Deis.com makes the destination (v1.0 vs v2.0) pretty clear to me.


In a remoteSSH LiveShare read/write terminal,  terminal control applications are blacked out for the guest

Describe what happened:

The host opened an SSH remote VSCode session via Remote Explorer.

The remote session was LiveShared with a guest.

A terminal was opened and shared in read/write mode.

A terminal control applications vi, ipython and jupyter console were opened in the shared terminal. In each case:

For the guest, the application terminal was black. For a a few milliseconds after a key press, it would display correctly, then black out again.
It didn't matter whether the host or guest launched the terminal control application.
The application always displayed correctly for the host.
For read-only terminals, the application displayed correctly for both host and guest

What was your system configuration?
Product and Version [VS/VSCode]:
VSCode.
Host and guest are both running:
Version: 1.44.2
Commit: ff915844119ce9485abfe8aa9076ec76b5300ddd
Date: 2020-04-16T17:50:03.709Z
Electron: 7.1.11
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Linux x64 4.15.0-96-generic
OS Version[macOS/Windows]:
Host, remote and guest are both running Kubuntu 18.04.3 LTS
Live Share Extension Version:
1.0.2048
Target Platform or Language [e.g. Node.js]: n/a
Steps to Reproduce / Scenario:
See above.
Please attach logs to this issue:
You can access them via the Live Share: Export Logs command from the command palette (ctrl + shift + p) and attach them to this issue
log.zip
Log

@sjdv1982: thanks for filing this issue!
Assigning to @IlyaBiryukov for further investigation

It must be because of some ANSI-sequences that a guest terminal renderer sends to the terminal process. For read-only terminals we ignore all input from the guests. If we ignore all ANSI-sequences from the guest terminals, this should fix it, and still let guest users participate in the terminals.
I'll have time to get to this issue in a several weeks or later.

@IlyaBiryukov Thank you for looking into it. LiveShare has been great for us already, but shared IPython consoles would be ideal for remote collaboration. We are really looking forward to this fix!

I tried again, and the problem is gone! Did you do something on the LiveShare server side?

It may have been an issue in the renderer in VSCode, and a recent update may have fixed it. We don't do anything with the traffic between collaboration session participants. In fact, we cannot even read it on the server side because it's encrypted end-to-end on the client side with ssh connection.

No recent update for me, it is still 1.44.2, same commit. I hope this isn't a heisenbug?


How to listen for code deleted by developers? I cannot obtain the deleted code using the following API, but I obtain the code after deleting it

vscode.workspace.onDidChangeTextDocument(async (event) => {
const document = event.document;
const contentChanges = event.contentChanges;
	for (const change of contentChanges) {
	  if (change.text === '') {
		await vscode.commands.executeCommand('workbench.action.files.save'); // 等待文档保存

		// 等待文档更新
		await new Promise((resolve) => setTimeout(resolve, 100));

		const deletedText = document.getText(change.range);
		console.log(`文件 ${document.fileName} 删除了文本：`);
		console.log(`被删除的文本内容：${deletedText}`);
		console.log(`范围：${change.range.start.line}:${change.range.start.character} - ${change.range.end.line}:${change.range.end.character}`);
	  }
	}
  })
)

### Tasks

Please ask your question on StackOverflow. We have a great community over there. They have already answered thousands of questions and are happy to answer yours as well. See also our issue reporting guidelines.
Happy Coding!


impl add/sub/mul wrapped for u128/i128

The change here implements add/sub/mul wrapped variants for u128/i128 by exporting the relevant bitcode functions and calling them. I'd like to implement them as asm, but it involves exposing multiple variants of add/sub/mul asm instructions and I will defer that to a subsequent PR, leaving this one the minimal change to get this working.
fixes #7253 , fixes #7251

I'm thinking we should cleanup some of the related tests in gen_num with this change to cover more of the different types.  They're a bit spread out and it's hard to see we've covered the different combinations. WDYT?

I can give it a shot. For example of add, I can move all the add_wrap_* tests to the same place and check similar spread of cases as the add_saturated test? I think for F32/F64/Dec there should be no wrapping behaviour, and currently Num.addWrap throws a type error when you try with Frac * types.


Extremely vague and confusing setup for Windows/Visual Studio C++ users.

I understand the pain of writing documentation however manually building and setting up GRPC for Windows machines and using Visual Studio is an absolute nightmare and has caused several people including me days of frustration.
However, I stumbled upon a savant by the name of plasticbox that has an already made set of scripts to automate the process for you. After fixing paths and settings in Visual Studio, you can get a hello-world application up and running in a half-hour.
https://github.com/plasticbox/grpc-windows
Perhaps you can add this in your 'easy installation' section? 📦

@y-zeng sorry I'm unfamiliar with the c++ build myself, cc @yang-g?

Since the time this issue was created, we actually deprecated the pre-generated VS projects and cmake is now the official way to build on Windows (so the instructions from https://github.com/plasticbox/grpc-windows are now obsolete).
The new instructions to build with cmake are available here
https://github.com/grpc/grpc/blob/master/INSTALL.md#building-using-cmake-recommended
There is still a few known issues with the cmake build (and we are working on fixing them), but things should be simpler now than with the old pre-generated vsprojects.


fix: PathRouteBuilder#any discards their exactRoute

Consider the following code,
import { Path } from "rocon/react";

const anyThenExactRoutes = Path()
  any("id", {
    action: ({ id }) => `id is ${id.slice(0, 8)}`,
  })
  .exact({
    action: () => "I am root",
  });

const exactThenAnyRoutes = Path()
  .exact({
    action: () => "I am root",
  })
  any("id", {
    action: ({ id }) => `id is ${id.slice(0, 8)}`,
  });

console.log(`any then exact: ${anyThenExactRoutes.exactRoute}
exact then any: ${exactThenAnyRoutes.exactRoute}`);

both anyThenExactRoutes and exactThenAnyRoutes have an exactRoute property on the type level, but...
Expected behavior
any then exact: [Object object]
exact then any: [Object object]

Actual behavior
any then exact: [Object object]
exact then any: undefined

Thank you very much!!! 🥺
However the new test has failed and apparently there is still a problem in types. I will take a look when I have time, but it'd be extremely nice if you could take a look too.


Android sdkmanager tool not found Flutter

please help me, i cant run my flutter project
i tried to instal the obsolete android SDK tools but it does not work
Try re-installing or updating your Android SDK,
visit https://flutter.dev/setup/#android-setup for detailed instructions.

Hi @Davidromerojimenez
Take a look at https://github.com/flutter/flutter/issues/51670#issuecomment-592943797
I'm closing the current one as duplicate.
If you disagree please write in the comments and I will reopen it.
Thank you


Mic doesn't turn off if applyPolyfill is set

Describe the bug
I'm trying to set up polyfill using react-speech-recognition and this library. My mic's behavior ok without using the polyfill.
To Reproduce
My code is almost the same as in the example. I have only changed the continuous property.
const appId = process.env.REACT_APP_SPEECHLY_ID;
const SpeechlySpeechRecognition = createSpeechlySpeechRecognition(appId);
SpeechRecognition.applyPolyfill(SpeechlySpeechRecognition);

const SomeComponent = () => {

  const {
    transcript,
    resetTranscript,
    listening,
    browserSupportsSpeechRecognition,
  } = useSpeechRecognition();

  useEffect(() => {
    if (!listening) {
      SpeechRecognition.stopListening();
      setTitleState(prevState);
    }

  }, [listening]);

  useEffect(() => {
    if (transcript) {
      setValue('do something here');
    }
  }, [transcript]);

  const handleOnClikOrTapStart = () => {
    setPrevState(titleState);
    if (browserSupportsSpeechRecognition) {
      resetTranscript();
      setTitleState(STATE_VOICE);
      SpeechRecognition.startListening({
        language: "en-US",
      });
    }
  };
return (
   <Button
            className={classnames("voice-btn", {
              active: listening,
            })}
            btnType="icon"
            onMouseDown={handleOnClikOrTapStart}
            onTouchStart={handleOnClikOrTapStart}
            disabled={!browserSupportsSpeechRecognition}
          >
            <MicIcon />
    </Button>
)
}

Expected behavior
I need to have my mic turned off. But it is working all the time after clicking the button.
Environment

Platform: [Desktop]
OS: [macOS (latest)]
Browser [chrome, safari]
Version [latest]
Package version [latest]

Hi @newdisease thanks for raising this issue!
You've encountered an interesting difference between the browser's native speech recognition and the Speechly polyfill. When SpeechRecognition.stop is called in the native version, the browser will stop transcribing and turn off the microphone. In the polyfill, voice data will stop being streamed to the Speechly API and transcription will end (i.e. the listening state will become false) but the microphone will remain active. However, the functionality should be identical between the two as no microphone data is being processed while transcription is turned off - the only difference is that the user will see the recording icon on their browser tab. Keeping the microphone on probably has a slight efficiency advantage in the case where transcription is needed again later. That said, I could understand if this affected user trust if they asked for the microphone to be turned off but could still see the recording icon.
Besides the microphone staying on with the polyfill, have you seen any unexpected behaviour differences that affect how your web app works?

Hi. Thanks for your answer!
After recording, the microphone does not work.  However, the recording icon still appears, confusing my users.
Is it possible somehow to fix that?

@newdisease I totally understand, and have raised an issue on the Speechly Browser Client library for you to follow. If we're able to work out a suitable change to the Browser Client, I'll update it in the polyfill.
In the meantime, the best I can suggest is to make it as clear as possible in your UI when no voice data is being processed (i.e. when the web app is not "listening"). In most cases, users will pay more attention to the UI than the recording icon in the browser tab, so they shouldn't notice the discrepancy too often. But I do understand your concern about any confusion or trust/privacy issues that could cause.

Hi @JamesBrill , I investigated a solution that allows closing the microphone after each utterance without @speechly/browser-client API changes. If you find this approach working work we could work towards creating a PR out of this (currently many unit tests fail as internal initialize function was retired).
Here's a summary of changes:

start() always waits for microphone to be reattached. This works well on modern browsers but at least old iOS 12 suffers from considerable lag.
there is a new listeningPromise that orchestrates start and stop calls into a queue so they work neatly in stress testing. Also 'transcribing` state change is immediate, used to ensure that duplicate start/stop calls are not made.

And here's the diff for git apply createSpeechRecognition.ts.patch:
diff --git a/src/createSpeechRecognition.ts b/src/createSpeechRecognition.ts
index 4828eec..2e0258d 100644
--- a/src/createSpeechRecognition.ts
+++ b/src/createSpeechRecognition.ts
@@ -32,11 +32,11 @@ export const createSpeechlySpeechRecognition = (appId: string): SpeechRecognitio

   return class SpeechlySpeechRecognition implements SpeechRecognition {
     static readonly hasBrowserSupport: boolean = browserSupportsAudioApis
-
     private readonly client: BrowserClient
-    private clientInitialised = false
+    private readonly microphone: BrowserMicrophone
     private aborted = false
     private transcribing = false
+    private listenPromise: Promise<void> | null = null

     continuous = false
     interimResults = false
@@ -46,15 +46,14 @@ export const createSpeechlySpeechRecognition = (appId: string): SpeechRecognitio

     constructor() {
       this.client = new BrowserClient({ appId })
+      this.microphone = new BrowserMicrophone()
       this.client.onSegmentChange(this.handleResult)
     }

     public start = async (): Promise<void> => {
       try {
         this.aborted = false
-        await this.initialise()
-        await this.client.start()
-        this.transcribing = true
+        await this._start()
       } catch (e) {
         if (e === ErrNoAudioConsent) {
           this.onerror(MicrophoneNotAllowedError)
@@ -73,31 +72,49 @@ export const createSpeechlySpeechRecognition = (appId: string): SpeechRecognitio
       await this._stop()
     }

-    private readonly initialise = async (): Promise<void> => {
-      if (!this.clientInitialised) {
-        const microphone = new BrowserMicrophone()
-        await microphone.initialize()
-        const { mediaStream } = microphone
+    private readonly _start = async (): Promise<void> => {
+      if (this.transcribing) {
+        return
+      }
+
+      this.transcribing = true
+
+      this.listenPromise = (async () => {
+        // Wait for earlier task(s) to complete, effectively adding to a task queue
+        await this.listenPromise
+        await this.microphone.initialize()
+        const { mediaStream } = this.microphone
         if (mediaStream === null || mediaStream === undefined) {
           throw ErrDeviceNotSupported
         }
         await this.client.attach(mediaStream)
-        this.clientInitialised = true
-      }
+        await this.client.start()
+      })()
+
+      await this.listenPromise
     }

     private readonly _stop = async (): Promise<void> => {
       if (!this.transcribing) {
         return
       }
-      await this.initialise()
-      try {
-        await this.client.stop()
-        this.transcribing = false
-        this.onend()
-      } catch (e) {
-        // swallow errors
-      }
+
+      this.transcribing = false
+
+      this.listenPromise = (async () => {
+        // Wait for earlier task(s) to complete, effectively adding to a task queue
+        await this.listenPromise
+        try {
+          await this.client.stop()
+          await this.client.detach();
+          await this.microphone.close();
+          this.onend()
+        } catch (e) {
+          // swallow errors
+        }
+      })()
+
+      await this.listenPromise
     }

     private readonly handleResult = (segment: Segment): void => {

@JesusADS Don't worry, I haven't forgotten about this issue - I've just lacked free time for open source recently. I've applied @arzga 's patch in a Pull Request to get the ball rolling. 😃

Thanks

The PR that fixes this is now ready for review - apologies for the delay. https://github.com/speechly/speech-recognition-polyfill/pull/31 @arzga @bigdatabaracus

@newdisease @JesusADS @kla-ko A fix for this has been released in version 1.3.0 - let us know if this resolves the issue for you.

Works on Chrome/Desktop, Opera/Desktop, Safari/Mobile, Samsung/Mobile
Thanks


Syntax highlighting for Nit language

Since you guys changed the way you handle highlighting, here's the updated version for the Nit language !
Samples were already included in #1320, I included a few samples however since it has some stuff that was not covered by the old samples (triple-quoted strings, FFI)

I took care of this over in #1973. It should be live on github.com within a couple of weeks.

And thanks!


add a helm chart for deployment

This adds a simple Kubernetes deployment mechanism for gitlab-monitor.

Thank you! :)


Make ownable configurable by deployment

Description

Type of change

[ ] Docs change / dependency upgrade
[ ] Configuration / tooling changes
[ ] Refactoring
[ ] 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)
[ ] Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)
Fixes #1736
Related pull request(s)

it seems we should have a single delay constant thats relevant for both upgrading the contracts and making any major ownership changes. is there a reason why they are different? open to other arguments here
other than that it lgtm

Hmm, I had thought it could be useful to have them separate tbh, you might want to upgrade quickly but make ownership changes slower. I could see our launch having these properties initially.

Agree

merging then!!


HMR not using alias

Using config below, error - Uncaught Package not found "app"
changing require("app")  ==> require("./js/app");  the module is found.
alias: {
"app": "~/js/app"
}
    var test = fuse.bundle("test")
        .target("browser")
        .instructions(` > index.js
        + **/*.{js,html,css,json}
    `);

   test.hmr().watch();

I think u might have got it wrong, aliases  are key/value based.
so with
alias: {
"app": "~/js/app"
}

you are asking fuse to whenever someone does import * as something from"app", to internally require ~/js/app and not vice versa.

I wasn't able to reproduce the issue

HMR picked up the changes without problems. Please provide a repository

My fuse.js is up one level and my index.js is under src.

Doesn't matter as long as your don't go outside the homeDir, it works

Wouldn't mind seeing what's is fuse.js

And my fuse.js is outside of homeDir.  Could be the problem??

My File hierarchy follows the getting-started doc.

That's good, it should be outside homeDIr.

Is js your homeDir?

no src

Humor me just once - add the CSSPlugin() plugin to your config, nothing else and see what happens.

Yep, works without problems.

Here's what I had to do:

Added my css to the test html page;

2. removed CSSPlugin() and aliases
3. copied one non-standard library to my js dir - node_modules/tablesorter/dist/js/extras/jquery.tablesorter.pager.min.js (no need to do this when alias works).
4.  changed require imports to relative directories.
Works with this config....  and font-awesome works without changes.

It's easier if you create a repo with your problem
And HMR doesn't work on external files.

Follow up on using HMR with  bootstrap & tablesorter

Not using aliases

CSS - Using CSSPlugin  - config and code
CSSPlugin({
group: 'bundle.css',
outFile: ${src}/bundle.css
}),

/*
Group and bundle css into ${src}/bundle.css - allows HMR to locate css
*/
if (1 == 2) {  //hack to eliminate 404's
require("~/../node_modules/bootstrap/dist/css/bootstrap.min.css");
require("~/../node_modules/tablesorter/dist/css/theme.blue.min.css");
require("~/../node_modules/tablesorter/dist/css/jquery.tablesorter.pager.min.css");
require("~/../node_modules/tablesorter/dist/js/extras/jquery.tablesorter.pager.min.js");
}
require('~/css/site.css');
require("font-awesome/css/font-awesome.css");

The tablesorter pager library(a jquery plugin) - used CopyPlugin -
CopyPlugin({ files: ["node_modules/tablesorter/dist/js/extras/jquery.tablesorter.pager.min.js"], dest : "static", useDefault : false })
require("../dist_test/static/d5b4a6d8-jquery.tablesorter.pager.min.js");
Need to code above import to have fuse inject the correct link into the html.

Whew!
From https://medium.com/fusebox/fusebox-2-0-the-beast-reborn-e4ec0443b782
Would like to get this working...
But with FuseBox HMR, we won’t make you refresh the browser, we will automagically reload only the files that changed, and all of your changes will immediately appear on your page!

@DaveO-Home
why don't you do:
import "bootstrap/dist/css/bootstrap.min.css"

Then use shims for jquery and tablesorter

@DaveO-Home the syntax provided by @nchanged above works perfectly, we use it.

@devmondo - you are absolutely correct and I am using the jquery shim and the bootstrap import works just fine.  However the tablesorter css does not load using the same syntax.  Also, I'm thinking the aliases don't work because in my config I declare them in src's parent directory.  I'm trying to use the same config for both dev and prod.  Aliases work in prod, so I do something like this require('bootcss'), therefore I put the boostrap for HMR in the bundle with tablesorter css.  Yes it may be much cleaner not to use alias with bootstrap.  My file hierarchy is complaint to this.  Also, I tried a shim for the tablesorter pager plugin without success.

guys, I did finally get the css to load with @nchanged suggested syntax, don't know why it didn't work previously?? So if I can only get the jquery plugin to work, it's coded like !function(e){ code..}(jquery);
Tried this in shim:
tablesorter: {source: "node_modules/tablesorter/dist/js/jquery.tablesorter.combined.js", exports: "tablesorter"},
tablepager: {source: "node_modules/tablesorter/dist/js/extras/jquery.tablesorter.pager.min.js"}

I don't this a jquery shim exports anything. I think it's set globally to $ variable, that's how plugins in jquery work

I checked that out by coding the plugin first in the shim.  It gave me "jQuery" not defined.  Moved it after jquery and it didn't complain.

that's how it should be after Jquery. Then you can just use it.. $.tablesorter or whatever

My problem is not with tablesorter that works just fine, it's the pager jquery plugin that's giving me the headache.  If I do my hack and load via html it plugs into jquery.  The shim doesn't plug it in, I get
$(...).tablesorter(...).tablesorterPager is not a function

Well, it turns out that the issue is index.js vs index.ts - index.js works when started up, but once a change is made to code the hmr does to re-process the aliases etc.  Changing to index.ts everything works, bug or feature?

Can u share your config?

const {FuseBox, QuantumPlugin, WebIndexPlugin, CSSPlugin, CSSResourcePlugin, HTMLPlugin, JSONPlugin, UglifyJSPlugin, HMRPlugin, CopyPlugin, EnvPlugin} = require("fuse-box");
const  {BlockStripPlugin} = require("./appl/js/plugin/BlockStrip");
const aliases = {
    "apptest": "./karma/apptest.js",
    "routertest": "./routertest.js",
    "toolstest": "./toolstest.js",
    "domtest": "./domtest.js",
    "app": "~/js/app",
    "router": "~/js/router",
    "pager": "tablesorter/dist/js/extras/jquery.tablesorter.pager.min.js",
    "default": "~/js/utils/default",
    "setup": "~/js/utils/setup",
    "helpers": "~/js/utils/helpers",
    "config": "~/js/config"
};
let value = !process.env.NODE_ENV? EnvPlugin({NODE_ENV: 'development', USE_KARMA: 'false'}) : null;
let isProduction = process.env.NODE_ENV === 'production';
let distDir = isProduction ? "dist_prod" : "dist_test";
let isKarma = process.env.USE_KARMA === "true";
let useQuantum = true;
let resources = (f) => (isProduction && isKarma ? `/base/dist_prod/resources/${f}` : isProduction ? `dist_prod/resources/${f}` : `../dist_test/resources/${f}`);
var src = 'appl';

const fuse = FuseBox.init({
    experimentalFeatures: false,
    plugins: [
	isProduction && WebIndexPlugin({
	    template: "appl/testapp.html",
	    target: "testapp.html",
	}),
	isProduction && useQuantum && QuantumPlugin({
	    //bakeApiIntoBundle: 'acceptance',
	    api: (core) => {
	        core.solveComputed("moment/moment.js");
	    },
	    //uglify: !isKarma,
	    manifest: false
	}),
	["node_modules/font-awesome/**.css",
	    CSSResourcePlugin({
	        dist: distDir + "/resources",
	        resolve: resources
	    }), CSSPlugin()],
	CSSPlugin(),
	HTMLPlugin(),
	JSONPlugin(),
	isProduction && !isKarma && BlockStripPlugin({
	    options: {
	        start: 'develblock:start',
	        end: 'develblock:end'
	    }}),
	isProduction && !isKarma && UglifyJSPlugin({
	    compress: true,
	    mangle: true,
	})
    ],
    homeDir: src,
    output: distDir + "/$name.js",
    log: true,
    debug: true,
    cache: !isProduction,
    hash: false,
    sourceMaps: isProduction && !isKarma,
    alias: aliases,
    allowJs: true,
    shim: {
	jquery: {
	    source: "node_modules/jquery/dist/jquery.js",
	    exports: "$",
	}
    }
});

if (!isProduction) {

fuse.dev({
    root: './',
    port: 3080,
    open: false,
});

var vendor = fuse.bundle("vendor")
        .target("browser")
        .instructions(`~ index.ts`);

var acceptance = fuse.bundle("acceptance")
        .target("browser")
        .instructions(`> [index.ts]`)
        .hmr({reload : true})
        .watch();

} else {

fuse.bundle('vendor')
        .target('browser')
        .sourceMaps(true)
        .instructions(`~ index.ts`);

fuse.bundle('acceptance')
        .target('browser')
        .sourceMaps(false)
        .instructions(`!> [index.ts]) // + ./appl/**/*.{js,html,css,json}`)
        .alias(aliases);
}

fuse.run(); //{chokidar : {ignored: /((^|[\/\\])\..|node_modules)/} });

and my index.ts and index.js - using  .js alias fails on reload, note; isKarma is false, isProduction is false
/* develblock:start */
if(!window.__karma__) {
    require ("./js/hmr");
}
/* develblock:end */

window.Popper = require("popper.js");

var App = require("app"),
	Router = require("router"),
	Default = require("default"),
	Setup = require("setup"),
	Helpers = require("helpers"),
	Config = require("config");
require("pager");

App.init(Default);

var Route = Router.init();

Setup.init();

/* develblock:start */
//Code between the ..start and ..end tags will be removed by the BlockStrip plugin during the production build.
//testit is true if running under Karma - see testapp_dev.html
if (typeof testit !== "undefined" && testit) {

    var apptest = require("./karma/apptest").apptest;

//Run acceptance tests.
apptest(Route, Helpers, App);
jasmine.DEFAULT_TIMEOUT_INTERVAL = 10000;
setTimeout(function () {
    __karma__.start();  //<===== Very Important - executed here!! -- Fusebox needs a delay.
}, 500);

}
/* develblock:end */

Have you seen that http://fuse-box.org/page/configuration#usetypescriptcompiler ?
You should use it, if you bundle .js instead of .ts

@DaveO-Home also make sure you dont have the same file name as ts and js as typescript will get confused

@DaveO-Home any updated?

No real updates - I went with development index.ts to use HMR and index.js in production to strip development code(I couldn't get typescript to not strip comments, even with my own tsconf file).
Using usetypescriptcompiler seems to be overkill(but it does fix the hmr problem), Renaming index.js to index.ts is simpler since typescript accepts javascript.


Create basic skeleton

Could you add a .nvmrc to this?

One more thing, seems we need to use Node 20 to host on Vercel
https://vercel.com/docs/functions/runtimes/node-js/node-js-versions

One more thing, seems we need to use Node 20 to host on Vercel https://vercel.com/docs/functions/runtimes/node-js/node-js-versions

Interesting! downgraded to v20.18.0


Access restrictions which use both IP and CA

Reverts changes in #2846

@MarkvanMents The fix is released. Please publish the documentation. Thanks!


what's the meaning of the "use_cbgs" ,thx

It means whether to use CBGS training strategy. For more details, please refer to https://arxiv.org/abs/1908.09492.


ICAT to PaNOSC Data Model Conversion

Description:
Once the data model for the Search API has been created, there needs to be some way of converting between the PaNOSC and ICAT data models. I believe we will need to convert both ways (i.e. from PaNOSC to ICAT and from ICAT to PaNOSC) to support query filters and then to convert the data from ICAT into a format suitable to be outputted in the Search API.
The current plans of converting from ICAT to PaNOSC (large credits to @louise-davies):

Affiliation (TBA on ICAT) <-> Affiliation
Investigation <-> Dataset
DataPublication? Investigation? <-> Document
Datafile <-> File
Instrument <-> Instrument
InvestigationUser <-> Member
InvestigationParameter <-> Parameter
User <-> Person
Sample <-> Sample
Technique (TBA on ICAT) <-> Technique

The property isPublic exists on the Dataset and Document entities in the PaNOSC data model. Since the anon user will be used in ICAT to get data, we can assume this value will always be true. However, the releaseDate could be used in ICAT to determine is a piece of data is actually public or not.
I'm not entirely sure how we go about converting between data models, perhaps we have a function in each PaNOSC entity class called convert_to_icat() and this constructs an ICAT entity in Python ICAT (using client.create())? Then there needs to be something similar to convert from ICAT to PaNOSC although I'm less sure how that would work at this stage.
There should also be tests to verify that the conversion works correctly.
Acceptance criteria:

[ ] Add mechanism to convert from PaNOSC to ICAT data model
[ ] Add mechanism to convert from ICAT to PaNOSC data model
[ ] Add tests for each conversion method

I think in our discussion on this last week we decided that an ICAT Dataset is a PaNOSC Dataset, and that an Investigation is a Document

@louise-davies thanks for the clarification, I've just updated the list to reflect that :)

Hi @MRichards99
Thanks for this.
I got a question about the mapping of the dataset:

pid
dataset.doi

Does it mean that all datasets need to have a DOI to be exported via panosc API? We are not minting a DOI for each dataset and will not happen because we got too many of them.
Besides I was wondering, can not this mapping be configurable? Even if what you propose has lot of sense it does not exactly corresponds to what we need and I can imagine that it will happen to others too.
I gave a quick look and the fields like technique.name, sample.description are not currently stored in such a way today and even needs to have a recent version of ICAT that is not the case today for us.

Just because that attribute in the ICAT schema is named doi does not mean that only a DOI may be stored in it

Then, am I supposed to fill the column DOI with something that is not a DOI? If it is the case I don't think it is a very clean approach and might be error-prone at medium, long-term.

Then, am I supposed to fill the column DOI with something that is not a DOI?

If your dataset does not have a DOI, but any other PID, yes. Where else would you put it? Btw. that attribute name in the ICAT schema is legacy. We discussed it several times and agreed that it would better be named pid instead. That is why the newer PID attributes in Instrument, ParameterType, Sample, and Study introduced in ICAT 4.10.0 have been named pid (rf. icatproject/icat.server#198 and icatproject/icat.server#216).

If it is the case I don't think it is a very clean approach and might be error-prone at medium, long-term.

The attribute names are invisible to users. The admins that are the only ones to see them should be professionals enough to be able to deal with such legacy names.


Possible to run testcafe-live via Node?

Hi,
Is it possible to run testcafe-live version via node?
I would like to start my runner class from CMD ">node tRunner.js chrome" but I would actually like to start the live version. I.e. I would like to monitor the test via devtools.
What should I write in my tRunner.js file in order to starta the testcafe-live version?
return runner
.src('./tTest.js')
.browsers([args])

TestCafe Live doesn't have a proper API yet, but you can use the child_process.spawn to start it in another process.


Try 'train.py' and 'ValueError: too many values to unpack (expected 2)' occured

Thank you for your work, this job is fabulous!
I tried the 'python train.py task=Aliengo headless=False' command and encountered a dimension mismatch error:
Error executing job with overrides: ['task=Aliengo', 'headless=False']
Traceback (most recent call last):
  File "train.py", line 61, in launch_hydra
    ppo_runner = OnPolicyRunner(env, train_cfg_dict, log_dir, cfg.rl_device)
  File "/home/xxx/Downloads/rl-mpc-locomotion/extern/rsl_rl/rsl_rl/runners/on_policy_runner.py", line 30, in __init__
    obs, extras = self.env.get_observations()
ValueError: too many values to unpack (expected 2)

Set the environment variable HYDRA_FULL_ERROR=1 for a complete stack trace.

the 'self.env.get_observations()' is printed as follows:
self.env.get_observations() =
tensor([[0., 0., 0.,  ..., 0., 0., 0.],
        [0., 0., 0.,  ..., 0., 0., 0.],
        [0., 0., 0.,  ..., 0., 0., 0.],
        ...,
        [0., 0., 0.,  ..., 0., 0., 0.],
        [0., 0., 0.,  ..., 0., 0., 0.],
        [0., 0., 0.,  ..., 0., 0., 0.]], device='cuda:0')

it seems to mismatch with the command 'obs, extras = self.env.get_observations()'
Some help will be appreciated~

Hi,
Thanks for your interests.
The submodule rsl_rl should be checked out to commit 2ad79cf, instead of the latest commit. I am not sure if it's the issue of git submodule update --init.
Could you try clone the repo again using git clone https://github.com/silvery107/rl-mpc-locomotion.git --recurse?

Thanks for your help!
It turns out to be the problem of rsl_rl version. The 2.0.2 version will rise the problem of ValueError and the 1.0.2 version works just fine.
When I first git clone using git clone https://github.com/silvery107/rl-mpc-locomotion.git and git submodule update --init sequentially, it won't be able to download all the submodules. Instead the command git clone https://github.com/silvery107/rl-mpc-locomotion.git --recurse works just fine.
Thank you again for you patience and help!

Great!


fix: Make caching work with custom attributes

When I added the custom attributes, I overlooked the fact that cache command does its own initialization of the Electrician, so it won't load the correct attributes.
This commit should fix that.
PS: I had a quick look at adding tests for the console commands, but since the package doesn't load a complete Laravel installation, testing Artisan commands is tricky. So for now, I'm afraid this is it.

I know about the tests for commands, that's a pain right now and I just make sure to keep as much domain logic out of them as possible.
Thanks 👍

Done!


RuntimeIdentifier property not set for referenced projects

I'm trying to make a project that is ultimately built using dotnet publish as a self-contained executable for multiple platforms (by specifying the runtime on the command line). This project has some different behavior (and native libraries) for each of my target platforms. I attempted to use the RuntimeIdentifier property as a condition in my csproj for DefineConstants as well as controlling which native libraries are copied over. However I found that referenced projects don't seem to have the RuntimeIdentifier property set during dotnet publish even though the entry point project does have that property set.
I've setup a repo that has a simple repro setup showing the issue. For reference, when I run dotnet --version it prints out 2.2.106. I'm also using the .NET SDK on macOS in case that makes a difference.
This feels like a bug to me, but it also might indicate that this isn't the correct way to handle native dependencies like this. I'm not trying to make a single cross-platform build (since I intend to distribute self-contained builds I don't need the .NET DLLs to be generic) so some of the advice in, for example, this issue aren't as important to me. I've simply ensured I have NativeLib.dll for Windows and libNativeLib.dylib for macOS which makes my DllImports work as intended (by specifying just 'NativeLib' as the assembly name and letting the runtime choose the prefix and suffix).
If this is a bug, hopefully it can be addressed. If there is a better way to handle things like configuring defines and copying the correct native libraries, I'd appreciate any pointers.

RuntimeIdentifier seems to be a question for project system: https://github.com/dotnet/project-system. cc @drewnoakes @davkean
I am not sure if interop will work cross-plat the way you plan to use it - @jeffschwMSFT @janvorli may know / help route ...

RuntimeIdentifier would be an SDK question, cc @dsplaisted @nguerrera

Try adding <RuntimeIdentifiers>win-x64;osx-x64<RuntimeIdentifiers> to the referenced projects. Put all the runtime identifiers that you use in publish. There is code in the process of resolving references that decides whether to flow runtime identifier based on whether the referenced project has rids or not.

That did in fact do the trick. Is that documented? It doesn't seem unreasonable but I had no idea I had to list those for the identifiers to resolve correctly.
Please feel free to close this issue unless you internally want it for something. I'm more than happy to add that property to my projects to resolve the issue.

I think we are probably missing documentation on this. It's relatively obscure. You can file an issue on https://github.com/dotnet/docs/issues and link here.
I will close this out, but happy to help on a docs issue with the text.


boost-locale:arm-windows fails to install when trying to install  boost-log, boost-program-options for arm-windows

PS X:\acdc> python .\build\scripts\build.py --clean --install-deps --arch arm
Starting Build
Target OS: Windows
Flavor: windows-arm-msvc-debug
Arch: arm
Config: debug
CMake Generator: Visual Studio 15 2017
Compiler: msvc
Clean: True
Source Path: X:\src
Bin Path: X:\bin\windows-arm-msvc-debug
Applied user-wide integration for this vcpkg root.
---- vcpkg output starts here ----
All MSBuild C++ projects can now #include any installed libraries.
Linking will be handled automatically.
Installing new libraries will make them instantly available.
CMake projects should use: "-DCMAKE_TOOLCHAIN_FILE=X:/acdc/build/vcpkg/scripts/buildsystems/vcpkg.cmake"
Using local portfile versions. To update the local portfiles, use git pull.
No packages need updating.
The following packages are already installed:
boost-build[core]:x86-windows
The following packages will be built and installed:

boost-align[core]:arm-windows
boost-asio[core]:arm-windows
boost-context[core]:arm-windows
boost-coroutine[core]:arm-windows
boost-date-time[core]:arm-windows
boost-dynamic-bitset[core]:arm-windows
boost-filesystem[core]:arm-windows
boost-interprocess[core]:arm-windows
boost-locale[core]:arm-windows
boost-log[core]:arm-windows
boost-multi-index[core]:arm-windows
boost-parameter[core]:arm-windows
boost-phoenix[core]:arm-windows
boost-pool[core]:arm-windows
boost-program-options[core]:arm-windows
boost-property-tree[core]:arm-windows
boost-proto[core]:arm-windows
boost-random[core]:arm-windows
boost-serialization[core]:arm-windows
boost-spirit[core]:arm-windows
boost-tokenizer[core]:arm-windows
boost-tti[core]:arm-windows
boost-variant[core]:arm-windows
boost-xpressive[core]:arm-windows
brotli[core]:arm-windows
cpprestsdk[brotli,core,default-features,websockets]:arm-windows
openssl[core]:arm-windows
openssl-windows[core]:arm-windows
websocketpp[core]:arm-windows
Additional packages (*) will be modified to complete this operation.
Starting package 1/30: boost-locale:arm-windows
Building package boost-locale[core]:arm-windows...
-- Using cached X:/acdc/build/vcpkg/downloads/boostorg-locale-boost-1.68.0.tar.gz
-- Using source at X:/acdc/build/vcpkg/buildtrees/boost-locale/src/ost-1.68.0-590dc9a6a1
-- Building arm-windows-rel
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:56 (message):
Command failed: X:/acdc/build/vcpkg/installed/x86-windows/tools/boost-build/b2.exe;--stagedir=X:/acdc/build/vcpkg/buildtrees/boost-locale/arm-windows-rel/stage;--build-dir=X:/acdc/build/vcpkg/buildtrees/boost-locale/arm-windows-rel;--user-config=X:/acdc/build/vcpkg/buildtrees/boost-locale/arm-windows-rel/user-config.jam;boost.locale.iconv=off;boost.locale.posix=off;/boost/locale//boost_locale;boost.locale.icu=off;-j12;--debug-configuration;--debug-building;--debug-generators;--disable-icu;--ignore-site-config;--hash;-q;-sZLIB_INCLUDE="X:/acdc/build/vcpkg/installed/arm-windows/include";-sBZIP2_INCLUDE="X:/acdc/build/vcpkg/installed/arm-windows/include";threading=multi;threadapi=win32;runtime-link=shared;link=shared;address-model=32;architecture=arm;toolset=msvc-14.1;-sZLIB_BINARY=zlib;-sZLIB_LIBPATH="X:/acdc/build/vcpkg/installed/arm-windows/lib";-sBZIP2_BINARY=bz2;-sBZIP2_LIBPATH="X:/acdc/build/vcpkg/installed/arm-windows/lib";variant=release;debug-symbols=on
Working Directory: X:/acdc/build/vcpkg/buildtrees/boost-locale/src/ost-1.68.0-590dc9a6a1/build
See logs for more information:
X:\acdc\build\vcpkg\buildtrees\boost-locale\build-arm-windows-rel-out.log

Call Stack (most recent call first):
installed/arm-windows/share/boost-build/boost-modular-build.cmake:270 (vcpkg_execute_required_process)
ports/boost-locale/portfile.cmake:20 (boost_modular_build)
scripts/ports.cmake:71 (include)
Error: Building package boost-locale:arm-windows failed with: BUILD_FAILED
Please ensure you're using the latest portfiles with .\vcpkg update, then
submit an issue at https://github.com/Microsoft/vcpkg/issues including:
Package: boost-locale:arm-windows
Vcpkg version: 2018.11.23-nohash
build-arm-windows-rel-out.log
build-arm-windows-rel-out.log
build-x64-windows-dbg-out.log
build-x64-windows-rel-out.log
build-x86-windows-dbg-out.log
build-x86-windows-rel-out.log

@cirvine-MSFT, boost build tool start to support to build with arm from 1_73, please try to get latest source and try again.
I have double confrimed, it built successfully for me, please reopen this issue if it still be a problem for you.
PS F:\VCPKG\boost_173\vcpkg> ./vcpkg install boost-locale:arm-windows
Computing installation plan...
The following packages will be built and installed:
boost-locale[core]:arm-windows
Starting package 1/1: boost-locale:arm-windows
Building package boost-locale[core]:arm-windows...
-- Using community triplet arm-windows. This triplet configuration is not guaranteed to succeed.
-- [COMMUNITY] Loading triplet configuration from: F:\VCPKG\boost_173\vcpkg\triplets\community\arm-windows.cmake
-- Using cached F:/VCPKG/boost_173/vcpkg/downloads/boostorg-locale-boost-1.73.0.tar.gz
-- Extracting source F:/VCPKG/boost_173/vcpkg/downloads/boostorg-locale-boost-1.73.0.tar.gz
-- Applying patch 0001-Fix-boost-ICU-support.patch
-- Using source at F:/VCPKG/boost_173/vcpkg/buildtrees/boost-locale/src/ost-1.73.0-3a88fc7440
-- Including F:/VCPKG/boost_173/vcpkg/ports/boost-locale/b2-options.cmake
-- Building arm-windows-rel
-- Building arm-windows-rel done
-- Building arm-windows-dbg
-- Building arm-windows-dbg done
-- Packaging arm-windows-rel
-- Packaging arm-windows-rel done
-- Packaging arm-windows-dbg
-- Packaging arm-windows-dbg done
-- Packaging headers
-- Packaging headers done
-- Using cached F:/VCPKG/boost_173/vcpkg/downloads/boost_LICENSE_1_0.txt
-- Installing: F:/VCPKG/boost_173/vcpkg/packages/boost-locale_arm-windows/share/boost-locale/copyright
-- Performing post-build validation
-- Performing post-build validation done
Building package boost-locale[core]:arm-windows... done
Installing package boost-locale[core]:arm-windows...
Installing package boost-locale[core]:arm-windows... done
Elapsed time for package boost-locale:arm-windows: 28.39 s


Results of Imagenet256 using DPM++ not reproducible

Problem
In the DPM++ paper, the FID of parameters [s=8.0 | NFE=25] for Imagenet256 benchmark is 8.39; yet, this repo does not produce an approximate number (the result shows about FID ~= 200).
Env
GPU: NVIDIA RTX 2080Ti * 4
Pytorch==1.13.1
cuda-11.7
config/imagenet256_guide.yml
# the rest of options is the same
sampling:
+batch_size: 10
+fid_total_samples: 10000

What I did
I simply ran ddpm_and_guided-diffusion/sample.sh and commented out CIFAR10/Imagenet64 to only execute Imagenet256
Question
Are there any parameters should be changed? I checked everything that mentioned in the paper or README in this repo.

Hi @wonkyoc ,
Thanks for following our work!
I've checked the script and config and I can successfully sample the images. Could you please show one of your sampled images here?

Hi @LuChengTHU,
Thanks for the fast response and I am glad that there is no problem. Unfortunately, I accidentally deleted results for fid_total_samples: 10000 but I assume fid_total_samples: 1000 should be enough to figure a problem out. The following information is from what I have just re-run.
# sample.sh
data="imagenet256_guided"
scale="8.0"
sampleMethod='dpmsolver++' or 'dpmsolver'
type="dpmsolver"
steps="20"
DIS="time_uniform"
order="2"
method="multistep"

# config/imagenet256_guided.yml
sampling:
    total_N: 1000
    batch_size: 10
    last_only: True
    fid_stats_dir: "./fid_stats/VIRTUAL_imagenet256_labeled.npz"
    fid_total_samples: 100
    fid_batch_size: 100

DPM++2M

DPM2M

Hope this can help!

@wonkyoc ,
Even if for samples like this, the FID cannot be that poor (~200). I guess the FID stats file you used may be incorrect. Could you please check it?

Hi @wonkyoc ,
I've checked carefully for the README and I feel so sorry for this typo: 52bc3fbcd5de56d60917b826b15d2b69460fc2fa
Is your bug corresponding to this incorrect FID stat?

@LuChengTHU
I actually recognized that typo and used the right file for Imagenet256. I also agree that that image (or w/ others) cannot be produce that high FID. I suspect one of packages related to calculating FID seems to be matter...
pytorch==0.3.0
scipy==1.9.1

I will investigate further

@wonkyoc
Please try the pytorch 1.x instead of 0.x (I used torch==1.12.1)

Oh, that's typo. I am using pytorch==1.13.1 and what I wanted to write was actually pytorch-fid=0.3.0. Anyway, luckily, I found an issue at my end. I put torch.manual_seed(0) for SDE evaluation and this generates only a certain set of images repeatedly and it eventually does not calculate the proper FID. (i.e., 50 images are generated multiple times filling 10k images). I am closing the issue. Thanks for your help!


chore(main): release 2.5.17

:robot: I have created a release beep boop
2.5.17 (2024-12-31)
Bug Fixes

细节优化 (493f882)
细节优化 (9cb921e)
调整结构 (3f89e63)
配置文件修改退出 (e41cf33)

Code Refactoring

优化ws和加载配置文件 (a2955ef)
优化代码 (e0e89c8)
重构部分代码 (6ca5a39)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/rainbowwarmth/KazuhaBot/releases/tag/v2.5.17 :sunflower:


Setup Cloudflare CSAM Scanning Tool

[!WARNING]

Trigger Warning
This ticket discusses child abuse.

[!IMPORTANT]

The contents of this ticket is not legal advice, does not reflect official policy of the EOS Network Foundation, and is not a formal statement by the EOS Network Foundation including but not limited to a statement of intention. This ticket is a proposal from the author to the larger organization provided according to the terms of the license in this repository. This disclaimer also applies to all comments and metadata surrounding this ticket, including but not limited to the GitHub Projects status.

From issue 88, this ticket is to setup the free Cloudflare CSAM Scanning Tool for the eosnetwork.com "website." Cloudflare's use of the term "website" includes eosnetwork.com and any *.eosnetwork.com domain or subdomain.
The Cloudflare CSAM Scanning Tool compares all of our web content proxied by Cloudflare to fingerprints of known child sexual abuse material (CSAM) provided by various child safety advocacy organizations.
If matching content is found, Cloudflare will automatically:

Block the content, preventing it from being served to clients.
File a report on our behalf to the National Center for Missing and Exploited Children (NCMEC), a private non-profit funded by the United States Congress, using their CyberTipline API.
Email the report ID along with technical information necessary for incident response to the EOS Network Foundation using an email address created for this purpose.

The NCMEC will review Cloudflare's report, inform the US government, and initiate an investigation.
The EOS Network Foundation is then responsible for responding to the incident in compliance with United States and International law, informed by internal policy and any legal advice. Such a response might look like this.

Escalate Cloudflare's report internally to relevant Engineers, Lawyers, and Executives.
Determine whether the content identified by Cloudflare is CSAM, or a false-positive.
Collect forensic information, potentially including but not limited to:

The offending content.
External access logs.
Internal access logs.
System logs.
Server images.
Specific software versions being used.
Current web architecture and relevant documentation.
Recent server backups.

Encrypt the collected data using modern cipher suites, such as AES-256 and SHA-512, to protect the privacy and identity of victims.
Store the encrypted copy of the collected data and the decryption key, separately, with a retention policy as required by law.
Cooperate with the corresponding law enforcement investigation.

The EOS Network Foundation does not host adult content, nor do they currently host user-uploaded content as far as the author is aware. However, illegal content could still become present on our infrastructure in the event of a cybersecurity incident or similar.

This ticket is currently blocked, waiting on CyberTipline API credentials to be issued by the National Center for Missing and Exploited Children.

This ticket is currently blocked, waiting on CyberTipline API credentials to be issued by the National Center for Missing and Exploited Children.
The NCMEC asked us to fill out a form about two weeks ago. I collected the necessary information from relevant stakeholders and submitted that form this afternoon.


With Expo, get this error: [TypeError: null is not an object (evaluating '_reactNative.NativeModules.ImagePickerManager.launchImageLibrary')][🐛]

Hello!
I am using react-native-image-picker with Expo and when run function (launchCamera or launchImageLibrary) get this error:
error: [TypeError: null is not an object (evaluating '_reactNative.NativeModules.ImagePickerManager.launchImageLibrary')]
error [TypeError: null is not an object (evaluating '_reactNative.NativeModules.ImagePickerManager.launchCamera')]
code:
import { launchCamera, launchImageLibrary } from 'react-native-image-picker';
const pickImage = () => {
try {
launchImageLibrary({ mediaType: 'photo' }, resp => {
console.log(resp);
});
} catch (error) {
console.log('error', error);
}
}
const camera= () => {
try {
launchCamera({ mediaType: 'photo' }, resp => {
console.log(resp);
});
} catch (error) {
console.log('error', error);
}
}
version:
"react-native-image-picker": "^4.0.6",
Any help please, thanks.

Same issue here ! Any solution please !

I'm having this issue but only when I run in expo-go. When I run from xcode in the simulator or on-device it works fine. I've cleaned and rebuilt in xcode and run expo start --clear a hundred times and I'm still getting this. I've also installed other libraries that work fine.

Same issue on android

Getting the exact same issue here on android

Just managed to fix this for my project. I needed to add two things to MainApplication.java
Add this to the top with your imports:
import com.imagepicker.ImagePickerPackage;
And add this ImagePickerPackage() where your MainReactPackage is:
protected List<ReactPackage> getPackages() {
          return Arrays.<ReactPackage>asList(
            new MainReactPackage(),
...
            new ImagePickerPackage()
);
}

this helped me https://docs.expo.dev/versions/v42.0.0/sdk/imagepicker/

@lukehali  Searching your option, I understand that this is possible only if detach expo project, because in my expo project  not found this files. And detach expo project it would be my last option.
@Flooooooooooorian yes, by the moment I'm using expo-image-picker, but this library no support select multiples images and that is what I need.
-- I create a new application with React Native without Expo and the library works without problems, will it be some incompatibility with expo?
-- someone knows similar library with multiple select images and run with expo?

Having the same issue. Any ideas?

Hello, I have the same issue. Anybody can help me, please ? Thank you

Hello, I have the same issue. Anybody can help me, please ? Thank you

HI
IF YOU HAVE THIS PROBLEM
FIRST GO https://docs.expo.dev/versions/latest/sdk/imagepicker/
AFTER INSTALL IN YOUR CMD
expo install expo-image-picker
AND COPY AND PASTE THIS
import React, { useState, useEffect } from 'react';
import { Button, Image, View, Platform } from 'react-native';
import * as ImagePicker from 'expo-image-picker';
export default function ImagePickerExample() {
const [image, setImage] = useState(null);
const pickImage = async () => {
// No permissions request is necessary for launching the image library
let result = await ImagePicker.launchImageLibraryAsync({
mediaTypes: ImagePicker.MediaTypeOptions.All,
allowsEditing: true,
aspect: [4, 3],
quality: 1,
});
console.log(result);

if (!result.cancelled) {
  setImage(result.uri);
}

};
return (
<View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>

{image && <Image source={{ uri: image }} style={{ width: 200, height: 200 }} />}

);
}
AND RELOADING YOUR APP

import React, { useState, useEffect } from 'react';
import { Button, Image, View, Platform } from 'react-native';
import * as ImagePicker from 'expo-image-picker';  // not react-image-picker

export default function ImagePickerExample() {
  const [image, setImage] = useState(null);

  const pickImage = async () => {
    // No permissions request is necessary for launching the image library
    let result = await ImagePicker.launchImageLibraryAsync({
      mediaTypes: ImagePicker.MediaTypeOptions.All,
      allowsEditing: true,
      aspect: [4, 3],
      quality: 1,
    });

    console.log(result);

    if (!result.cancelled) {
      setImage(result.uri);
    }
  };

  return (
    <View style={{ flex: 1, alignItems: 'center', justifyContent: 'center' }}>
      <Button title="Pick an image from camera roll" onPress={pickImage} />
      {image && <Image source={{ uri: image }} style={{ width: 200, height: 200 }} />}
    </View>
  );
}

Just managed to fix this for my project. I needed to add two things to MainApplication.java
Add this to the top with your imports: import com.imagepicker.ImagePickerPackage;
And add this ImagePickerPackage() where your MainReactPackage is:
protected List<ReactPackage> getPackages() {
          return Arrays.<ReactPackage>asList(
            new MainReactPackage(),
...
            new ImagePickerPackage()
);
}

I am using expo expo-dev-client with eas build in my project. Got the same error and this solution solved my problem. I just edited MainApplication.java. Added the import part to top and edited the other part like this:
        protected List<ReactPackage> getPackages() {           @SuppressWarnings("UnnecessaryLocalVariable")           List<ReactPackage> packages = new PackageList(this).getPackages();           packages.add(new MainReactPackage());           packages.add(new ImagePickerPackage());           return packages;         }
Then I rebuild my app and its working right now.

@audteyebaris
Finally It Worked
Using
npx expo install expo-image-picker


Add homedirectory reporting grafana dashboard

Adds a sortable home directory table that makes it much much easier to see who is using what. This is an addition to the same information shown as a timeseries in the user diagnostics dashboard.

(I've blanked out the usernames for privacy)
This has been used in production for a while, and is very helpful in finding users who inadvertently use terabytes of storage.

The linter looks like it has always failed, and I've reverted that in https://github.com/jupyterhub/grafana-dashboards/pull/136.

Thank you, @minrk


Send cloud-to-device messages with IoT Hub (Python) - ErrorCodes.UnknownError: Connection in an unexpected error state.

Hi,
I am trying to get the SimulateDevice.py / SendCloudToDeviceMessage.py to work,
At first the SimulateDevice.py did not work until I added websockets = true in line 24
client = IoTHubDeviceClient.create_from_connection_string(CONNECTION_STRING, websockets = True)
At this point I can run the SimulateDevice.py just fine and I am able to receive messages just fine using the Azure IoT Explorer but for some reason when I run the SendCloudToDeviceMessage.py I get the following error message
Starting the Python IoT Hub C2D Messaging service sample... Sending message: 0 ConnectionClose('ErrorCodes.UnknownError: Connection in an unexpected error state.') Unexpected error {0} ErrorCodes.UnknownError: Connection in an unexpected error state.
I have used the connection string from the iothubowner (Hostname, SharedAccessKeyName, SharedAccessKey) and the device ID to the device I added, not sure what else I could possibly change.

Python version 3.11.2
pip version 23.0
Azure IoT Hub version 2.6.1
Azure IoT Device version 2.12.0
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 617cf9c4-6f85-d240-d8e5-6010cd0b7839
Version Independent ID: a3c4e9da-c539-2f51-c245-57b5e43eca42
Content: Cloud-to-device messages with Azure IoT Hub (Python)
Content Source: articles/iot-hub/iot-hub-python-python-c2d.md
Service: iot-hub
GitHub Login: @kgremban
Microsoft Alias: kgremban

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

@Andri-e This error can occur if firewall is blocking the connection.
Make sure that port 8883 is open in your firewall. The device sample in this article uses MQTT protocol, which communicates over port 8883. This port may be blocked in some corporate and educational network environments. For more information and ways to work around this issue, see Connecting to IoT Hub (MQTT).

@Andri-e Please check the above suggestions and let us know if you have any further queries.
Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


Keep N most recent directories

Dirkeeper currently deletes the oldest count subdirectories, rather than what the README documents, which is deleting everything but the most recent count subdirectories. The special-cased counts of 0 (to delete everything) and greater-than-the-number-of-subdirectories (to delete nothing) work correctly, but are inconsistent with the less-than-the-number-of-subdirectories case.
I've changed the relevant test to make the difference more obvious by keeping a count that's different than the number of directories that should be deleted, then changed the dirs array slice to delete all-but-the-newest-n so it passes.

This might require a major version bump, since it worked completely different.

@niallo what do you think of moving this repo to the Strider org?

Ping :+1:

@niallo ding ding ding 🔔  😸

Hallo, anyone home 😉

@knownasilya done - moved! sorry for the delay

Woot! My persistence paid off

Now I just need npm rights

@knownasilya added on npm too!


Fixing bug with /bin/sh not understanding other shells' keywords

This is meant to fix the following issue:
https://github.com/nvbn/thefuck/issues/222
It reads the os.environ["SHELL"] to run the command to get the output.  If SHELL isn't defined, os.environ.get() should return None, which will run the default "/bin/sh" .

The corrects the interpretation, but still has bugs when using "sudo"

I solved my specific "nocorrect" problem by writing a new sudo.py rule that strips out the "nocorrect" and "noglob" keywords.
nocorrect mkdir -p /nopermissions --> sudo mkdir -p /nopermissions
This is a dumb solution, because it is zsh-specific.


Migrate to Next.js 13

Checkout discussion #660

Recently I learned Next.js 13 & do some projects on that...I would love to do this so that my skills will be enhanced..Can you assign this issue to me as a GSSOC23 contributor?

@crocmons have u gone through discussion #660

@crocmons have u gone through discussion #660

yeah..I read it properly..

@crocmons so are u planning to migrate it in one go?

@crocmons How long will it take for you to successfully migrate this?

@crocmons so are u planning to migrate it in one go?

yeah, I guess I need 1 week to successfully migrate this code into next.js 13...and if I have any trouble migrating this code then I will tell you...

Ok then, go ahead

Hey, I would like to collaborate to migrate the website to NexttJs.
I have created many websites with NextJs like these: B. S. Sen. Sec. School and my portfolio s2sharpit.me

@s2sharpit yes you can collaborate with @crocmons  if is she needs any assistance.
@crocmons Do you need to collaborate with him?

Hey @crocmons,
Looking forward to your response!

OK then you guys can work for this issue together. @s2sharpit You can take css part which needs to be migrated into tailwind css. Is that ok or something else you want to work on?

Hi @crocmons,
I hope you're doing well. I wanted to reach out and let you know that I've just created a new branch called next-ts-tw-migrate for our ongoing migration process. It would be fantastic if you could assist me by creating a pull request and incorporating the code for the Next.js migration that has been completed thus far into this branch.
Your expertise and collaboration would be greatly appreciated. Thank you so much for your support!

Hi @crocmons,
I hope you're doing well. I wanted to reach out and let you know that I've just created a new branch called next-ts-tw-migrate for our ongoing migration process. It would be fantastic if you could assist me by creating a pull request and incorporating the code for the Next.js migration that has been completed thus far into this branch, and, If you encounter any problems or difficulties during the process, let me know.
Your expertise and collaboration would be greatly appreciated. Thank you so much for your support!

ok

Hey @crocmons
Are you facing any problem while creating the pull request?

Actually, I need some time to work on it.. @s2sharpit I haven't created the pull request yet... @rohansx can you extend the time duration of this issue? Because I started today & there is a lot of code I have to remove also modify the code structure...

Actually, I need some time to work on it.. @s2sharpit I haven't created the pull request yet... @rohansx can you extend the time duration of this issue? Because I started today & there is a lot of code I have to remove also modify the code structure...

Hey, It's not to do whole migration today. It's just to create a pull request for the part you have done yet or the starting files.

Actually, I need some time to work on it.. @s2sharpit I haven't created the pull request yet... @rohansx can you extend the time duration of this issue? Because I started today & there is a lot of code I have to remove also modify the code structure...

Hey, It's not to do whole migration today. It's just to create a pull request for the part you have done yet or the starting files.

ok

wait @s2sharpit  typescript.. we don't need to add typescript here? In discussion #660 not mentioned typescript.

@s2sharpit getting error ...

Hey @crocmons
Can you tell me what error are you getting?

yeah, @s2sharpit  I'm getting errors on that branch now it was fixed ..And Also I create a pr but not completed yet still need to work on it...

Hello,
I wanted to update you on the progress of the project. I have successfully created the initial files and implemented navbar, and we are currently in the migration process. To view the website in its current state, please visit: https://informatician-next.s2sharpit.me/.

One second how could you merge your code here...PA will be merged...and the second thing I worked on the file & folder structure in my pr according to the next 13 rules...that's why I remove the src folder and separate the component, utils folder, layout ,pages file should be inside on the app folder. @s2sharpit @rohansx

Please don't merge and assign labels by yourself otherwise it may lead to disqualification from the gssoc program. Revert the PR and remove the label and create PR again. You should only review the PR and accept/request changes in the PR and as soon as you review the changes and accept it, I'll merge from my side.

@s2sharpit Please co-ordinate with @crocmons with the regarding issues

Dear @rohansx,
I sincerely apologize for the inconvenience caused. I understand the importance of following the correct procedure and I assure you that I will adhere to it moving forward. I will revert the pull request, remove the label, and create a new pull request once the necessary changes have been implemented.
Thank you for your understanding in this matter. I will solely focus on reviewing the pull request and providing feedback as required. After the changes have been accepted, I will patiently await your decision on the merging process.
Additionally, I acknowledge your request to coordinate with @crocmons regarding the related issues. I will reach out to @crocmons to ensure effective collaboration and resolve any outstanding matters.
Once again, I deeply apologize for any oversight and I will take extra care to strictly adhere to the program guidelines in the future.
Thank you for your understanding and guidance.

Hey @crocmons
Thank you for your feedback. I understand your concern about the file and folder structure, but I wanted to clarify that the src directory actually adheres to the Next.13 rules as well. Next.js provides flexibility in organizing the project structure, and the documentation on their official website (https://nextjs.org/docs/app/building-your-application/configuring/src-directory) supports this approach. Please take a look at the link for more information. If you have any specific suggestions or concerns regarding the src directory, I'm open to discussing them further. Thank you!"

Hey @crocmons Thank you for your feedback. I understand your concern about the file and folder structure, but I wanted to clarify that the src directory actually adheres to the Next.13 rules as well. Next.js provides flexibility in organizing the project structure, and the documentation on their official website (https://nextjs.org/docs/app/building-your-application/configuring/src-directory) supports this approach. Please take a look at the link for more information. If you have any specific suggestions or concerns regarding the src directory, I'm open to discussing them further. Thank you!"

@s2sharpit According to the latest version it's more convenient to use the app folder..Let me handle the folder structure because we have to add the API routes over there.. and also you add the component, utils folder inside the src folder

Alright, @crocmons. Since I've already raised some pull requests, I suggest we wait for those to be merged first. Once they're merged, you can go ahead and raise the pull request for the folder structure changes.

Also I noticed that you included global.css, a favicon inside the app folder it should be added on the styles, public folder @s2sharpit

Alright, @crocmons. Since I've already raised some pull requests, I suggest we wait for those to be merged first. Once they're merged, you can go ahead and raise the pull request for the folder structure changes.

yeah, sure

Also I noticed that you included global.css, a favicon inside the app folder it should be added on the styles, public folder @s2sharpit

Thank you for your feedback. Regarding the favicon, I placed it in the app folder because Next.js automatically detects and uses the favicon from that location. This ensures proper functionality and saves time by avoiding the need to manually configure it.
Regarding the global.css file, since we're using Tailwind CSS, a single global.css file suffices, eliminating the need for a separate styles folder.

Alright, @crocmons. Since I've already raised some pull requests, I suggest we wait for those to be merged first. Once they're merged, you can go ahead and raise the pull request for the folder structure changes.

yeah, sure

You can create pull request now for file structure issue @crocmons

Hey @crocmons,
As we are currently in the process of migrating the project to Next.js, a significant number of files are being changed with each pull request. Therefore, it is essential to synchronize your branch before making any pull requests to avoid unnecessary errors and conflicts.
Regarding the recent PR (#808), I wanted to bring to your attention that the theming of the project has been adversely affected. This issue arose because the pull request was merged without synchronizing the code. Consequently, the full theming has broken, resulting in an inconsistent appearance throughout the application.
Additionally, I would like to reiterate the importance of the favicon that was added to the 'app' directory. Next.js automatically uses this favicon for the website. Unfortunately, I noticed that you deleted it after the addition. It would be greatly appreciated if you could cooperate and retain the favicon to maintain consistency across the project.
To provide more context, I encountered the following errors while deploying on Vercel:

Error got in terminal:

I appreciate your cooperation in addressing these issues promptly. Resolving them will significantly contribute to both the stability and the successful migration of the project to Next.js.

Link of deployment of my last pr deployment: https://informatician-git-theme-s2sharpit.vercel.app
locally rendering application after merging your pr:

Hi @rohansx,
Could you please take a moment to review the ongoing issue discussed above? Your input and guidance on the matter would be invaluable.
Thank you for your attention.

Hello @rohansx and @crocmons,
I wanted to let you know that I have addressed the errors and made the necessary changes for a successful deployment of the website. Additionally, I have fixed the styling of the image section, which was previously broken.
I kindly request you to review the pull request (#818) at your convenience.

wait I'm currently working on the home component and now added the styling on the hero section...@s2sharpit

Hi @rohansx,
I hope you're doing well. I have a question regarding the assignment of levels to pull requests (PRs) in our repository. Could you please clarify the process for determining the level assigned to a PR?
Thank you in advance for your assistance.

Hey @rohansx
I would request you to merge the pull requests as soon as possible as it will help to work further in the migration process.

@rohansx @SiddhantPawar03 Can you please tell me what should be the db name?

@rohansx #936 & #944 please add a level to this pr...

Hello, @rohansx can you merge this #967 pr with the level.. so that I can add this new pr "Added Newsletter & Mail API Routes"...I got a merge conflict if I add this pr now because I added new npm packages...

@rohansx @s2sharpit @crocmons I would love to help you both with this if you need more assistance, I have good experience in tailwind css.

@rohansx, I think the 'next-ts-tw-migrate' branch is almost done. So, you can merge it into the main branch. We will do the rest of the implementation on the main branch so that other contributors can continue their work with this newly developed branch.

@s2sharpit @crocmons I saw by running the code of the nextjs branch, and its design has changed significantly from the main branch, including changes to the home page and other pages as well. So, please take a look at it once by comparing with the main branch deployed link

@s2sharpit @crocmons I saw by running the code of the nextjs branch, and its design has changed significantly from the main branch, including changes to the home page and other pages as well. So, please take a look at it once by comparing with the main branch deployed link

Thank you, @rohansx, for taking the time to explore the nextjs branch! Our goal was to improve the website, so we resolved any identified UI issues and made it more attractive where we felt it needs improvement. The ultimate aim was to create a seamless and enjoyable website. We would greatly appreciate your valuable feedback or any suggestions you might have for further improvement. Your input is essential to us, and we look forward to hearing from you!

@s2sharpit @crocmons  I was facing issues with the process you mentioned, so I created a copy of the main branch and named it 'v1.' Then, I copied all the files from the 'next-js-tw-migrate' branch and overwrote the files in the 'main' branch. After that, I pushed the changes to the main branch.
The migration to Next.js has been successfully completed in the main branch.
Apologies for the delays, now you can proceed with the further process and issues. Thanks for helping throughout this open source program. You guys are great contributors and collaborators. Appreciate your contributions.

@s2sharpit @crocmons Now, there is a main task to be done, which is to integrate the open-source book reader platform with books in the format of pdf or epub. Let me know if you guys would like to take on this task.

@s2sharpit @crocmons I was facing issues with the process you mentioned, so I created a copy of the main branch and named it 'v1.' Then, I copied all the files from the 'next-js-tw-migrate' branch and overwrote the files in the 'main' branch. After that, I pushed the changes to the main branch.
The migration to Next.js has been successfully completed in the main branch.
Apologies for the delays, now you can proceed with the further process and issues. Thanks for helping throughout this open source program. You guys are great contributors and collaborators. Appreciate your contributions.

Fantastic news, @rohansx! Thank you for the kind words and for all your assistance. Just a quick heads up, we'll need to update the framework preset in Vercel. Let's get that done and continue with the process. Appreciate your continued support.

@s2sharpit @crocmons Now, there is a main task to be done, which is to integrate the open-source book reader platform with books in the format of pdf or epub. Let me know if you guys would like to take on this task.

Hey @rohansx,
Thanks for reaching out! I'm interested in contributing to the project, but I must admit that I'm not familiar with integrating a book reader platform. However, I'm eager to learn and take on new challenges. I'll quickly look into it and get back to you soon to confirm if I can handle the task. Thanks again for considering me for this opportunity.
Looking forward to your response!
Best regards,
Tushar ☺

@s2sharpit @crocmons I was facing issues with the process you mentioned, so I created a copy of the main branch and named it 'v1.' Then, I copied all the files from the 'next-js-tw-migrate' branch and overwrote the files in the 'main' branch. After that, I pushed the changes to the main branch.
The migration to Next.js has been successfully completed in the main branch.
Apologies for the delays, now you can proceed with the further process and issues. Thanks for helping throughout this open source program. You guys are great contributors and collaborators. Appreciate your contributions.

I have checked it locally. It's working perfectly. 👍☺❤

Dear @rohansx,
I am happy to inform you that the issue has been resolved by adding the Mongodb environment key. Everything is now working correctly. Please be reminded to add your MongoDB environment key and ensure that the DB name is "Books".
Thank you for your cooperation.

@s2sharpit @crocmons Thanks for your help. I deployed the project but books section is not visible  on homepage please check that

Could you kindly provide the link here, @rohansx?

Could you kindly provide the link here, @rohansx?

It's the same link.. www.informatician.in

Could you kindly provide the link here, @rohansx?

@crocmons, Are you working on it, or I address this issue?

Also I have deployed the v1 branch on react.informatician.in for taking any reference to make further changes like adding oauth in login section and many more

@s2sharpit It appears that you have previously worked on this homepage, so I believe you may be able to address the issue at hand. Is it possible that the problem is related to the react-swiper card?

It appears that you have previously worked on this homepage, so I believe you may be able to address the issue at hand. Is it possible that the problem is related to the react-swiper card? @s2sharpit

It was working perfectly at morning. Let me handle the issue then. ☺

Also, @s2sharpit  I got this warning on my terminal you can check it out-
Warning: ReactStars: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead.
at ReactStars (webpack-internal:///(sc_client)/./node_modules/react-rating-stars-component/dist/react-stars.js:41:41)
at div
at div
at div
at CardContent (webpack-internal:///(sc_client)/./components/BkCards/CardContent/CardContent.js:41:28)
at a
at LinkComponent (webpack-internal:///(sc_client)/./node_modules/next/dist/client/link.js:105:19)
at div
at eval (webpack-internal:///(sc_client)/./node_modules/swiper/react/swiper-slide.js:26:67)
at div
at div
at eval (webpack-internal:///(sc_client)/./node_modules/swiper/react/swiper.js:40:98)
at div
at div
at div
at div
at BkCards (webpack-internal:///(sc_client)/./components/BkCards/BkCards.js:51:69)
at Lazy
at div
at section
at InnerLayoutRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:226:11)
at RedirectErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
at RedirectBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
at NotFoundBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/not-found-boundary.js:59:11)
at LoadingBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:322:11)
at ErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:103:11)
at InnerScrollAndFocusHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:139:9)
at ScrollAndFocusHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:213:11)
at RenderFromTemplateContext (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/render-from-template-context.js:15:44)
at Lazy
at OuterLayoutRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:331:11)
at Lazy
at m (webpack-internal:///(sc_client)/./node_modules/next-themes/dist/index.js:1:335)
at exports.ThemeProvider (webpack-internal:///(sc_client)/./node_modules/next-themes/dist/index.js:1:3636)
at ThemeProvider (webpack-internal:///(sc_client)/./components/theme/theme-provider.jsx:13:26)
at Lazy
at body
at html
at RedirectErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9)
at RedirectBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11)
at ReactDevOverlay (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/react-dev-overlay/internal/ReactDevOverlay.js:70:9)
at NotFoundErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/not-found-boundary.js:51:9)
at NotFoundBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/not-found-boundary.js:59:11)
at HotReload (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/react-dev-overlay/hot-reloader-client.js:319:11)
at Router (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/app-router.js:147:11)    at ErrorBoundaryHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:77:9)
at ErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:103:11)
at AppRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/app-router.js:384:13)
at Lazy
at Lazy
at ServerComponentWrapper (C:\Users\HP\informatician-2\node_modules\next\dist\server\app-render\create-server-components-renderer.js:90:31)
at ServerComponentWrapper (C:\Users\HP\informatician-2\node_modules\next\dist\server\app-render\create-server-components-renderer.js:90:31)
at InsertedHTML (C:\Users\HP\informatician-2\node_modules\next\dist\server\app-render\app-render.js:890:33)

Also, @s2sharpit I got this warning on my terminal you can check it out-
Warning: ReactStars: Support for defaultProps will be removed from function components in a future major release. Use JavaScript default parameters instead. at ReactStars (webpack-internal:///(sc_client)/./node_modules/react-rating-stars-component/dist/react-stars.js:41:41) at div at div at div at CardContent (webpack-internal:///(sc_client)/./components/BkCards/CardContent/CardContent.js:41:28) at a at LinkComponent (webpack-internal:///(sc_client)/./node_modules/next/dist/client/link.js:105:19) at div at eval (webpack-internal:///(sc_client)/./node_modules/swiper/react/swiper-slide.js:26:67) at div at div at eval (webpack-internal:///(sc_client)/./node_modules/swiper/react/swiper.js:40:98) at div at div at div at div at BkCards (webpack-internal:///(sc_client)/./components/BkCards/BkCards.js:51:69) at Lazy at div at section at InnerLayoutRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:226:11) at RedirectErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9) at RedirectBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11) at NotFoundBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/not-found-boundary.js:59:11) at LoadingBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:322:11) at ErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:103:11) at InnerScrollAndFocusHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:139:9) at ScrollAndFocusHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:213:11) at RenderFromTemplateContext (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/render-from-template-context.js:15:44) at Lazy at OuterLayoutRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/layout-router.js:331:11) at Lazy at m (webpack-internal:///(sc_client)/./node_modules/next-themes/dist/index.js:1:335) at exports.ThemeProvider (webpack-internal:///(sc_client)/./node_modules/next-themes/dist/index.js:1:3636) at ThemeProvider (webpack-internal:///(sc_client)/./components/theme/theme-provider.jsx:13:26) at Lazy at body at html at RedirectErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:72:9) at RedirectBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/redirect-boundary.js:80:11) at ReactDevOverlay (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/react-dev-overlay/internal/ReactDevOverlay.js:70:9) at NotFoundErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/not-found-boundary.js:51:9) at NotFoundBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/not-found-boundary.js:59:11) at HotReload (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/react-dev-overlay/hot-reloader-client.js:319:11) at Router (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/app-router.js:147:11) at ErrorBoundaryHandler (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:77:9) at ErrorBoundary (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/error-boundary.js:103:11) at AppRouter (webpack-internal:///(sc_client)/./node_modules/next/dist/client/components/app-router.js:384:13) at Lazy at Lazy at ServerComponentWrapper (C:\Users\HP\informatician-2\node_modules\next\dist\server\app-render\create-server-components-renderer.js:90:31) at ServerComponentWrapper (C:\Users\HP\informatician-2\node_modules\next\dist\server\app-render\create-server-components-renderer.js:90:31) at InsertedHTML (C:\Users\HP\informatician-2\node_modules\next\dist\server\app-render\app-render.js:890:33)

Yaa, I got the error. Fixing it.