Library doesn't compile with default-features=false

Describe the Bug
Library doesn't compile without default features.
Steps to Reproduce
Either add wasm-bindgen as dependency to a project:
wasm-bindgen = { version = "0.2", default-features = false }

Or git clone the repo and then do
cargo check --no-default-features

Expected Behavior
Crate is expected to compile with any set of chosen features, including when all features are off.
Actual Behavior
It fails to compile because the code uses std when std feature is disabled.
Compilation error message

error[E0432]: unresolved imports `crate::convert::VectorFromWasmAbi`, `crate::convert::VectorIntoWasmAbi`
  --> src/convert/slices.rs:13:22
   |
13 | use crate::convert::{VectorFromWasmAbi, VectorIntoWasmAbi};
   |                      ^^^^^^^^^^^^^^^^^  ^^^^^^^^^^^^^^^^^ no `VectorIntoWasmAbi` in `convert`
   |                      |
   |                      no `VectorFromWasmAbi` in `convert`
   |
help: a similar name exists in the module
   |
13 | use crate::convert::{RefFromWasmAbi, VectorIntoWasmAbi};
   |                      ~~~~~~~~~~~~~~
help: a similar name exists in the module
   |
13 | use crate::convert::{VectorFromWasmAbi, OptionIntoWasmAbi};
   |                                         ~~~~~~~~~~~~~~~~~

error[E0433]: failed to resolve: use of undeclared crate or module `std`
    --> src/lib.rs:1349:23
     |
1349 |             let msg = std::format!(
     |                       ^^^ use of undeclared crate or module `std`

error[E0433]: failed to resolve: use of undeclared crate or module `std`
    --> src/lib.rs:1818:35
     |
1818 |                 crate::throw_str(&std::format!("{:?}", e));
     |                                   ^^^ use of undeclared crate or module `std`

error[E0433]: failed to resolve: use of undeclared crate or module `std`
    --> src/lib.rs:1705:5
     |
1705 |     std::thread_local! {
     |     ^^^ use of undeclared crate or module `std`

error[E0433]: failed to resolve: could not find `externref` in the crate root
    --> src/lib.rs:1702:16
     |
1702 |         crate::externref::link_intrinsics();
     |                ^^^^^^^^^ could not find `externref` in the crate root

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:190:27
    |
190 |               type Anchor = Box<[$t]>;
    |                             ^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:193:54
    |
193 |               unsafe fn ref_from_abi(js: WasmSlice) -> Box<[$t]> {
    |                                                        ^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:194:18
    |
194 |                   <Box<[$t]>>::from_abi(js)
    |                    ^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `WasmMutSlice` in this scope
   --> src/convert/slices.rs:199:24
    |
199 |               type Abi = WasmMutSlice;
    |                          ^^^^^^^^^^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `MutSlice` in this scope
   --> src/convert/slices.rs:200:27
    |
200 |               type Anchor = MutSlice<$t>;
    |                             ^^^^^^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `WasmMutSlice` in this scope
   --> src/convert/slices.rs:203:44
    |
203 |               unsafe fn ref_mut_from_abi(js: WasmMutSlice) -> MutSlice<$t> {
    |                                              ^^^^^^^^^^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `MutSlice` in this scope
   --> src/convert/slices.rs:203:61
    |
203 |               unsafe fn ref_mut_from_abi(js: WasmMutSlice) -> MutSlice<$t> {
    |                                                               ^^^^^^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:204:33
    |
204 |                   let contents = <Box<[$t]>>::from_abi(js.slice);
    |                                   ^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0433]: failed to resolve: use of undeclared type `JsValue`
   --> src/convert/slices.rs:205:26
    |
205 |                   let js = JsValue::from_abi(js.idx);
    |                            ^^^^^^^ use of undeclared type `JsValue`
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider importing this struct
    |
4   + use crate::JsValue;
    |

error[E0422]: cannot find struct, variant or union type `MutSlice` in this scope
   --> src/convert/slices.rs:206:17
    |
206 |                   MutSlice { contents, js }
    |                   ^^^^^^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:212:27
    |
212 |               type Anchor = Box<[$t]>;
    |                             ^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:215:59
    |
215 |               unsafe fn long_ref_from_abi(js: WasmSlice) -> Box<[$t]> {
    |                                                             ^^^ not found in this scope
...
222 | / vectors! {
223 | |     u8 i8 u16 i16 u32 i32 u64 i64 usize isize f32 f64
224 | | }
    | |_- in this macro invocation
    |
    = note: this error originates in the macro `vectors` (in Nightly builds, run with -Z macro-backtrace for more info)

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:355:19
    |
355 |     type Anchor = Box<str>;
    |                   ^^^ not found in this scope

error[E0433]: failed to resolve: use of undeclared crate or module `mem`
   --> src/convert/slices.rs:359:9
    |
359 |         mem::transmute::<Box<[u8]>, Box<str>>(<Box<[u8]>>::from_abi(js))
    |         ^^^ use of undeclared crate or module `mem`
    |
help: consider importing one of these items
    |
4   + use core::mem;
    |
4   + use crate::mem;
    |

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:359:26
    |
359 |         mem::transmute::<Box<[u8]>, Box<str>>(<Box<[u8]>>::from_abi(js))
    |                          ^^^ not found in this scope

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:359:37
    |
359 |         mem::transmute::<Box<[u8]>, Box<str>>(<Box<[u8]>>::from_abi(js))
    |                                     ^^^ not found in this scope

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:359:48
    |
359 |         mem::transmute::<Box<[u8]>, Box<str>>(<Box<[u8]>>::from_abi(js))
    |                                                ^^^ not found in this scope

error[E0412]: cannot find type `Box` in this scope
   --> src/convert/slices.rs:365:19
    |
365 |     type Anchor = Box<str>;
    |                   ^^^ not found in this scope

error[E0425]: cannot find value `GLOBAL_EXNDATA` in this scope
    --> src/lib.rs:1711:9
     |
1711 |         GLOBAL_EXNDATA.with(|data| {
     |         ^^^^^^^^^^^^^^ not found in this scope

error[E0425]: cannot find value `GLOBAL_EXNDATA` in this scope
    --> src/lib.rs:1718:9
     |
1718 |         GLOBAL_EXNDATA.with(|data| {
     |         ^^^^^^^^^^^^^^ not found in this scope

error[E0433]: failed to resolve: use of undeclared crate or module `std`
    --> src/lib.rs:1814:13
     |
1814 |     impl<E: std::fmt::Debug> Main for &mut MainWrapper<Result<(), E>> {
     |             ^^^ use of undeclared crate or module `std`
     |
help: consider importing one of these items
     |
1430 +     use core::fmt;
     |
1430 +     use crate::fmt;
     |
help: if you import `fmt`, refer to it directly
     |
1814 -     impl<E: std::fmt::Debug> Main for &mut MainWrapper<Result<(), E>> {
1814 +     impl<E: fmt::Debug> Main for &mut MainWrapper<Result<(), E>> {
     |

Yeah, wasm-bindgen's no_std support has been broken for a while: see https://github.com/rustwasm/wasm-bindgen/issues/2689#issuecomment-933526660.

I'm happy to review a PR making the std feature no-op.

This was fixed in https://github.com/rustwasm/wasm-bindgen/pull/4005.


Bad Request

Hey guys, I get a bad request returned when trying to authenticate. Have you experienced this issue? Know how to fix?
[root@bastion-prod ~]# onelogin-aws-login
Onelogin Username: evan.furman
Onelogin Password:
Traceback (most recent call last):
  File "/usr/local/bin/onelogin-aws-login", line 26, in <module>
    api.save_credentials()
  File "/usr/local/lib/python3.4/site-packages/onelogin_aws_cli/__init__.py", line 140, in save_credentials
    self.assume_role()
  File "/usr/local/lib/python3.4/site-packages/onelogin_aws_cli/__init__.py", line 115, in assume_role
    self.get_saml_assertion()
  File "/usr/local/lib/python3.4/site-packages/onelogin_aws_cli/__init__.py", line 86, in get_saml_assertion
    res = self.request("api/1/saml_assertion", headers, params)
  File "/usr/local/lib/python3.4/site-packages/onelogin_aws_cli/__init__.py", line 57, in request
    raise Exception("Error: {}".format(res.json()))
Exception: Error: {'status': {'code': 400, 'message': 'bad request', 'type': 'bad request', 'error': True}}

Thanks!

I was futzing around with parameters to see what could cause this and the only way for me to get this to happen was to blank out the subdomain and/or app id.  Can you check that those are set correctly?

Closing this out - let me know if you can repro


Update builds and patches for FFmpeg 6.1

The latest stable release of FFmpeg is 6.1, and some distros (e.g. Arch, OpenMandriva Rolling) have already updated to FFmpeg 6.1.
Currently the repo has patches for 6.0 but not 6.1, and the Latest Auto-Build (2023-11-21 14:09) is 6.0.

Done.


Add support for consensus pool:common and pool:fee-accumulator

Currently, only the runtime's common pool and fee accumulator is resolved in https://github.com/oasisprotocol/oasis-sdk/blob/main/client-sdk/go/helpers/address.go. Add support for consensus common pool and fee-accumulator as well by passing the ParaTime instance to ResolveAddress(). If the instance is defined, then use the ParaTime's address, otherwise return the consensus address.
Perhaps it would make sense to migrate most of the helpers/address.go to Oasis CLI and get rid of all the pools, separators and other CLI-related literals?

Yes, I agree that this should be moved to the CLI.


obtaining timeRangeSelect options dynamically

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area tests

What this PR does / why we need it:
These modifications allow the dynamic obtaining of the list of options to be shown in the TimeRangeSelect component.
The values, rather than being hard-coded, are generated based on a builderConfig object. The function to which it is provided takes care of the construction of both the value and the appropriate label.
Which issue(s) this PR fixes:
The insertion/removal of new options is as immediate as adding/removing an integer from the appropriate property in the builderConfig object.

Fixes #
Special notes for your reviewer:

The changes allow the addition of options that refer to the seconds.

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

a37def3 init

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign cpanato after the PR has been reviewed.
You can assign the PR to them by writing /assign @cpanato in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@didof what's the status of this PR? We're planning to release v1.0.0 this week and this PR blocks it. Thanks.

Excuse me, why this got closed?

I am gonna send it again (adding some of your suggestions).


Doc fixes

Original pull request by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

A few documentation errors and glitches have been corrected in this PR.

Documentation issues fixed.

Further documentation errors fixed.

Some more documentation issues fixed.

\brief expects empty line after paragraph! (this \ingroup commands are missing a preceding empty line to end the brief paragraph.)

Exclude SbTypeInfo.h from documentation generation.

Superfluous img tags removed.

Replaced some references to coin3d.org with bitbucket.org/Coin3D

reference to coin-discuss list on groups.google.com

Extraction of anonymous namespaces disabled. (As anonymous namespaces are internal implementation detail they should IMHO not be added to the public API documentation)

Comments very welcome on this PR,
Cheers, Volker

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

Looks like a mountain of work. Thanks.
Is the “merge” button present for you in the top right?

Original comment by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

Most stuff was corrected by a simple regex. But yes, other issues needed some more evaluation :).
Unfortunately the merge button is still missing. The repo shows "Access level: Read" only. I think that's why the merge capabilities are disabled.
Cheers, Volker

Original comment by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

Yippie A Yeah, it showed up next to the Edit button! Many Thanks, @veelo
Cheers, Volker

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

You’re right, the user and group access settings in the repository settings were on “read”. Just switched to “write”. Does that help? I’ll visit every repository and change them.

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

ok great

Original comment by Bastiaan Veelo (Bitbucket: veelo, GitHub: veelo).

@VolkerEnderlein You probably know this, but I am getting failure mails from AppVeyor. Looks like the images just lack doxygen.
https://ci.appveyor.com/project/VolkerEnderlein/coin/build/4.0.0-default-ci-46

Original comment by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

Thank you @veelo . Yes, I am aware of it. I scheduled the fix for this evening. Yesterday there were some issues on BitBucket with pushing to the repos from https. Those seem to be solved now. There is another small fix in the pipeline regarding the MacOS X build problems.


Add support for kid-less jwks signature validation

The documentation states that JWKS mandates a kid claim, but it seems that this is not the case in both the JWS and JWK RFCs, even though there's a statement that says that kid is used to match a JWS, it does not indicate that is a requirement.
I'm implementing application-based access using Teleport and they do not add a kid claim in the header or in JWKS. I'm able to correctly validate JWKS with a stripped-down version of this library.
What do you think about allowing this use case?

Also, I've noticed that we are actually not 100% compliant with the specification... there could be duplicated kids in a set. In that case, we should ALSO match the kty parameter as per the specification.

That makes sense.

I am gathering feedbacks here and in other issues about possible breaking changes so that we can think about a 2.0 version here. I will open an issue for that so that it gives a bit more clarity of what I am currently thinking.
In any case, I can't promise a schedule for this kind of fix. I want to address this properly now that I have more experience using all kinds of different implementations (thanks Open Finance Brasil... ).

In our code where we use joken_jwks we have also run into problems with an OIDC provider not adding the kid to their id token.
This is because it is optional in the OIDC specs and they only have one key.
So we are interested in a fix for this as well.
One possible solution could be to allow not providing a kid claim only when exactly one key is present in the keys list.


Add in Toggle Market Button to appear on markets page

Created in response to: https://github.com/AugurProject/augur/issues/189

Thanks for taking the time to put this together.  It's a good start, but there are a few problems that jump out at me:

The toggle switch could use some kind of label.  Right now it's hard to tell what it does prior to clicking on it.
Clicking the toggle triggers a full market reload.  This isn't obviously a problem right now, because the total number of markets is relatively small and it's on a hosted node.  But, it would be much more efficient to just filter the markets that are already in the data store, rather than re-fetching all the markets from scratch.
parseCache is not a good place to do the filtering, because (as its name suggests) this method is only invoked when loading data from the MongoDB.  To make this work for local (direct-to-geth) connections, you'd need to either create a second equivalent block of code somewhere in the loadMarkets code, or (preferably) insert this logic somewhere else where it doesn't care about where the data came from and doesn't couple the toggle to the initial loading logic.
It looks like you're using mMarkets both as a method and as a variable (to store the toggle's state).  This is confusing and you should use multiple labels instead of just one.  A bigger issue is that state shouldn't be saved in the actions -- usually you should use the stores for this, but if you need to it's ok to save some state info within the component (if the state does not need to persist after the component unloads).  But don't store it in the action!  Stuff like this window.flux.actions.market.mMarkets = true; should never ever ever be happening in the components.

Leaving this PR open for now.  (This code will likely need a rewrite before it's ready to merge.)

what about something like an open sign/closed sign icon set?
so I know what you're saying, I have different code that was based on what you mentioned before but every time an action happens it uses the parsecache to update everything so when I used my function to toggle, it would still randomly run the parsecache function and erase what I filtered away from the store.  I'd prefer it I could scrap this portion or make it function for a local node which seems ideal long term.

toggleMarketsOn: function() {
  var self = this;
  var storedMarkets = self.flux.store('market').getState().markets; // from marketStore
  var currentPeriod = 191; //flux.store('branch').getState().currentBranch.currentPeriod;
  var markets = {};

  for (var market in storedMarkets) {

      var marketExpires = storedMarkets[market].tradingPeriod.toNumber();

      if (!storedMarkets.hasOwnProperty(market)) continue;
      if (currentPeriod >= marketExpires) delete storedMarkets[market];
      markets = storedMarkets;

  }
 // save markets to MarketStore
    self.dispatch(constants.market.LOAD_MARKETS_SUCCESS, { markets:  markets });
    console.log(Object.keys(markets).length + " Markets Found");
}
   ```

* as for replacing window. I'm reading what you've shared now, thx!


Can you give some info on how to use this with Swift?

I installed the framework using cocoaPods , but I still cannot import nor create a bridging header. Could you add some direction in the Readme.md?

+1 for this question. I tried to import it with the following Bridging-Header but still got Could not build module error.
#import <MZFormSheetPresentationController/MZFormSheetPresentationController.h> // error
#import <MZAppearance/MZAppearance.h> // OK

I wish there were some instructions on README.

Use CocoaPods if you not sure how to integrate it


Document exact spec lifeccyle

Description
Write up the details of how the spec lifecycle is implemented

For new specs

Who creates the topic branch
Who tags the branch once changes are checked in
Who updates the release metadata when an SDK or documentation drop is released
Who merges the topic branch when all criteria have been met

For spec edits

Who creates the tag after a spec edit

Already done in the adx wiki


k8s: don't use default image pull policy of always for busybox images.

Since we're using the busybox image from dockerhub to do the initial k8s pod creation and by default k8s uses image pull policy of always, we could reach the dockerhub unauthenticated pull limit if the user haven't defined a docker auth in the agola config definition.

Instead of forcing the policy just leave the decision to k8s and by default don't use busybox:latest but busybox:stable is the k8s policy will be the default for non latest images (IfNotPresent)

Implemented in #270. Also implemented the same logic also in the docker executor #269


Nuxt + Vuetify production mode loading css late

Version
v2.8.1
Reproduction link
https://github.com/amritk/vuetify-nuxt-repro
Steps to reproduce
Grab the repo, build and run in production mode. Make sure to have the network tab open to disable cache. You can see as you refresh that some vuetify styles load late and the elements change.
What is expected ?
There should be no jump in style as they should be loaded already from nuxt SSR.
What is actually happening?
The styles seem to be loaded via javascript so you can see the elements jump.
Additional comments?
I have also tested this with the latest vuetify 2 beta, the problem still occurs. As I wasn't sure if this was a vuetify or nuxt bug I did post it there as well.

This bug report is available on Nuxt community (#c9394)

Here is a gif of what happens on my app I'm trying to take to production.

As you can see here, there are a few style blocks that are added on the client but are not there on the server. How do I ensure these styles are loaded on the server?
Server:

Client:

I've found a lot of CSS packages only work with nuxt in 'spa' mode that you can edit in the nuxt config, if you can isolate the components in question you can also wrap them in the  tag. This was the case with bootstrap among others

hey @edmundpf thats good for when a component is breaking on the server side. My problem however is the opposite: styles are missing server side that should be there. I'm not sure how to configure nuxt to show these styles.

Alright its the v-layout styles loading late. Any way I can pre-load them somehow?

Closing as this is a vuetify issue


[Developer Portal] parameters are not displayed when catalog items with parameters are selected

Instead of displaying the parameters for a catalog item that requires parameters, this message is shown: This catalog item requires no parameter inputs, and will be created immediately.

The catalog item does require parameters:

Deploying from az cli works as expected.

Hi @nb-atudose! The reason for this the UI creation scenario is only able to know about parameters specified in the manifest file. If you add the parameters that you see in the ARM template to the manifest, that data can be input via the UI.

Here is an example of a manifest.yml with some basic parameters:
name: AppConfig
summary: This is an App Configuration deployment.
description: Deploys an App Config.
templatePath: azuredeploy.json
parameters:
- id: "name"
  name: "name"
  description: "Name of the App Config"
  default: ""
  type: "string"
  required: false
- id: "location"
  name: "location"
  description: "Location to deploy the environment resources"
  default: "[resourceGroup().location]"
  type: "string"
  required: false
runner: arm

Thank you! It would be a good idea to specify this in the documentation :grin:


About "open with MS word"

It seems  and table{width:100%;} don't work as expected when the output is opened with MS word, however, they work as expected when output is saved as PDF or HTML file. The script is as below, please help to check if any errors in my file. Or, is it the problem of my MS word 365 (version of 2016)?
'
'1. Line Main Protection Setting List
'1.1 System settings
'
'
'
' No.
' Name
' Range
' Value
' Unit
' Description
'
'
'
'
'1
'ActiveGrp
'1~30
'1
'&nbsp
'Current active setting group
'
'
'1
'Grp
'1
'1
'&nbsp
'group
'
'
'
'1.2 Line settings
'
'
'
' No.
' Name
' Range
' Value
' Unit
' Description
'
'
'
'
'1
'Z1L
'(0.05~655)/In
'Z_L1_sec
'ohm
'Positive-sequence impedance of the whole line (secondary value)
'
'
'
'1
'Z0L
'(0.05~655)/In
'1
'ohm
'zero
'
'
'

Hi,
The native output format of the Calcpad output is Html. That is why everything works there at first.
Then the Html is converted to Word, but not all CSS and Html features are supported, only the most important ones.
So, if something does not work, it is simply because it is not supported. It is not possible at this moment to support for all CSS and Html features. They are too many, so it would be a project larger than the entire Calcpad.
For pdf we use wkhtmtopdf that support more features. Unfortunately, for MS Word there is no such FOSS library that works for us, because they cannot create native Word equations and this is more important than some extra formatting.

Thank you so much. I will prefer save as pdf. it's ok
.

Yes, PDF is best if you do not need to change anything afterwards.
On the other side Word allows you to modify text and formulas but does not support all the formatting. Anyway, this is not such a big trouble, since you can use Word for formatting as well. It is even better than Calcpad for that purpose.


Deregister was removing the blackbox-list.txt file

In the process of testing blackbox out for our own use I found that the deregister command wipes out the entire keyrings/live/blackbox-files.txt .
This removes that action and instead adds the file to be committed to git.  I also added some removes of the unencrypted file and the encrypted file.  However if that wasn't what was intended I can remove that bit.

Thanks for spotting this bug. I decided to fix it slightly differently, but my change is based on yours. Thank you for raising this issue!
See https://github.com/StackExchange/blackbox/commit/c0dda22c9cc169df1e69131ea7350c109466322b


Add a blanket implementation for CustomSigFn

Adds a blanket CustomSignatureFunction implementation for closures, for we don't want to add a description.
Drops the name and misc parameters, since they can be taken directly when creating the function along with the OpDef.

So we can just do:
let name = "MyOp".into();
let description = "".into();
let args = vec![];
let mut misc = HashMap::new();

let sig: Signature = todo!(); // Some complex computation
let signature = move |_args: &[TypeArg]| {
    Ok((sig.input.clone(), sig.output.clone(), ResourceSet::new()))
};

OpDef::new_with_custom_sig(name, description, args, misc, signature)

Adds a blanket CustomSignatureFunction implementation for closures, for we don't want to add a description.

Yes, very neat

Drops the name and misc parameters, since they can be taken directly when creating the function along with the OpDef.

Ideally not - can you just make the blanket CustomSigFunc impl take and ignore those parameters?
My thinking is that if you might not be using a lambda - rather, that misc could be extra data that defines the op. So this would give yet another way of defining TKET1 ops: you have a Resource that has an OpDef for each different TKET1 op, but they all use the same CustomSigFunc which expects a serialized TKET1 op in the misc data.

Since OpDef always creates dyn CustomSignatureFunctions we can always do that specialization at initialization time.
In the case you mention, you can just create a TKET1CustomSigFn::new(name, misc) when creating the OpDef since you already have the exact same data there.
Doing only for the blanket impl with reduced parameters is a bit annoying. We can only define a single blanket impl (because Fn is a trait, so multiple Fns can clash) so it makes more sense to have it match the signature of compute_signature.

I think that same argument says we should also remove misc from try_lower and then we might as well drop misc altogether? (If it's only for ops internal to the toolchain, rather than 3rd-party ops, then there's no need for it to go in the YAML!).
I don't see a problem with a CustomSigFunc impl only for Functions taking just the TypeArgs, note. (Sure, you could have variations, but I'm willing to bet that that's a common case.)

I re-added the parameters in the trait method, but left them out in the blanket impl on closures as suggested.


feat: adapt for wokwi projects

Re-adding the fpga action that was removed by the original PR. Since this wasn't merged yet, I'll do a squash & force-push.


Hey, I want to contribute in the styling of the project.

Opensource Programs section elements are not equally sized.
Site logo Overflowing in smaller display size.

Thanks for raising this issue.
/assign @chaman-rawat


Remove unused $size parameter

$size is not currently being used in the make-col-ready() mixin

$columns either, also with $gutter in make-col() mixin.
They aren't needed.


Replace submenus with explore pages

Describe the enhancement you'd like
Right now, we use submenus to navigate to the different layouts. This is hard to navigate on mobile and takes additional clicks. It would be a good idea to replace these submenus with explore pages you can use to navigate to the subpages.
Describe why this will benefit the LibrePhotos
Better navigation on mobile and fewer clicks.

Already documented in #398


LightGBM feature selection and low model size

So I build a Random Forest regression model earlier, model size was around 200mb with HPT and pruning.

Now that I'm trying with lightGBM, a regression model, without HPT I am getting same high accuracy (rmse). I used default parameters only . Is lightGBM so effective compared to RF ?

Size of saved lightGBM model is 250kb, does that sound right for typical lightGBM model, or I am making some mistake ?

Is there a way for feature selection in lightGBM (top features wrt to target) ?

Below is the sample code
X = dataset.data; y = dataset.target
X_train, X_test, y_train, y_test = train_test_split(X, y, test_size=0.30)

model = ltb.LGBMRegressor()
model.fit(X_train, y_train)
print(); print(model)

expected_y  = y_test
predicted_y = model.predict(X_test)

print(metrics.r2_score(expected_y, predicted_y))
print(metrics.mean_squared_log_error(expected_y, predicted_y))

filename = 'lightgbm_model.sav'
pickle.dump(model, open(filename, 'wb'))

New to this model, hence questions.

Hi @ninenerd , thanks for using LightGBM! Apologies for our delayed response.

Now that I'm trying with lightGBM, a regression model, without HPT I am getting same high accuracy (rmse). I used default parameters only . Is lightGBM so effective compared to RF ?

Performance is dependent on the problem and data, so we can't make a broad claim about LightGBM always being more effective than any other technique. LightGBM has been used in many winning solutions for machine learning competitions (https://github.com/microsoft/LightGBM/tree/c20cce0474ceba0a3239e09782f50aed1050bc38/examples#machine-learning-challenge-winning-solutions).
If you want to go very deep into how LightGBM achieves good performance in some tasks, you can see the original LightGBM paper.

Size of saved lightGBM model is 250kb, does that sound right for typical lightGBM model, or I am making some mistake ?

Are you doing work where the size of the model on disk is very very important? Like deploying to a very small machine? If not, I would not worry too much about this. 250kb does not sound very large  to me. If that size is a problem for you, please give use more details in a separate issue.

Is there a way for feature selection in LightGBM (top features wrt to target) ?

Like other tree-based supervised learning models, LightGBM has feature selection built into it. Features that don't help explain the target will never be chosen for splits.
If you want to examine feature importance  after a trained model, see model.feature_importances. You can also explore plot_importances() (https://github.com/microsoft/LightGBM/blob/c20cce0474ceba0a3239e09782f50aed1050bc38/python-package/lightgbm/plotting.py#L29)
import lightgbm as lgb
from sklearn.datasets import load_breast_cancer
from sklearn.model_selection import train_test_split

X, y = load_breast_cancer(
    return_X_y=True,
    as_frame=True
)

X_train, X_test, y_train, y_test = train_test_split(
    X,
    y,
    test_size=0.1,
    random_state=42
)

gbm = lgb.LGBMClassifier(
    n_estimators=50,
    colnames=list(X.columns)
)

gbm.fit(
    X_train,
    y_train,
    eval_set=[(X_test, y_test)],
    early_stopping_rounds=5,
    verbose=False,
)

print(gbm.feature_importances_)

from lightgbm.plotting import plot_importance
plot_importance(gbm, color='r', title='t', xlabel='x', ylabel='y')

I'm going to close this issue, because we try to use the Issues list to track work that needs to be done, like fixing bugs and adding new features. If you want to get more familiar with LightGBM, please consult the documentation. If you find that something is missing from the documentation that could help you, please open a new issue and request it or open a pull request that proposes documentation changes.


News articles are sometimes outside of the allowed parent

Describe the bug
First off - I've not been able to replicate this, though I've seen this happen in production twice.
News articles are occasionally created (along with the year & month) folder under the site root instead of the allowed parent (News).
In this latest occurrence, the year and month folders had already been correctly created under 'News' as part of previous article creations.
_Using version: Umbraco version 10.2.0, DateFolders: 10.1.0
This is our config:
"DateFolders": {
"CreateDayFolders": false,
"OrderByDescending": true,
"FolderDocType": "dateFolder",
"ItemDocTypes": [ "newsArticle" ],
"AllowedParentDocTypes": [ "news" ]
},
Any tips that might help troubleshoot this much appreciated.

Hi @rosspetev ! Thank you very much for getting in touch with us. Your report is very clear. We're going to do some investigating and come back to you when we know something or if we have more questions.

It's my understanding that this isn't the first time that we hear or see this, but as of yet, we're unable to reproduce this behaviour and therefore unable to provide a fix or workaround at the moment.
Possible causes for this issue include, but are not limited to:

Timeouts on the database or other connection related issues
Errors on other notification handlers or cancellation by other notification handlers, preventing the datefolders plugin from performing.

Have you noticed any of these errors on your installation?


Fixed matched route name in case when there are no allowed methods

This fix is to conform behaviour with zend-expressive-aurarouter
and zend-expressive-fastrouter, we should have matching path in that case

Thanks, @webimpress


gist does not work

With the current version of http://ethereum.github.io/browser-solidity/ refuse to publish the files to gist and refuse to load

http://ethereum.github.io/browser-solidity/?#gist=1b71fbff29df3306540b
https://chriseth.github.io/browser-solidity/?gist=https://gist.github.com/anonymous/b28692c94b053febe27bbb3692bb31ad
http://ethereum.github.io/browser-solidity/?gist=https://gist.github.com/anonymous/b28692c94b053febe27bbb3692bb31ad

Chrome show this error when I would like to publish to Gist:
app.js:15945 Uncaught TypeError: files.list(...).filter is not a function
at packageFiles (app.js:15945)
at HTMLButtonElement. (app.js:15955)
at HTMLButtonElement.dispatch (app.js:10576)
at HTMLButtonElement.elemData.handle (app.js:10552)

With firefox in Linux, I can start with this URL
https://ethereum.github.io/browser-solidity/#gist=3c9bd8182bfb5b9757f18de5fd364838&version=soljson-v0.4.9+commit.364da425.js
But not with Chrome in Windows or Linux.
I both, the Javascript console signal two errors:

file.set is not a function
file.list(...).filter is not a function

It's impossible to publish files in Gist :-(


Added a sublime-project file to version control, so we can share info…

… about what folders to ignore, etc.
Set this up to ignore files that are in the .gitignore.

This is great. I'll add whitespace, tabs, and end-of-file preferences to this. Syncing up on whitespace and the like makes PRs a little easier to review since there's no whitespace noise in them.


refactor: replace/remove deprecated method calls

This:

Bumps tslint to the latest ^5.9.1;
Adds deprecation rule to the tslint.json;
Replaces all usages of deprecated methods (in majority tslint methods);

@rafaelss95 thanks for the cleanup! Would you check why the build is failing?

@mgechev so... that was what I asked above, if I change in these 2 places I mentioned, the tests break, I really don't know why.

ERROR: /Users/travis/build/mgechev/codelyzer/src/angular/sourceMappingVisitor.ts[107, 18]: createFailure is deprecated: Prefer `addFailureAt` and its variants.
ERROR: /Users/travis/build/mgechev/codelyzer/src/angular/templates/basicTemplateAstVisitor.ts[186, 53]: addFailure is deprecated: Prefer `addFailureAt` and its variants.

I guess we should not use deprecated methods.

I think you don't understand what I mean. I'm trying to say that if I change these deprecated calls it break some tests. See https://github.com/mgechev/codelyzer/pull/587#issuecomment-385220278

@mgechev I've pushed the changes for those leftovers. Now you can see the full log error in travis.

bump @mgechev.

@rafaelss95 will take a look in a few minutes.


Crashes On Server Restart

When server restarts, app stops responding

Corrected in version <IP_ADDRESS>


How to connect chat with AI agency in Telegram and WhatsApp?

How can I use Telegram bot or Watsapp chat instead of Gradio chat so that only @User message is shown?

You would first deploy your agents as an API and then integrate this endpoint with Telegram or WhatsApp webhooks. We will add this to our SaaS and release some templates in our course later, however, it will never be added directly into the framework.
In the meantime, I recommend finding some tutorials on how to create telegram/whatsapp bots and taking it from there.


Calculation of per-example accuracy

First of all, I would like to thank you for this incredible work!
Seems that you only present the robustness evaluation per attack in the testing. May I know how do you calcualte the per-example accuracy  (A_rob in the paper)?
Thanks.

Right. The evaluation code can only report the accuracy under each attack. If you want to calculate the per-example accuracy, you need to save the classification results for each test sample against all attacks, and then count the number of samples that are classified correctly under all attacks.

I see, thanks a lot.
By the way, may I ask how do you choose the training epoch to stop the training without validation set?

We adopted the setting in TRADES (use the 75th epoch checkpoint). The paper "Overfitting in Adversarially Robust Deep Learning" discusses more on this.

I see, thanks. One last question:
in the method of adt_expam, I find you calculate mean and std of rand_noise by using the first 3 channels of phi as follows:
adv_mean = phi[:, :3, :, :]
adv_std = F.softplus(phi[:, 3:, :, :])
But it is hard to say the first 3 channels of phi correspond to the input image, right? So I just try:
adv_mean = phi
adv_std = F.softplus(phi)
The result degrades a lot. May I further figure it out?
Thanks.

You cannot get adv_mean and adv_std with a single output phi because they should not be correlated. It's natural to use the first three output channels to get adv_mean and the last three channels to get adv_std since they will depend on different weights in the output layer. This way of getting adv_mean and adv_std is similar to training variational auto-encoders.

Got it, thanks a lot. I may close this issue.


Add an existing LB to an existing VMSS instance

Related command
This should fall under az vmss update command
Is your feature request related to a problem? Please describe.
Currently, on portal users can attach an existing load balancer to an existing vmss instance. This feature doesn't exist for CLI
Describe the solution you'd like
A CLI command that allows users to attach an existing LB to an existing VMSS instance, similar to how the portal experience is.
Describe alternatives you've considered
Portal, but the portal experience isn't scalable for customers
Additional context

The portal experience is shown in the screen shot attached. The CLI experience should accomplish the same task and reach parity with the portal experience.

@zhoxing-ms for awareness

@mahipdeora Since this is an internal feature request rather than a bug and we need to know some necessary information (such as REST service, Swagger link, command design...) , could you please use this template service_team_request to help us create a feature request?
After you create the new feature request, we will evaluate it's priority and workload, and add it to our development plan for the subsequent sprints, thanks~

@mahipdeora Could you please use the template  service_team_request to help us supplement the necessary information?

Hi @zhoxing-ms, I found a workaround using CLI (will have a doc posted about this soon). I will do further testing tomorrow, and if it works, we can close this.

Hi @zhoxing-ms, I just tested the CLI command I found, and it works. There is no need to create a new CLI command. I will create documentation on this use case. Thanks for your help.


Add CI and Testcases

Add 2 steps on CI.yml (build, test)
Add 105 Testcases (C/C++)
Add build.sh script
Add test-plsan.sh script

Currently, main branch doesn't have function that detect memory leaks, so test-plsan.sh step failed.

cmake dosen't work in CI now. i don't know about this error ;(
Check below:
-- The C compiler identification is GNU 11.4.0
-- The CXX compiler identification is GNU 11.4.0
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /usr/bin/cc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /usr/bin/c++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found ZLIB: /usr/lib/x8[6](https://github.com/hygoni/precise-leak-sanitizer/actions/runs/7656516812/job/20865024215#step:6:7)_64-linux-gnu/libz.so (found version "1.2.11")
-- Found LibXml2: /usr/lib/x[8](https://github.com/hygoni/precise-leak-sanitizer/actions/runs/7656516812/job/20865024215#step:6:9)6_64-linux-gnu/libxml2.so (found version "2.[9](https://github.com/hygoni/precise-leak-sanitizer/actions/runs/7656516812/job/20865024215#step:6:10).[13](https://github.com/hygoni/precise-leak-sanitizer/actions/runs/7656516812/job/20865024215#step:6:14)")
CMake Error at CMakeLists.txt:13 (include):
  include could not find requested file:

    AddLLVM

CMake Error at PreciseLeakSanitizer/CMakeLists.txt:1 (add_llvm_pass_plugin):
  Unknown CMake command "add_llvm_pass_plugin".

-- Configuring incomplete, errors occurred!
make: *** No targets specified and no makefile found.  Stop.
Error: Process completed with exit code 2.

I will fix this issue asap!


Using npm to install amplify will fail quietly if let run for ~5 mins

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
[X] I have removed any sensitive information from my code snippets and submission.

How did you install the Amplify CLI?
npm i -g @aws-amplify/cli
If applicable, what version of Node.js are you using?
v16.18.0
Amplify CLI Version
10.2.3
What operating system are you using?
Ubuntu
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made, just having issues installing Amplify.
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug
When managing Amplify installation through NPM, installation hangs for ~5 minutes, then fails quietly but stores a file with javascript in npm folder along with a symlink between amplify and that folder.
No binaries are ever stores and whenever any Amplify command is run app will hang saying "Downloading release from https://package.cli.amplify.aws/10.2.3/amplify-pkg-linux-x64.tgz"
Expected behavior
Expected to fail when trying to install binary files in the wrong folder location saying something like "this is not how you should be installing Amplify on an Linux machine, read the docs."
Reproduction steps
To recreate this issue I ran a linux virtual machine and tried to Amplify. I was using a virtual machine and running Linux Ubuntu 20.04
Prerequisites

Create a virtual machine
ssh and Install nvm ($ curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.38.0/install.sh | bash)
Use nvm to select and install Node with lts version (nvm install --lts, node --version v16.18.10)
check npm version ( npm --version, expected 8.19.2)
Install amplify, npm install -g @aws-amplify/cli . This will hang for some time ~5 minutes and then successfully exit
Try to run any amplify script (amplify --version) and you will get an attempt to install the binary.

GraphQL schema(s)
N/A
Project Identifier
n/a
Log output
Downloading release from https://package.cli.amplify.aws/10.2.3/amplify-pkg-linux-x64.tgz
Additional information
No response

not quite related but similar concerns https://github.com/aws-amplify/amplify-cli/issues/10610


upgrade hibernate-validator to 6.1.7.Final

Starting from 5.4.x, jersey version 2.31 will have transitive dependencies on HibernateValidator versions 6.1.2.Final. Upgrade HibernateValidator to 6.1.7.Final.

@confluentinc It looks like @xiaoyali97 just signed our Contributor License Agreement. :+1:
Always at your service,
clabot


Inquiry: Support for Google Sign-In Authentication System (not Google+)?

I received recent notification of the following:

Hello Google+ Developer,
We’re writing to let you know that as part of the sunset of the consumer version of Google+, we will be shutting down our Google+ APIs on March 7, 2019. As part of these changes, Google+ Sign-in has been fully deprecated and will also be shut down on March 7, 2019.
What do I need to know?
On March 7, 2019, all Google+ APIs and Google+ Sign-in will be shut down completely. This will be a progressive shutdown beginning in late January, with calls to these APIs starting to intermittently fail as early as January 28, 2019.....

The go on to say:

Note: If you see calls to people.get, these can be the result of using the Google+ Sign-In feature in your application, which is now fully deprecated and is being shut down. Developers should migrate from the Google+ Sign-In feature to the more comprehensive Google Sign-in authentication system.

Do you know if there are plans to support this using this library?

Hi aaron, I had not had plans to write a google auth provider myself, but that doesn't mean a patch won't get accepted.. Would you like to take a stab at it?


Add run-inference component for autolabeling

Right now, we manually label all run-inference issues and its easy for things to slip through the cracks (I've noticed a few different issues with this problem this morning). I'd propose we use this label for any run-inference issues we create going forward.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

retest this please

R: @yeandy @ryanthompson591 or @AnandInguva


NSURLSessionDownloadTask response data is not available for 403 status codes

I'm using AFURLSessionManager and an NSURLSessionDownloadTask to make a POST request to grab some JSON.
I'm using a downloadTask instead of a dataTask because that's what background session configurations require.
Because I'm using a background session configuration I'm relying on the session delegate methods rather than the task delegate methods.
If this particular request fails with a 403, I need to access the response body data (it contains details about what went wrong) and respond accordingly.
But in the case of 403, the setDownloadTaskDidFinishDownloadingBlock: is never called. The only delegate method called is the setTaskDidCompleteBlock:. Tracing this back through AFNetworking I see that the AFURLSessionManager's self.mutableData property is nil. Which means that I have no way to access the response body's data.
Snooping the response in Charles Proxy confirms that the response body is being sent to the device.
Difficult to tell if this is an AFNetworking issue or an Apple issue. Any help would be much appreciated. Thanks!

I'm using a downloadTask instead of a dataTask

That's why you're not getting data. responseData is nil for downloads, because the data is accumulated in a file instead. To see the data itself, look to the file path into which the response data was downloaded.

@mattt thanks for the quick reply. This seems like unexpected behavior because Apple forces us to use downloadTask in lieu of dataTask when using a background session. And in the event of failure (at least this 403 failure), the data is never downloaded to disk, so there's no file location to inspect.
In short, downloadTask failures never call the setDownloadTaskDidFinishDownloadingBlock:. Odd to omit this because response body is in the spec for 403 failures.
So just to clarify, seems like an Apple issue and not an AF issue?
Thanks again


[Bug]: Unable to start Tika server

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

Branch name
main
Commit ID
33eaf6f
Other environment information
docker install

Actual behavior
2024-05-11 10:55:37,125 [MainThread  ] [ERROR]  Unable to run java; is it installed?
[ERROR] [2024-05-11 10:55:37,125] [tika.startServer] [line:669]: Unable to run java; is it installed?
2024-05-11 10:55:37,125 [MainThread  ] [ERROR]  Failed to receive startup confirmation from startServer.
[ERROR] [2024-05-11 10:55:37,125] [tika.checkTikaServer] [line:601]: Failed to receive startup confirmation from startServer.
Traceback (most recent call last):
File "/ragflow/rag/svr/task_executor.py", line 141, in build
cks = chunker.chunk(row["name"], binary=binary, from_page=row["from_page"],
File "/ragflow/rag/app/naive.py", line 159, in chunk
doc_parsed = parser.from_buffer(binary)
File "/root/miniconda3/envs/py11/lib/python3.11/site-packages/tika/parser.py", line 65, in from_buffer
status, response = callServer('put', serverEndpoint, '/rmeta/text', string, headers, False, config_path=config_path, requestOptions=requestOptions)
File "/root/miniconda3/envs/py11/lib/python3.11/site-packages/tika/tika.py", line 532, in callServer
serverEndpoint = checkTikaServer(scheme, serverHost, port, tikaServerJar, classpath, config_path)
File "/root/miniconda3/envs/py11/lib/python3.11/site-packages/tika/tika.py", line 602, in checkTikaServer
raise RuntimeError("Unable to start Tika server.")
RuntimeError: Unable to start Tika server.
Expected behavior
No response
Steps to reproduce
extract excel file

Additional information
No response

file format error?
convert xls to xlsx

您好！我是莫洋，我已经收到您的来信了！

file format error? 文件格式错误？ convert xls to xlsx 将xls转换为xlsx

I fixed it by installing java in container of ragflow-server。


Titles ending in # are flagged as invalid anchors

Describe the bug
When you write a heading that ends with a #, the link validator flags it as an "invalid anchor".
Maybe it would be possible to configure specific words that should not be considered anchors?
To Reproduce

Add a heading ending in # -- e.g., "Coding in C#".
Run the link validator.

Expected behavior
Do not flag this as an invalid anchor.
How often does this bug happen?
Every time
System Info
No response
Additional Context
No response

Thanks for your report 🙌
I'm not sure a configuration would be the proper solution considering your report as I think this sounds more like a real issue and this should not get flagged or detected like an anchor.
Would you be able to provide a repro or an example of content that triggered the issue. I tried with the following content but did not manage to get an error:
## Heading ending with a#

Sentence ending with a#

[Link to heading ending with #](#heading-ending-with-a)

HTML link to heading ending with #

Oh how strange! This is the repo I've been working on https://github.com/splashkit/the-programmers-field-guide

Just cloned the repo and it seems the error are not related to headings ending with # but seems to indicates invalid links which are just the # character.
The 9 errors I get when building are:

src/content/docs/book/part-1-instructions/3-control-flow/1-concepts/06-statement-simple-structured.md
- [Assignment Statement](#) used to calculate a value and store it in a Variable.

src/content/docs/book/part-2-organised-code/3-structuring-data/0-overview.md
- [Enumeration](#): used to store one of a list of available options.
- [Record](#): used to store multiple fields in a single composite value.

and
Passing data to a [Function](#) or

src/content/docs/book/part-2-organised-code/4-indirect-access/1-concepts/02-01-pointer-use.md
- You can get the address of values in [Local Variables](#), [Global Variables](#), [Parameters](#), fields of [Records](#) and [Unions](#). Basically, you can get the address of any value you can read.

Ah, you're right! I'm so sorry for the brain fart. Must have completely misread the output. That teaches me for working late at night :)

No worries at all, glad we got to the bottom of this 🎉


chore: fix running tests on Windows

Trying to remove the elements that make tests not pass on Windows,
or tweaking the GitHub workflow so windows can pass (proving there
is a way to develop jsii on Windows).

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 142dd21fe3bc04e218916df569b0db687b614dfc
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 254b2566a284dc2dce48e131d93a76c060bfed84
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: be4bcfcc57fa3c2a0735afcba152ce6cc3eea439
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Starting to guess this error is because of a \ versus / again... Windows, amirite?

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: c4d1c4fe18b7723ff632d8f72a1cb1b8f8b5ae20
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 03b5725033f1d31abdace09f9e6fcd3151b25c58
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 0b71697648d3f9f2ba6ade801001c33de32c3242
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 15414a4aac039fb5a03597bcfeed43c278ed166c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 953df41785a94b3347536cf2471ac65022d07507
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 599da888eea66528f0c9e7e9b30b73aa3fa47d0f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: ac374d8d9466b4ced28f79febcdc3ebf64d0d695
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7d5233e4cba77eb3b0b6daa352d79b229c2ed9de
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 0a8eede4c589e630146d07c6cff4d83fdf1e5e68
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: cccb7798048932422d9d5097ff33574c948e94e5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: bc923b04e36bc2c341e9d56d6e355f4e2574206b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 4527d2bb619eea96cd6898fe0d3d4787b54f88e2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7ef62ce6af17d2bc51cdb862a0cb4108ce8e47ef
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: dbe16371eab65b8e32a4f4b5b83f24cfa9f987c2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 5aa6d6c3ee88addf3c3d49656b2d22c28f6218a2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: d93559eb68f85c98ed89a1a1dfd9d18912ae4e37
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: c495fcaa776086db43148264ad1d45e4b53bea33
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 223c154578782cde5b60ff5dce8623258cb1337f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7200f16d602f4dd3e2660003017f19c366e87d1e
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: cd6374cf5e4c79f23ea209aae585819fd17fa29b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 04ed9a50183f6b9761f4421ff6c3b2ebd8fed58b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 8b80fb451e5ac788117f88ae2647cf0f8c8abc8d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 3dc274a35ba6e1d2ce081d1045fd833242e25c50
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 577725c0ea43e16437851232ba4970d1b9f270a7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: c22e608436fdab56c4cba0d05b1470b76b379f56
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 020ef86758bd08ca3a4bf4a24b5ff5509a30ccc0
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

Yay - it now works. but there's an issue with jsii-tree tests on Windows (that's what we are here for, I guess!)

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 52ca9ba79e1c45bad65d3a22109097b7bfdbe82f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 87713e5699431cb4af10a113a5fab0f8ccb0483d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: d9364dbbe35b86f2ce14a25054ca81be1f0783c8
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 414c6562999832759154f7dc5f9fd4b7ba2b0104
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: bdbe99e226cddf78f20a6bd444b9cc1f7149da17
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: de981d7d924dc5e0d7b69bb2dc2d1668ae19c3c7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 95f97833299e79bf5630a61da45dd7f3220faa0d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: da4a3f48b310dcd9249adf77316fb73aaf0a3b32
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 54c10566798ce686b97e8489f2be6a63df81e260
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: e26ccc0718dd2052d4ae40a1231252e12f40c49d
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 2adbdc145370b90e55a053945673c3048fdc5c8a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 38ba3b6c115ccf51b4cba8fccda545fbcb121894
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 42dee9e035c0b0755c43d875d5b55e8ba485ca2a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 4e7e27e9052addca582278ac4afa655eedbe435a
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 8f80dcc48ce4e2661fc7ac706d456ea941ab3332
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 18b54b9cdbdfb925eda2808d756f60859aeea971
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: f2e539166d106c782ac4d0b9bfafdf254f07c8f6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 2e979a32f9161baedd86c40ecd337c52d3d96579
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: fce7e787638eeb0d3385c0ad508c1ab82917e491
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: b73ad8b6765181c020c8eb7473ad6d6fb1dea94f
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: ebbdbe3afdcafe45cd01bb7dcd5998190aa35e86
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: cfc071d9dcaf20bf1f87d6a89e13d9638041edd8
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 287b4ee7e8bbd08019159ad1f45897bd3901c9b6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 8ccca388867058deffe3deaceb6ed26395b1706b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 200ed9c336a3c39f17b005a396168ced58adcf86
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7234bafcd755effa12c49e62cd73b4fab3939f78
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 5c1a669ae43140fd4989b7bd31c2170781d064c5
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 39c747b6b051550296d2a0f33a9232a252bba3b2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7a951fbbcd42a6f136925775fd57314276a9a4df
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7c8f1b4cda5422454d44764d5fc937031b88b259
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: ce06bb4eb824952246459865573ac5d4b1351bf7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 53f67f6f765032cbac351af8e6ee09e7fea513d2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: c7fcbfbc0072cd2d9bfb0fdea401ef3ed47b096b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: e50b00e644d19f1cb3fadcf48fd0ca8525201286
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7b37173481fd4ac3a405af1e44d64eb2e17f238b
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: a68df079b3065d9aded23c695e50e950db8827b2
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 7e6b3f107b2d1314426d85ba99a3473ecc7df6da
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: c679242bd1a0259347b5347631771fa70f5c9d37
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: a7dde6fd6c7e388b639b8bf15855b1bc32d3bdc9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: e85399850030df1cde227b16f35a74e2fa4b2e61
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: dc620f5b6846e84f83e89d5fce97062b47bb0cbb
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: b0e87a22958efa006217cd92b464a949ce0eb991
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 57e367397b19069773918d7a871569a2d8dab026
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 76a8c4e7911a50e965f4690555dbb6c8cdf56c53
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 0140b85a914315d627c61c75dd4464b9919bc8fc
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: e28b2512bc9af00368b55268ef0045a5c654fb69
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 4e44b19eb425caa16778fc61d8b39818901a9c66
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 2acee296d794f12815e99537c4c75ba5c5e3be8c
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 02bac8b4c9f393ec421f29bfc8a188ff58222630
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: e3b86a9bb86c7b14a694d332eaabfd5a096bfc24
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: b1ad25a7ce9b2e6e3531fdadbd521ae63df51ef8
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 010e0c78f0b133803be0c1dceabe44c1d21853b2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: ce2bbc5bb704fb3362056ba17d68b7c7d4ea7ca3
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: a30add3c2154381ac741c691ea76fefe5cd39a22
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 76ac785d2730094e85ad338b7a329e7f022cf0f7
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: cadbfeae953f783f09d2ea9eea973d159dc3cfd4
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 8cc02cc7e8bfa1423edda5a458d15dd818440482
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 02f1561dede95fe5aa7f340c747a800cd5a7de15
Result: FAILED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 74be80a01ebb1a1bc47573e33bca2aa47187e0a2
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: e10d02faabe1f2a0639f589de518dffa07792da6
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: c55cfc596d8c6e6e3c9f42631337e936af3bc1dd
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-Blkkw9bQFn8A
Commit ID: 69e2fb03943f6cd724f91be0deecb010aeb1cbf9
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


[AutoPR hdinsight/resource-manager] [HDInsight] Added support for ADLS type Gen 2

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3376

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/1986


evaluate comrak as Markdown parser, renderer

Feature Description
Recently, comrak gained support for math parsing. It now fulfills most of (everything?) what Gitea requires, so it's perhaps worthwhile considering it as a parser/renderer. GitLab already has and step-by-step replaces their own quirks.
My main motivation for suggesting this stems from Gitea's various math bugs, e.g.:

#28259
#28070
#27834
#27777
#27618
etc.

Screenshots
No response

Erm… How is gitea supposed to include Rust code as a Go project?

I thought it might be possible since GitLab, written in Ruby, does the same.

They use it as library with Ruby binding, nothing we want to do.

Alright, thanks for the input. Closing.


Update readme with straight.el installation steps

add straight installation instructions
(use-package doom-snippets
  :after yasnippet
  :straight (doom-snippets :type git :host github :repo "hlissner/doom-snippets" :files ("*.el" "*")))

Sorry for the (tremendously) late reply. Thanks for the PR!


Prerelease PR# versioning

Updated Prerelease deployment spack env style, and uses more generic undeploy-* workflow from build-cd.
Requires ACCESS-NRI/build-cd#42 before merging
References ACCESS-NRI/ACCESS-OM2#56

This looks very similar to https://github.com/ACCESS-NRI/ACCESS-OM2-BGC/pull/5
Is there any point in consolidating it in some shared CI code?

Yep. That is what is currently being done with the whole OM3 thing - pulling out functionality that is similar.
This is a special case, where the CI/CD infra is almost completely identical. I'm not sure I want to create a parent repo to house the OM2-specific CI that each of them call...at least not yet. If there are more variants, then yeah.

A fair bit of it seems model agnostic to me, but I'll defer to you about the best approach to generification


Re-export internal dependency instead of leaking it into user package

PR Info

Closes https://github.com/SeaQL/seaography/issues/66

Adds

[x] seaography re-export heck and itertools. We cannot re-export those dependencies on seaography-macros because proc_macros crate can only export proc_macros.
[x] Write seaography version dynamically based on the version of seaography-generator

Changes

[x] seaography-generator: Cargo.toml template will not include heck and itertools as dependencies.
[x] CI compile generated examples that depends on local seaography

Ready for review

Looks good to me


Git artifacts: 'reference delta not found' clone problem

Pre-requisites

[X] I have double-checked my configuration
[X] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
Looks like the library 'go-git' that you are using for cloning git repositories has a problem "reference delta not found" on the git.PlainClone function.

https://github.com/go-git/go-git/issues?q=is%3Aissue+reference+delta+not+found
Looks like in the latest version the problem is fixed. I think that a version update on your side will fix the problem.
Thank you!
Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
artifacts:
          - name: repo
            path: /src
            git:
              repo: "{{workflow.parameters.repo}}"
              revision: "{{workflow.parameters.revision}}"
              disableSubmodules: true
              usernameSecret:
                name: "{{workflow.parameters.secretName}}"
                key: username
              passwordSecret:
                name: "{{workflow.parameters.secretName}}"
                key: password

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

ERRO[2022-12-13T10:08:07.481Z] container "main" in pod "create-flz2c-retrieve-changed-markdown-files-4256658970" is terminated  namespace=argo podName=create-flz2c-retrieve-changed-markdown-files-4256658970 workflow=create-flz2c

Logs from in your workflow's wait container
There are no logs

Experiencing the same problem

I think this issue is still persisting, got it with the latest version of Argo

I think this issue is still persisting, got it with the latest version, i.e., 3.4.4

There has not been a new release since the fix, i.e. it is not fixed in the 3.4.4 release, maybe in 3.4.5 (or what will be the next release version).
https://github.com/argoproj/argo-workflows/blob/release-3.4/go.mod#L229

Any work arounds known? This only seems to be the case for private repositories (I was able to pull a public one).

@lvijnck This workaround by Alex might work for you until the fix for this issue is released. You can use your auth token as mentioned here.


Extreme Beta

I can login to LiveShare, see other team members...but something as simple as - setting my status from Offline, to Available...NOTHING...This looks to be a great idea...many, many years ago I looked - without any success - at a PostGrad investigation into collaborative software engineering environments...and as many years later, I thought this was it. Sooo many issues, problems, connectivity SNAFUs...all before the slightest collaboration is even possible. Contact me in a couple years when this product actually works!

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

ID: 62d2dbef-9f65-dfc7-3d5d-b74b7d88c399
Version Independent ID: 09d0d40c-987f-112a-de83-8a3db354b2b9
Content: Troubleshooting - Visual Studio Live Share
Content Source: docs/troubleshooting.md
Product: visual-studio-family
Technology: live-share
GitHub Login: @Chuxel
Microsoft Alias: clantz

Hi @ChrisMulvey,
Thank you for the feedback. We've actively working on reliability issues. If there's specific ones you're running into, please attach logs and we can help address the issues.

Closing due to staleness. If you have logs or more information, that would be really helpful! Feel free to re-activate if you can provide those details so we can investigate.


NeoVim freezes when opening a file with the .zig extension

Issue is in the title.
I've confirmed this on macOS and Linux running Neovim nightly and stable.
Open nvim with an empty buffer and run :checkhealth nvim_treesitter with only this parser installed will crash nvim.

I got error too, not because of this commit. I'm investigating. I'll fix in the weekend. I have 12h working tomorow

Has anyone found a fix or workaround for this yet? This also affects the helix editor.

Good new guys https://github.com/neovim/neovim/pull/16606#pullrequestreview-829735327. Without it, i really have no clue how to fix it

Solved with
https://github.com/nvim-treesitter/nvim-treesitter/issues/2049#issuecomment-993853458


IE, Embed, and Header

IE SVG CSS Fix
Embed Area
Header title a little bigger on desktop
@jiwalker-usgs I'll figure out the merge conflicts

@jiwalker-usgs All ready to review

@mwernimont fix conflicts?

@jiwalker-usgs Got blocked by github, but should be dec for the moment


How was the 18k dataset prepared?

Hi,
Im trying to fine-tune the model with functions support.
When I use the Vicuna prepare_all.py data pipeline on the original sharegpt dataset with 16k max token length, I get 60k~ conversations on merged_clean_lang_split_identity_single.json. When I only get the english, I get 45k~
What kind of filtering did you do exactly? For example, did you remove the small conversations?, Did you get only the english? etc

@musabgultekin I use: clean_sharegpt, optional_clean, extract_gpt4_only (after this is roughly 15k), and I add non-gpt4 response with > 16K(~2k) , split_long_conversation(but with 16K length), ending up ~18K. I started with a shareGPT with ~80K conversation.
Thx for the question! We are iterating on some data processing and new version training. Will release an official document on the final version of data.

Hi,
Im trying to fine-tune the model with functions support. When I use the Vicuna prepare_all.py data pipeline on the original sharegpt dataset with 16k max token length, I get 60k~ conversations on merged_clean_lang_split_identity_single.json. When I only get the english, I get 45k~
What kind of filtering did you do exactly? For example, did you remove the small conversations?, Did you get only the english? etc

Hi @musabgultekin , may I ask where can I get the original sharegpt dataset? Thank you very much!

@Arist12 AFAIK https://huggingface.co/datasets/anon8231489123/ShareGPT_Vicuna_unfiltered


[HUDI-4647] Change the default value of HIVE_SYNC_MODE in MergeInto to HMS

By default, an error will be reported when synchronizing hive. When using SQL, it is troublesome to fill in the JDBC URL parameter every time

Caused by: org.apache.hudi.hive.HoodieHiveSyncException: Cannot create hive connection jdbc:hive2://localhost:10000/
        at org.apache.hudi.hive.ddl.JDBCExecutor.createHiveConnection(JDBCExecutor.java:107)
        at org.apache.hudi.hive.ddl.JDBCExecutor.<init>(JDBCExecutor.java:59)
        at org.apache.hudi.hive.HoodieHiveSyncClient.<init>(HoodieHiveSyncClient.java:91)
        ... 48 more
Caused by: java.sql.SQLException: Could not open client transport with JDBC Uri: jdbc:hive2://localhost:10000: java.net.ConnectException: Connection refused (Connection refused)
        at org.apache.hive.jdbc.HiveConnection.openTransport(HiveConnection.java:234)
        at org.apache.hive.jdbc.HiveConnection.<init>(HiveConnection.java:178)
        at org.apache.hive.jdbc.HiveDriver.connect(HiveDriver.java:105)
        at java.sql.DriverManager.getConnection(DriverManager.java:664)
        at java.sql.DriverManager.getConnection(DriverManager.java:247)
        at org.apache.hudi.hive.ddl.JDBCExecutor.createHiveConnection(JDBCExecutor.java:104)
        ... 50 more
Caused by: org.apache.thrift.transport.TTransportException: java.net.ConnectException: Connection refused (Connection

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@hudi-bot run azure

@dongkelun thanks for the patch. there are 2 reasons to why we have to close this for now:

we should keep default value consistent for different scenarios
we don't want to introduce breaking changes (unless with strong reason) until 1.0 when we batch these breakings together

hence i'm tracking the tasks here https://issues.apache.org/jira/browse/HUDI-5062
OK. got it
One thing I want to say is that in previous versions of mergeInto, the default value of HIVE_SYNC_MODE is HMS. In other SQL statements, such as insert update, the default value is also HMS

@dongkelun thanks for the patch. there are 2 reasons to why we have to close this for now:

we should keep default value consistent for different scenarios
we don't want to introduce breaking changes (unless with strong reason) until 1.0 when we batch these breakings together

hence i'm tracking the tasks here https://issues.apache.org/jira/browse/HUDI-5062
OK. got it
One thing I want to say is that in previous versions of mergeInto, the default value of HIVE_SYNC_MODE is HMS. In other SQL statements, such as insert update, the default value is also HMS

@dongkelun ok in this case it's a different story. we should keep it aligned for all sql scenarios. I'm re-openning this PR. Can you please re-purpose this PR to move org.apache.spark.sql.hudi.command.MergeIntoHoodieTableCommand#buildMergeIntoConfig into org.apache.spark.sql.hudi.ProvidesHoodieConfig? we should fix the sync mode and make all hive sync settings aligned with others wherever applicable

@dongkelun thanks for the patch. there are 2 reasons to why we have to close this for now:

we should keep default value consistent for different scenarios
we don't want to introduce breaking changes (unless with strong reason) until 1.0 when we batch these breakings together

hence i'm tracking the tasks here https://issues.apache.org/jira/browse/HUDI-5062
OK. got it
One thing I want to say is that in previous versions of mergeInto, the default value of HIVE_SYNC_MODE is HMS. In other SQL statements, such as insert update, the default value is also HMS

@dongkelun ok in this case it's a different story. we should keep it aligned for all sql scenarios. I'm re-openning this PR. Can you please re-purpose this PR to move org.apache.spark.sql.hudi.command.MergeIntoHoodieTableCommand#buildMergeIntoConfig into org.apache.spark.sql.hudi.ProvidesHoodieConfig? we should fix the sync mode and make all hive sync settings aligned with others wherever applicable
@xushiyan  Ok, I will try my best

@dongkelun can you please rebase?

The job running on agent Azure Pipelines 8 ran longer than the maximum time of 150 minutes

@dongkelun can you please rebase?

@xushiyan Hi, the CI has passed

@xushiyan hello,can you please help me take a review?


In release 2.0, "".pluralize() is not a function

Date.create() works, but "".pluralize() yields a TypeError (at least in Chrome)
I have made sure that Sugar.extend() is called.
What tips do you have for resolving this?

So, first, are you using the main builds? Pluralize isn't part of the default build (actually it never was). There are a few ways you can build it, the easiest is through the site's new "custom build" too. If you're using it in node you may have to hold tight until the sugar-inflections package is pushed.. should be soon though....

Using it in Chrome.  I downloaded the "Sugar.js" from the main page.
I'll try from the builder

How were you using it before?

I'm not sure, but I think that's how I got it before.  It's been a while :)

But was it always through the site?

Yep.

Hmm that's strange then.. The inflections module was always excluded from the default build...

I might have gotten it from the old builder...I really don't remember

I'm just happy someone's using it! It was always kinda off the map... was wondering if it was all that useful....

I figured "if someone else wrote it, it saves me trouble" :)

Fun fact: I'm using the same .JS file for Node and UI ... yesterday the pre-upgrade version was cached.  Today it loaded the new one.  And doesn't like it much :)  I didn't fix any of my Node code.

Hmm... so to answer your question from yesterday I'm not really sure the best forum to help you out with this... if nothing comes to mind you could always shoot me an email...

Do you have a chat client that you use?  Or would email be better?

Email is maybe better for now I guess

Using the full build fixed the issue.


NEXUS-42442: Created Jenkinsfile to publish docker SBOMs

This pull request makes the following changes:

Add jenkins job to publish docker image SBOMs to sonatype-sboms repository in production

It relates to the following ticket:

https://sonatype.atlassian.net/browse/NEXUS-42442

Jenkins Job: https://jenkins.ci.sonatype.dev/job/nxrm/job/nxrm3/job/Docker image SBOM release/

Some of the code could be modularized, other than that LGTM