Bug with menu container when tag set to false

Hi.
I've got a custom menu extended from basic yii\widgets\Menu
In the widget we have $options array with tag option:

tag: string, defaults to "ul", the tag name of the item container tags. Set to false to disable container tag.

Okay, then what we do in our new widget:
$this->options['tag'] = false;

But now we see "<>" string in page at the begining of menu widget, what's going on? Let's have a look in parent widget:
echo Html::tag($tag, $this->renderItems($items), $options);

No conditions about $tag is equal to false, so it renders  '<>' right before widget layout

Have you tried with code from master?

@samdark Yes, just tried, the issue still exists

Do you want to work on a fix and then send a pull request?

@samdark Yes, I'll get it


skip-to-content keyboard accessibility link: should highlight target when clicked (temporary flashing outline)

Note that this is how the navigator handles document targets. I will see if I can use the same techniques in the UI.

fixed in a240094

Pull Request: https://github.com/readium/readium-desktop/pull/447

Note that this issue is about temporarily highlighting (visually-speaking) hyperlink targets which are not necessarily tabbable or even focusable, such as a main element which contains the content area that a "skip link" would typically reach into.
Such feature would typically rely on the existing CSS :target pseudo-class. In fact, there is already a style to achieve this effect:
https://github.com/readium/readium-desktop/blob/758d318ba17c334faeba8097f9b9d457b74d8bba/src/renderer/assets/styles/focus.css#L16-L37
For more context, see my comment:
https://github.com/readium/readium-desktop/pull/447#issuecomment-512846320
What needs to be discussed in this issue is whether such "highlighting" mechanism actually improves accessibility in the context of the Thorium User Interface. This mechanism is used in the EPUB HTML content documents, as it greatly improves usability for sighted users with mouse and keyboard interaction (without the visual effect, the user has now idea where the hyperlink targets are).
This technique is also used in the DAISY accessibility testsuite (albeit, the provided example displays a permanent highlight / outline, whereas I implemented a temporary one in the EPUB navigator):
https://github.com/daisy/epub-accessibility-tests/blob/f04c9d6dd1c4c9275e9f80000b31663fb06b44b2/content/epub30-test-0340/EPUB/Styles/styles.css#L34-L41

Closing, as not necessary in UI (okay in EPUB docs)


Can't build

Excuse me for being a computer novice, I seem unable to handle this issue.

Yeah, I have run the script and the top lines are the results after the run, My OS: Slackware Kerneal: 5.15.63

I tried to rerun the script：

Sorry  we need to add slackware support for installing dependency.
In the meanwhile either you can install dependencies manually by looking at what install_deps.sh is doing or try the latest release Appimage.

The AppImage also lacks some dependencies,

Anyway, thank you for your response, I will try to continue the problem because I want to use this high performance terminal.

Then you need to change install-deps.sh a bit and add the following calls :
fetch_and_unpack_Catch2
fetch_and_unpack_fmtlib
fetch_and_unpack_gsl
fetch_and_unpack_yaml_cpp
fetch_and_unpack_range

You can add this right after the line with 439: echo "OS $ID not supported."

Then you need to change install-deps.sh a bit and add the following calls :
fetch_and_unpack_Catch2
fetch_and_unpack_fmtlib
fetch_and_unpack_gsl
fetch_and_unpack_yaml_cpp
fetch_and_unpack_range

You can add this right after the line with 439: echo "OS $ID not supported."

Thank you! I'll try it.


Can't install vagrant-aws because xmlrpc requires Ruby version >= 2.3

I'm using Vagrant 1.9.4 to install vagrant-aws, which failed to install today with this error:
xmlrpc requires Ruby version >= 2.3
I tracked this down to one of the vagrant-aws dependencies: fog-core, which released 1.44.0 today and pulls in xmlrpc.
To workaround, I installed fog-core first with the last compatible gem:
vagrant plugin install --plugin-version 1.43 fog-core
Then vagrant plugin install vagrant-aws installs successfully.

Currently tracked on the fog side: fog/fog-core#206

+1 I have the same issue.

Root issue resolved in fog-core 1.44.1: https://github.com/fog/fog-core/issues/206

Plain vagrant plugin install vagrant-aws works for me now with the fog-core 1.44.1 published to rubygems.

I'm getting this error when running vagrant plugin install vagrant-aws with vagrant 1.8.4. I'm trying to work out what has changed "recently", because the code itself has not been modified for ages, but started failing around the 29th June.


[FormRecognizer] Improve DocumentField.AsCurrency docstrings

@kinelski commented on Tue Sep 07 2021
We should be more descriptive about the format of the returned string.

@maririos commented on Tue Oct 05 2021
Note that this will change in the future, so we need to be careful here

The service doesn't return a string for currency anymore. A CurrencyValue object is returned, and it has clear properties (Amount, Symbol) to describe the format used. Closing this issue.


Port To GitLab

Can we move to project over to GitLab please? I created the kubicorn group - just DM me if you need creds.

https://gitlab.com/kubicorn

Is this still on the docket? Any specific reasons for the change? Do we want to take advantage of CI stuff there?


I have somewhat an interesting setup but for the sake of a reproducible I ran the following commands inside a docker container docker run -it golang:1.23-alpine /bin/sh
$ go install golang.org/x/telemetry@latest
go: downloading golang.org/x/telemetry v0.0.0-20240830212034-a0ccdf0ac735
go: downloading golang.org/x/sync v0.8.0
package golang.org/x/telemetry is not a main package

Or to get a specific version go install<EMAIL_ADDRESS>What did you see happen?
The problem is the<EMAIL_ADDRESS>directory that comes with this package is not writeable by the owner, typically directories are 0755.
$ ls -l $GOPATH/pkg/mod/golang.org/x/telemetry/
total 4
dr-xr-xr-x    2 root     root          4096 Sep  4 00:44<EMAIL_ADDRESS>
I also ran stat<EMAIL_ADDRESS>which shows Access: (0555/dr-xr-xr-x)
What did you expect to see?
I expect directories to be 0755 so that they can be removed by owners.
It seems like this telemtry package is new https://pkg.go.dev/golang.org/x/telemetry?tab=versions (in existence since only Aug 28 2024).
In the Docker example above, I can remove the directory, since you're root in docker. But in other setups where this directory exists (I can share further details on how such a setup gets ends up with this file) I would expect them to be 0755 so that they could be removed.
Is it intentional for this directory to be 0555?

Related Issues and Documentation

cmd/go: telemetry data should not be in $XDG_CONFIG_HOME #68988
cmd/go: any invocation creates read-only telemetry configuration file under GOMODCACHE #68946 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

the entire mod cache is intentionally read only.
Unlike many projects, the Go project does not use GitHub Issues for general discussion or asking questions. GitHub Issues are used for tracking bugs and proposals only.
For questions please refer to https://github.com/golang/go/wiki/Questions

hi @seankhliao thank you for responding,
could you please reconsider.
I realalise the cache is read only, however when running go mod vendor -modcacherw the telemtery package is still read only, not the -modecacherw, this problem doesnt exist for other packages in the cache, see below:
# go mod vendor -modcacherw
go: downloading github.com/spf13/cobra v1.8.1
go: downloading github.com/spf13/pflag v1.0.5
go: downloading github.com/inconshreveable/mousetrap v1.1.0
# stat<EMAIL_ADDRESS>  File<EMAIL_ADDRESS>Access: (0555/dr-xr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)
# stat<EMAIL_ADDRESS>  File<EMAIL_ADDRESS>Access: (0755/drwxr-xr-x)  Uid: (    0/    root)   Gid: (    0/    root)

I have a simple cobra script which causes this,
here is the go.mod:
module mytelemetry

go 1.22.4

require github.com/spf13/cobra v1.8.1

require (
	github.com/inconshreveable/mousetrap v1.1.0 // indirect
	github.com/spf13/pflag v1.0.5 // indirect
)

I have updated the reproducible "What did I do section",
Please let me know if this is something that could be reopen :)

see #68946

I see, thank you @seankhliao


netusb: RNDIS host support

Hi, i am testing Zephyr connect to Android Phone with Type-C, i found Android Phone only supports RNDIS Device mode, so it that mean Zephyr device should support RNDIS Host?
I also tried ECM mode, but Zephyr can't run DHCP Server, so Android Phone doesn't have IP

Hi， I have same question

@Jeepgoing Zephyr only supports the USB Device role, not USB Host.

@carlescufi @finikorg I think RNDIS have Host and Decice itself , is it possible RNDIS host run on USB device?

@Jeepgoing Do you have Android phone with OTG?

yes @finikorg  It's have OTG function

yes @finikorg It's have OTG function

Then Zephyr is USB device and RNDIS should work

@finikorg But  Android phone need DHCP by Zephyr, I can't find DHCP server support

If Zephyr is compiled with auto IPv4 support CONFIG_NET_IPV4_AUTO=y, the system should start using 169.254.xxx.xxx addresses so there should be no need for DHCP server support.

@jukkar you mean Zephyr Device and Android Phone all use default IP?

you mean Zephyr Device and Android Phone all use default IP?

No, I mean that if devices are configured to use auto IPv4 addresses, then they will select suitable IPv4 addresses from 169.254/16 block in order to communicate with each other. Linux typically has this support automatically enabled but in zephyr you need to manually enable this.

Closing per comments


Update Contribution guidelines

We have contributing guidelines in 3 different places:

CONTRIBUTING.rst
Wiki: Guidelines for contribution
Wiki: Rules for commits and issues labelling (git)

Joshua is working on harmonizing the contributing guidelines across NeuroPoly projects with the new NeuroPoly Contributing Guidelines on wiki.
Those guidelines are compatible with current ADS guidelines except:

Versioning: ADS versioning differs from MAJOR.MINOR.PATCH
Maybe Versioning should be specific to each software and indicated in each project wiki.

Here are the changes that I proposed in ADS:

Remove CONTRIBUTING.rst:

The content is almost identical to NeuroPoly Contributing Guidelines
There are some ADS specific information that could be moved to the ADS wiki:
-- Issue Body: testing data (not up-to-date)
-- Issue Labels
-- Issue Examples
-- Some specific information concerning documentation and tests

Remove Wiki:Guidelines for contribution:

Bug reporting template is not useful (there is already a template when opening an issue)
The rest is very similar to NeuroPoly Contributing Guidelines
Make sure that theses 2 points are in the NeuroPoly guidelines:
-- Cite any papers, packages or code snippets used to implement the feature.
-- Each pull request should propose ONLY ONE feature (independent from other features in the code).

Modify Wiki: Rules for commits and issues labelling (git):

The commit message part is not used (do we really want that?)
The labelling part for issues and PR should be kept (like SCT) and the link add to it in the NeuroPoly Contributing Guidelines.
Everything else is very similar to NeuroPoly Contributing Guidelines
Changes made in SCT labels that would make sense in ADS:
-- Change the refactoring label to a PR "category" label (instead of "context") to distinguish code structure changes from enhancement changes
-- Change description of enhancement
-- Add description for refactoring
-- Change testing label to context instead of category
-- Other category labels to add? 	documentation-internal, CI, git/github

Rename Wiki: How to create a new release to Versioning an add the link in the NeuroPoly Contributing Guidelines

tagging @joshuanewton here

Versioning: ADS versioning differs from MAJOR.MINOR.PATCH

we go with MAJOR.MINOR.PATCH

Remove CONTRIBUTING.rst:

OK for remove

Remove Wiki:Guidelines for contribution:

OK for remove

Modify Wiki: Rules for commits and issues labelling (git):

We can do exactly as done in https://github.com/neuropoly/spinalcordtoolbox/wiki/Contributing%3A-Labelling-issues-and-pull-requests, and update https://www.neuro.polymtl.ca/open_source/contributing#pr_labels

Rename Wiki: How to create a new release to Versioning an add the link in the NeuroPoly Contributing Guidelines

We'll keep the name (How to create a new release), the link has been added to Versioning in Neuropoly wiki.

Thank you for the tag @jcohenadad, and thank you for taking the time to create this issue with an in-depth write-up @mariehbourget. :slightly_smiling_face:

Make sure that theses 2 points are in the NeuroPoly guidelines:
-- Cite any papers, packages or code snippets used to implement the feature.
-- Each pull request should propose ONLY ONE feature (independent from other features in the code).

Thanks much for this suggestion. I very much agree with adding the first point.
For the second point, how do you feel about this wording? "Each pull request should try to address only one issue, with each issue representing a single feature or bug report."

The labelling part for issues and PR should be kept (like SCT) and the link add to it in the NeuroPoly Contributing Guidelines.

If each of the projects ends up with a similar scheme for labels (e.g. context, category), perhaps this information could be put directly into NeuroPoly Contributing Guidelines, and we wouldn't even need individual pages on each GitHub Wiki.

We'll keep the name (How to create a new release), the link has been added to Versioning in Neuropoly wiki (https://www.neuro.polymtl.ca/open_source/contributing#versioning)

I agree with this, too.
In fact, I'm wondering if the NeuroPoly Contributing Guidelines should even have "Versioning". It doesn't necessarily seem like information that new contributors need to know about to be able to contribute. (It more seems like information needed by each of the specific, dedicated project maintainers who are responsible for creating releases -- that's why I like your suggestion of keeping the "How to create a new release" page on the developer Wiki.)

Stale

(minor minor nitpick, but for stale issues, I think it might be beneficial to close as "not planned" rather than "completed")

I didnt see those options - i didnt even know they existed!! Thanks!


Building the image with NVMe doesn't work without DENALI set

When building with NVME_USED=TRUE, snap_settings complains about missing DENALI environment variable for the Denali include directory
### WARNING ### Setting of NVME_USED=TRUE but DENALI not set!
It must be possible to build FPGA images with the NVMe host controller, even without a Denali environment.

it is part of the master branch

As Simulation always needs DENALI set, I cannot really help with the validation of this issue. Let us do this in image build. Putting me off the assignee list

I can confirm that image build with NVMe works now also in case $DENALI or other Denali related environment variables are not set.
@jsvogt please close this issue.

Thanks, closing this issue.


Preparation meeting -Team B 21/11/16

Preparation for full team meeting.
Summary below
https://docs.google.com/document/d/1tls0bY0KRH2MkzKZP6S9HSjSkJSsSoJOu3jCIXObMjE/edit?usp=sharing

Meeting Summary:
Avney Safa Madlikot
Ideas:

Usage statistics - dynamically change of the parking slots type according to the amount of cars with specific sticker color, or according to times and yearly events and holidays.

To be discussed:

Where can we find initial database? Is it fine to fake one? should we save car parking time amount using sensors? How should we update the driver about already parked curbstone color change?

Manager interface:
GUI for managing parking slots colors manually by:

hours

dates

holidays and events

semester periods (exam period, summer etc.)

To be discussed:

Should we give a grace period for drivers whose cars parked while the curbstone was in one color, and now it’s got changed to a not valid curbstone color for his car?

Proximity sensors:

Managing timers for collecting real time statistics.

Alerting when curbstone is about to be color changed

Blocking color from changing when car is parked in a parking spot.

To be discussed:

Is it necessary? Can we get them for the project? How should we transfer data from the sensors to the DB? Are we really want to block color changing when car is parking?

Users Management:

Classifying by sticker’s color.

Update sticker color.

Adding new users according to user details (name, id etc.)

User sticker status (valid or expired).

Watch all of the user’s parking tickets.

Queries:

Given user type (sticker color) and required parking time, the system shall answer the optimized parking slot according to the details above, with guarantee that the slot’s curbstone color will not be changed until the car is parked.

Given user type, the system shall show a map of the Technion with all the available parking slots (using proximity sensors).

Given a specific parking slot at the Technion, the system shall provide data about the sticker colors who can park there and in what time.

Map:

Graphical and dynamic view of the Technion parking areas, the dynamic colors of the curbstone should be shown as well:

Parking areas colors.

Parking navigation for specific car with specific sticker color.

Update parking’s curbstone color after manual update by Technion Security Unit.

Update parking’s curbstone color after dynamically update by the system.

Led Lights:

Visual change of the curbstone color according to the color it's get by the system.

To be discussed:

Is it necessary? Should the system consider a delay, if exists? Do we want to add this kind of a delay? Should we want to block color chaning using the proximity sensors?

First Sprints:

DB Design.
Basic design of a GUI for manually management of parking slots.
Creating DB for users and for parking statistics.
Creating basic GUI for management.
Basic diagnostic of the statistics - events, holidays, semester periods.
Expand diagnostic of the statistics - by hours and days in the week.


Farmer Working, Telegram Bots, working.

Can you please sort out the bots on the telegram page. It's constant chatter that gets in the way of real users who want to support another Chia fork.
Thanks guys. Stay Sync'd

Got it


Internationalization supports

Add internationalization supports.
filename.md: Default language set
filename-EN.md: English language set
'-' + 'ISO-639-1' before file extension will be reserved.

610483d amended.


Add liceupetrila.ro domain

https://liceupetrila.ro
https://liceupetrila.ro/oferta-educationala/ (Computer Science related field - program of 4 years of study)

@ImGAF Pull request merged. Thank you!


support namespaced operation

Welcome to Codecov :tada:
Once merged to your default branch, Codecov will compare your coverage reports and display the results in this comment.
Thanks for integrating Codecov - We've got you covered :open_umbrella:


?? Operator results in "Unexpected Token" err when used in package

Describe the bug
If you import a package that uses ?? operator in code, create react app will fail when debugging.
This issue seems to appear only when debugging with such a library. (npm run start)
It builds (npm run build) without errors. So the toolchain for start vs build is in question here.
The operator works fine if used directly -  not in the imported library code.
Did you try recovering your dependencies?
Issues occurred with multiple CRAs even with reinstalling node modules.
Which terms did you search for in User Guide?
Null Coalescing Operator Create React App
There seems to be an issue about optional chaining.
Environment
Windows 10 10.0.17763
npm 6.14.5
node 14.4.0
Google Chrome was used to ensure async, let, const, classes, and ?? support.
Steps to reproduce

Create a React App with TypeScript (Haven't tried without TS)
Create NPM package (TS with target ESNext, module, commonjs, declaration) that uses the ?? operator
Use package in your app.
Run start script

Expected behavior
The application should compile and run successfully when started or when built..
Actual behavior
The application fails to compile due to the ?? in the library.
Failed to Compile,
Unexpected token
You may need an additional loader to handle the result of these loaders.
Reproducible demo
If needed I can brew something up. This was found in a work project.

I'm encountering this issue too – here's a repo to reproduce: https://github.com/bitjson/bitauth-cra (npm install && npm start):
<EMAIL_ADDRESS>112:37
Module parse failed: Unexpected token (112:37)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|   }), {});
|   const entityOwnership = Object.entries(template.entities).reduce((all, [entityId, entity]) => ({ ...all,
>     ...Object.keys(entity.variables ?? {}).reduce((entityVariables, variableId) => ({ ...entityVariables,
|       [variableId]: entityId
|     }), {})

The nullish coalescing operator works as expected in App.js, the error only seems to occur when the operator appears in an external dependency. (Try replacing this block with console.log(undefined ?? "success!") to confirm.)
Does anyone have any tips for how to debug this issue?

As another data point, the bitauth-ide repo is running react-scripts at version 3.4.1, and the same library (@bitauth/libauth) is being imported without any errors. I'm still trying to figure out where the difference is.

For any TypeScript library authors having trouble with this, one workaround is to switch your compilation target from esnext to es2019. That will at least downlevel all nullish coalescing operators (??) so they don't trigger this bug.

Same error with<EMAIL_ADDRESS>

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

The above just remove transpilation of those features. That is, it drops support for older browsers.
Looks like 4.0.0 was released - but hasn't been properly tested.
Anyone can confirm that 4.0.0 still doesn't work with ?? (with or without TS)?

Still getting the error on 4.0.0
../dist/index.modern.js 88:119
Module parse failed: Unexpected token (88:119)
File was processed with these loaders:
 *<EMAIL_ADDRESS> * ../node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|
|   function numberMask(rawValue = emptyString, config) {
>     rawValue = clean(rawValue, options, (config === null || config === void 0 ? void 0 : config.currentCaretPosition) ?? -1);
|     let [integer, fraction] = rawValue.split(period);
|     const hasPeriod = rawValue.indexOf(period) > -1;

I tried the browserslist workaround from @bkiac and it worked for me (I could build debug but not production, now I can do both.) I'm on node 12.18.4 and the build is working fine for me. Oddly enough, my coworker cannot build the project for debug or production.
We don't have react-scripts installed so it might be an issue unrelated to react-scripts

I'm gonna bump it. But the fix may be to use CRACO or something to configure 4.0.1.

any update here?

any update here?

It happens to me on 4.0.1 , and I don't know any other workaround than forcing other libraries to not use esnext as the compilation target ( https://github.com/facebook/create-react-app/issues/9468#issuecomment-692963920 ). Which is far from nice.

Is there any way to fix this with a javascript module? (The module I'm using gives the same error, but it was written in javascript). Do I have to edit the module myself?

https://github.com/facebook/create-react-app/issues/9468#issuecomment-694191642 worked for me

<EMAIL_ADDRESS>10:41
Module parse failed: Unexpected token (10:41)
File was processed with these loaders:

./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|   useEffect(function updatePathOptions() {
|     if (props.pathOptions !== optionsRef.current) {

  const options = props.pathOptions ?? {};

|       element.instance.setStyle(options);
|       optionsRef.current = options;
------- herte is my error guys. please help me..

[Solved] Failed to compile<EMAIL_ADDRESS>10:41 Module parse failed: Unexpected token (10:41)

You might be able to fix this by using the @babel/plugin-proposal-nullish-coalescing-operator in your project. See https://github.com/PaulLeCam/react-leaflet/issues/883 for why this is happening.

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

could you plz send your package.json file

Same issue here,
<EMAIL_ADDRESS>10:41
Module parse failed: Unexpected token (10:41)
File was processed with these loaders:
 * ./node_modules/react-scripts/node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|   useEffect(function updatePathOptions() {
|     if (props.pathOptions !== optionsRef.current) {
>       const options = props.pathOptions ?? {};
|       element.instance.setStyle(options);
|       optionsRef.current = options;

Same error in a storybook

As a temporary workaround you can specify "@react-leaflet/core": "1.0.2" as dependency and spacify also
"resolutions": {     "react-leaflet/@react-leaflet/core": "1.0.2"   }
in package.json. This forces react-leaflet package to have @react-leaflet/core version 1.0.2 as dependency

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

This works for react-leaflet also when you delete the .cache folder within node_modules and run yarn start again.
Hope this helps. This fixed it for me.

I have tried the fix to remove the "development" property from "browserlist", delete the .cache folder, and start again, I get this prompt from CRA:
? We're unable to detect target browsers.

Would you like to add the defaults to your package.json? › (Y/n)

If I choose yes, CRA writes the development property back in, and the run fails again.  If I choose no, I get the message:
As of react-scripts >=2 you must specify targeted browsers.
Please add a browserslist key to your package.json.

Which makes no sense, because I'm not removing the browserslist key, just the development property of it.  I even tried this:
"browserslist": {
  "production": [],
  "development": []
}

But the error persists.  What can I do?

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

This works for react-leaflet also when you delete the .cache folder within node_modules and run yarn start again.
Hope this helps. This fixed it for me.

doing this solved for me. thanks

As a temporary workaround you can specify "@react-leaflet/core": "1.0.2" as dependency and specify also
"resolutions": { "react-leaflet/@react-leaflet/core": "1.0.2" }
in package.json. This forces react-leaflet package to have @react-leaflet/core version 1.0.2 as dependency

This is not working for me.

This is an issue with third-party packages so there's not much we can do  about it. Package authors should generally not be compiling for esnext. Consider opening an issue with those packages.

@iansu FYI it was esnext back when the issue was opened, but today it's es2019.  react-leaflet uses es2019 and this issue is most certainly present there. The author has rejected requests to revert to es2018, so the whole thing is in a nice deadlock.

Deleting the browserlist does not solve the problem for me as react-script automatically adds it back, this issue happens on installing some packages.
My workaround at the moment is to remove the package 😁

Deleting .cache folder inside node_modules worked for me. Thanks ;)

This is an issue with third-party packages so there's not much we can do about it. Package authors should generally not be compiling for esnext. Consider opening an issue with those packages.

Now, I very much do understand that it's hard to constantly upgrade the React tooling to support all the latest features of Javascript. Especially when Javascript is moving so fast that other frameworks suffer from similar issues.
However, since the nullish coalescing (??) is supported in every major browser now, it would be quite lovely if React could also support it. After all, React feels like the most modern of the frameworks. Is there an issue that I can watch and thus get notified when it gets implemented? Or could this issue be reopened?
https://caniuse.com/?search=nullish

I agree with @stefnotch. This is not an issue with the 3rd-party package, since this package shipped syntax that is supported by the browser! It's the CRA build pipeline that tripped up on valid code.
I think any reasonable build pipeline in 2021 should understand ES2021 syntax! It should then either

Leave the code as it is so that is continues to work (for >90% of users), or
Compile that code down to something supported by even more browsers.

As a package author, I don't want to start working around the quirks of downstream build pipelines.

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
you should delete the .cache folder within node_modules and run npm start again

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

This worked great for me, you have to remove node_modules and do npm install again for it to work.

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

After this,  Do the following:

Delete your node_modules folder
Run npm cache clean --force
Run npm install

Now everything should work as expected.

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

After this, Do the following:

Delete your node_modules folder
Run npm cache clean --force
Run npm install

Now everything should work as expected.

thanks this comments!
it remind me babel have cache，and i just delete the cache folder:
node_modules\.cache
it work for me

@nicolo-danzi what you said on 20th March worked for the problems that I had with react-leaflet/core. However I still have react-leaflet/esm related errors do you know any work around? Thanks in advance.

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

This works for react-leaflet also when you delete the .cache folder within node_modules and run yarn start again.
Hope this helps. This fixed it for me.

Thankyou very much for the solution, worked for me!

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue. I think #8445, #8526 could be related. The issue is with aggressive browser targets like last 1 chrome version.

Don't forget to delete the .cache folder in noce_modules before you do the npm install

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue.
I think #8445, #8526 could be related.
The issue is with aggressive browser targets like last 1 chrome version.

After this, Do the following:

Delete your node_modules folder
Run npm cache clean --force
Run npm install

Now everything should work as expected.

that's solved the issue

Do we know why did this fix the issue ? - note: it did fix the issue for me, but wanted to fully understand the reason behind

Do we know why did this fix the issue ? - note: it did fix the issue for me, but wanted to fully understand the reason behind

Because node_modules has a different babel preset.
babel-preset-react-app
https://github.com/facebook/create-react-app/blob/67b48688081d8ee3562b8ac1bf6ae6d44112745a/packages/react-scripts/config/webpack.config.js#L412-L424
vs babel-preset-react-app/dependencies
https://github.com/facebook/create-react-app/blob/67b48688081d8ee3562b8ac1bf6ae6d44112745a/packages/react-scripts/config/webpack.config.js#L464-L479
The craco config adds the plugin"@babel/plugin-proposal-nullish-coalescing-operator".

Changing browser targets from
 "browserslist": {
   "production": [
      ">0.2%",
      "not dead",
      "not op_mini all"
    ],
    "development": [
      "last 1 chrome version",
      "last 1 firefox version",
      "last 1 safari version"
    ]
},

to
"browserslist": [
   ">0.2%",
  "not dead",
  "not op_mini all"
],

solved my issue. I think #8445, #8526 could be related. The issue is with aggressive browser targets like last 1 chrome version.

This resolved an issue I had with parsing PURE annotations with babel in a library I was using.
Thank you!
./node_modules/react-square-web-payments-sdk/dist/components/divider/divider.es.js 12:15
Module parse failed: Unexpected token (12:15)
File was processed with these loaders:
 * ./node_modules/babel-loader/lib/index.js
You may need an additional loader to handle the result of these loaders.
|   return /*#__PURE__*/React.createElement(Line, { ...props
|   }, /*#__PURE__*/React.createElement(SpanText, { ...spanProps
>   }, children ?? "or"));
| };
|

Hey all, I've been looking at this the past couple days, and its still breaking.
Unfortunately the browse list change didn't work for me.
I installed '@babel/plugin-proposal-nullish-coalescing-operator and added it to the plugins array, and also no luck.
Any other solutions I missed that I should look at? Thanks

Hey all, I've been looking at this the past couple days, and its still breaking.
Unfortunately the browse list change didn't work for me. I installed '@babel/plugin-proposal-nullish-coalescing-operator and added it to the plugins array, and also no luck.
Any other solutions I missed that I should look at? Thanks

@acrabb
According to the doc:
https://create-react-app.dev/docs/supported-browsers-features/#configuring-supported-browsers

When editing the browserslist config, you may notice that your changes don't get picked up right away. This is due to an issue in babel-loader not detecting the change in your package.json. A quick solution is to delete the node_modules/.cache folder and try again.

Deleting the node_modules/.cache works for me.

Deleting the node_modules/.cache worked for me. Thanks @tkforce

Hey all, I've been looking at this the past couple days, and its still breaking.
Unfortunately the browse list change didn't work for me. I installed '@babel/plugin-proposal-nullish-coalescing-operator and added it to the plugins array, and also no luck.
Any other solutions I missed that I should look at? Thanks

@acrabb According to the doc: https://create-react-app.dev/docs/supported-browsers-features/#configuring-supported-browsers

When editing the browserslist config, you may notice that your changes don't get picked up right away. This is due to an issue in babel-loader not detecting the change in your package.json. A quick solution is to delete the node_modules/.cache folder and try again.

Deleting the node_modules/.cache works for me.

this worked for me. thanks much.

{
  "name": "wits",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "start": "webpack-dev-server --open --config webpack.dev.js",
    "build": "webpack --config webpack.prod.js",
    "analyz": "webpack --config webpack.analyzer.js",
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "@babel/core": "^7.9.6",
    "@babel/plugin-transform-runtime": "^7.12.15",
    "@babel/polyfill": "^7.11.5",
    "@babel/preset-env": "^7.9.6",
    "@babel/preset-react": "^7.9.4",
    "@babel/runtime": "^7.12.13",
    "babel-loader": "^8.1.0",
    "clean-webpack-plugin": "^3.0.0",
    "css-loader": "^3.6.0",
    "file-loader": "^6.0.0",
    "html-loader": "^1.1.0",
    "html-webpack-plugin": "^4.3.0",
    "mini-css-extract-plugin": "^0.9.0",
    "node-sass": "^4.14.1",
    "optimize-css-assets-webpack-plugin": "^5.0.3",
    "sass-loader": "^8.0.2",
    "style-loader": "^1.2.1",
    "webpack": "^4.43.0",
    "webpack-bundle-analyzer": "^3.8.0",
    "webpack-cli": "^3.3.11",
    "webpack-dev-server": "^3.11.0",
    "webpack-merge": "^4.2.2"
  },
  "dependencies": {
    "@material-ui/core": "^4.11.0",
    "@material-ui/icons": "^4.9.1",
    "@material-ui/lab": "^4.0.0-alpha.56",
    "@sweetalert/with-react": "^0.1.1",
    "axios": "^0.20.0",
    "canvas-gauges": "^2.1.7",
    "classnames": "^2.2.6",
    "downsample-lttb": "0.0.1",
    "expression-eval": "^5.0.0",
    "i18next": "^19.4.5",
    "i18next-browser-languagedetector": "^4.2.0",
    "leaflet": "^1.9.3",
    "moment": "^2.29.4",
    "plotly.js": "^2.18.2",
    "prop-types": "^15.7.2",
    "react": "^16.13.1",
    "react-alert": "^7.0.1",
    "react-alert-template-basic": "^1.0.0",
    "react-container-dimensions": "^1.4.1",
    "react-dom": "^16.13.1",
    "react-draggable": "^4.4.5",
    "react-grid-layout": "^1.3.4",
    "react-helmet-async": "^1.3.0",
    "react-i18next": "^11.5.0",
    "react-leaflet": "^4.2.1",
    "react-plotly.js": "^2.5.1",
    "react-query": "^3.39.1",
    "react-responsive-carousel": "^3.2.23",
    "react-router-dom": "^5.2.0",
    "use-interval": "^1.4.0",
    "use-window-focus": "^1.4.2"
  },
  "browserslist": [
    ">0.2%",
    "not dead",
    "not op_mini all"
  ]
}

and i am encountering the same error how can i resolve this?

Thanks this answer worked!
https://stackoverflow.com/a/67747605
Like @ferm12, you said @babel/plugin-proposal-nullish-coalescing-operator this solved the issue for me

@shahsawar92 I am glad you were able to solve your problem.

@ferm12 i am having an old repo which is at react 16 version.  the above issue is still persisting even though I updated the configs in babel
dependencies{
      "react": "^16.12.0",
      "react-scripts": "3.2.0",

babel.config.js
module.exports = {
   presets: ['@babel/preset-env'],
   plugins: [
      [
         '@babel/plugin-proposal-decorators',
         {
            legacy: true
         }
      ],
      '@babel/plugin-proposal-nullish-coalescing-operator',
      '@babel/plugin-proposal-logical-assignment-operators'
   ]
}

what is the issue here? is it with react versions? Could you give solution to this?
TIA.

I just had this issue while using node 12 in an old environment, nvm i 18 && nvm use 18 solved it for me after the browserlist change didn't fix it in my case.

The cause is exactly the same as #8526 which added support for nullish coalescing in the developers code (e.g. App.js) but not in node_modules.
Now that it is supported by all evergreen browsers it is reasonable to assume that there will be some NPM packages that do not transpile this.
I think the changes in #8526 should be added to https://github.com/facebook/create-react-app/blob/main/packages/babel-preset-react-app/dependencies.js until react-scripts is using a newer version of webpack that can handle this syntax.
I didn't want to change my browserslist because it would transpile other code unnecessarily, so I used CRACO.
npm install @babel/plugin-proposal-nullish-coalescing-operator --save-dev

// craco.config.js
module.exports = {
  babel: {
    plugins: [["@babel/plugin-proposal-nullish-coalescing-operator"]],
  },
};

@jamime Just curious if the whole node_modules are also transpiled by a babel plugin would'nt it make it slower to start react app or make hot reloding slower ?

// craco.config.js
module.exports = {
  babel: {
    plugins: [["@babel/plugin-proposal-nullish-coalescing-operator"]],
  },
};

This code is the fast fix the issue.I use craco,add the babel plugin is well fix this. Thx  @dhiren-eng


Combine concurrent and similar subject

Example;

No need to combine subject.
Feedback from Hayat :

The classes appeared on the schedule for law students are not fixed. Some of the time decided is for students to choose themselves and picked the right time for them. For example, subject 'Criminal Law' has 5 times appeared a week in the course schedule. Its actually only (2) times a week that are fixed. Another (3) is for us to choose only (1) our preferred time and delete the other (2) from our chedule. So, as this app does not allow us to delete/add the course & time, it's not practicable for law students. Hope creator can fix on this :) Thanks!


Unable to install Accio via brew

I tried to install Accio on my company Mac and stumbled upon an issue installing it.
I‘m not quite sure if it relates to Accio directly, though.
Current configuration:

macOS Mojave 10.14.4 (18E226)
Xcode 10.2.1 (freshly installed from the App Store)
Fresh installation of brew
Swift 5.0.1 (swiftlang-1<IP_ADDRESS> clang-1<IP_ADDRESS>)

Running brew install accio results in:
rion$ brew install accio
Updating Homebrew...
==> Installing accio from jamitlabs/accio
==> Cloning https://github.com/JamitLabs/Accio.git
Updating /Users/abraun/Library/Caches/Homebrew/accio--git
==> Checking out tag 0.6.1
HEAD is now at 6b01bd6 Merge branch 'deploy/0.6.1' into productive
HEAD is now at 6b01bd6 Merge branch 'deploy/0.6.1' into productive
==> make install prefix=/usr/local/Cellar/accio/0.6.1
Last 15 lines from /Users/rion/Library/Logs/Homebrew/accio/01.make:
2019-04-29 15:13:48 +0200

make
install
prefix=/usr/local/Cellar/accio/0.6.1

dyld: Library not loaded: @rpath/llbuild.framework/Versions/A/llbuild
  Referenced from: /Library/Developer/CommandLineTools/usr/bin/swift-build
  Reason: image not found
make: *** [accio] Abort trap: 6

If reporting this issue please do so to (not Homebrew/brew or Homebrew/core):
  jamitlabs/accio

/usr/local/Homebrew/Library/Homebrew/utils/github.rb:253:in `raise_api_error': Validation Failed: [{"message"=>"The listed users and repositories cannot be searched either because the resources do not exist or you do not have permission to view them.", "resource"=>"Search", "field"=>"q", "code"=>"invalid"}] (GitHub::ValidationFailedError)
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:207:in `open_api'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:352:in `search'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:260:in `search_issues'
from /usr/local/Homebrew/Library/Homebrew/utils/github.rb:273:in `issues_for_formula'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:372:in `fetch_issues'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:368:in `issues'
from /usr/local/Homebrew/Library/Homebrew/exceptions.rb:422:in `dump'
from /usr/local/Homebrew/Library/Homebrew/brew.rb:136:in `rescue in <main>'
from /usr/local/Homebrew/Library/Homebrew/brew.rb:36:in `<main>'

@Rion-Kaneshiro Thank you for reporting the issue. I tried freshly reinstalling Accio on my machine and it worked, so I can't reproduce the error. Could it be that this solution on SO fixes this for you, too?

@Dschee After a very long reinstallation of Xcode and your proposed solution, it finally installed :)
Seems like the problem has to do with having multiple instances of Xcode installed, like the Beta for example.
Thanks for the help :)

@Dschee After a very long reinstallation of Xcode and your proposed solution, it finally installed :)
Seems like the problem has to do with having multiple instances of Xcode installed, like the Beta for example.
Thanks for the help :)

Great to hear that! Closing this then.


Add python bindings for geomPropDef elements.

Adding basic geomPropDef-related methods to the python bindings.

Looks good, thanks Davide!


Fix missing bracket(ja)

What does this PR do?
Improve repo
For resources
Description
Fix missing bracket in japanese.
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

Thanks for finding these problems!


Won't work with Mix 6.0.49

I think you need to bump the peer laravel-mix to v6. I'm getting the following error:
npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/laravel-mix
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| ~5.0" from<EMAIL_ADDRESS>npm ERR! node_modules/laravel-mix-postcss-config
npm ERR!   laravel-mix-postcss-config@"*" from the root project

I am also experiencing this issue.


Drop validation-gen-enabled-tags and validation-gen-disabled-tags

Since we're using k8s: prefixes to selectively enabled declarative validation, we don't need these options.  Removing them simplifies things.

@thockin @aaron-prindle @yongruilin


Update automation-service.md

removing ARK integration from the list as it’s not compatible with the Automation Service fixed a typo in Arcann (it should be Arcanna)
Purpose of this pull request
This pull request (PR) ...
Issue number:

Select the type of change:

[x] Minor Changes - Typos, formatting, slight revisions
[ ] Update Content - Revisions and updating sections
[ ] New Content - New features, sections, pages, tutorials
[ ] Site and Tools - Updates, maintenance, and new packages for the site, Gatsby, React, etc

@kimsauce, the "verification/cla-signed" check is failing, even though @fullah-sumo signed his name. Do you have any idea why this is happening?

@jpipkin1 , after the contributor signs, you have to add that person's GitHub name to the .clabot file in our repo.

@jpipkin1 Thank you so much for your help

Thanks for the explanation, @kimsauce.
I created the following PR to add fullah-sumo to the .clabot file. Could you review it for me? #2032

Done! Looks good.

@kimsauce answer to your question at https://github.com/SumoLogic/sumologic-documentation/pull/2029#discussion_r1159942075


working on smoke test for Test environment

we have been continuously testing the test environment.

we have the new code for the testing, Need to do another testing.

All the test jobs runs successful in test environment.

Results are uploaded in teams folder
https://cdc.sharepoint.com/:w:/r/teams/CDC-Data-Exchange/_layouts/15/Doc.aspx?action=edit&sourcedoc={b594d951-e03c-4fc1-afb5-b3755477f0d7}&wdOrigin=TEAMS-ELECTRON.teamsSdk.openFilePreview&wdExp=TEAMS-CONTROL&web=1


Train derail in a bend

Sometimes a train derails at a high maxspeed. Most of the times it's in a bend which can be seen on the picture below. The train has a maxspeed of 2.0. In the 1.7 version it doesn't derail.

How to reproduce?

Build a bend as shown on the picture, set slowdown false and maxspeed at 2.0. Sometimes it does work so it doesn't derail. But sometimes it does derail with this setup.

Change some properties in the config, this isnt a real bug. Just the standard config is messed up.

Wich option must get changed for this?

Just restored the config from 1.7.10 and it still happens.

There is no change in the config from the other versions, the problem is that the 1.8 train mechanics changed only I lost the file that has the changes. Will go search for it.

So there's a bugg in TrainCarts?

No, only some values have to be changed in the config to match 1.8 minecarts.

And you only need to find these values back?

Yes, had them somewhere on a notation pad,

Ok, when do you think that you have these changes so I can test these?

Any progress?

Still waiting for you to find a YML file?

Yeah, I've noticed this as well, it broke a few rides on my server. Is this something we can fix config-side, or does it require an update to the plugin? If it is config side, what must be changed? Thanks :)

it is config side, and you need to change the distance between de individual carts to something like 0.4 or 1.0

Changed normal.cartDistance to 1.0 and 0.4, tested both. Still the same problem of breaking trains.

You need to change the turned.cartDistanceForcer to some value between 0.4 and 1.0. It should work then.

Didn't work either.

At a maxspeed of 0.8 the train breaks. With a maxspeed of 0.7 it didn't happend.

I found out that most of the bug came from 1.8 minecart behaviour itself. And there is not much that I can do about, because the values are different for each ride. The best solutions is to just thinker with it and find out what's working en what's not.


Unable to compile in termux

~/.../rust/nvim-rs $ cargo run --example basic --features use_tokio
   Compiling libc v0.2.166
   Compiling proc-macro2 v1.0.92
   Compiling unicode-ident v1.0.14
   Compiling autocfg v1.4.0
   Compiling cfg-if v1.0.0
   Compiling byteorder v1.5.0
   Compiling memchr v2.7.4
   Compiling parking_lot_core v0.9.10
   Compiling pin-project-lite v0.2.15
   Compiling getrandom v0.1.16
   Compiling crossbeam-utils v0.8.20
   Compiling futures-sink v0.3.31
   Compiling futures-core v0.3.31
error: failed to run custom build command for `proc-macro2 v1.0.92`

Caused by:
  could not execute process `/storage/emulated/0/Download/rust/nvim-rs/target/debug/build/proc-macro2-4f76f87a7b9d73fd/build-script-build` (never executed)

Caused by:
  Permission denied (os error 13)
warning: build failed, waiting for other jobs to finish...

It's my problem, due to the fact that I cloned the project to sdcard and then compiled it, resulting in no execute permissions, it actually compiles fine!


[release/1.1 backport] bump libseccomp-golang v0.9.1

backport of https://github.com/containerd/containerd/pull/3371 for the 1.1 branch
full diff: https://github.com/seccomp/libseccomp-golang/compare/32f571b70023028bd57d9288c20efbcb237f3ce0...689e3c1541a84461afc49c1c87352a6cedf72e9c
Release notes:

Version 0.9.1 - May 21, 2019

Minimum supported version of libseccomp bumped to v2.2.0 (https://github.com/seccomp/libseccomp-golang/commit/fc0298087f328ac97a1fa781392de96b2ebb8aac)
PowerPC and S390(x) architectures are unavailable below library version v2.3.0 and will return errors if used with incompatible libraries
Use Libseccomp's seccomp_version API to retrieve library version
Unconditionally set TSync attribute for filters, due to Go's heavily threaded nature
Fix CVE-2017-18367 - Multiple syscall arguments were incorrectly combined with logical-OR, instead of logical-AND (https://github.com/seccomp/libseccomp-golang/commit/06e7a29f36a34b8cf419aeb87b979ee508e58f9e)
Fix a failure to build on Debian-based distributions due to CGo code
Fix unit test failures on 32-bit architectures
Improve several errors to be more verbose about their causes
Add support for SCMP_ACT_LOG (with libseccomp versions 2.4.x and higher), permitting syscalls but logging their execution
Add support for SCMP_FLTATR_CTL_LOG (with libseccomp versions 2.4.x and higher), logging not-allowed actions when they are denied

Signed-off-by: Sebastiaan van Stijn<EMAIL_ADDRESS>(cherry picked from commit bb41ef87f1841531526126ccd2ad1a4291e8571c)
Signed-off-by: Sebastiaan van Stijn<EMAIL_ADDRESS>

Codecov Report

Merging #3375 into release/1.1 will not change coverage.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           release/1.1    #3375   +/-   ##
============================================
  Coverage        49.07%   49.07%
============================================
  Files               85       85
  Lines             7598     7598
============================================
  Hits              3729     3729
  Misses            3194     3194
  Partials           675      675

Flag
Coverage Δ

#linux
49.07% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

FWIW; I discussed the vendor bump with @justincormack, and he thought that the actual vendor in containerd, containerd/cri, and dockerd are not critical for the CVE itself; the version in runc is the important one, but turned out that it was already patched (there was some confusion about that).
Bumping the vendored files in these branches would still be good to have (IMO) to take away any doubt (and possibly security scanners finding a vulnerable version of the dependency).
If there's concerns about updating these files here, feel free to close

LGTM


About Me Picture Overflows

The about me picture overflows into the right side between 1100px and 1000px.

The width was set to 900px at min-width: 1000px. Changed the width to 800px and it stops the overflow.


bug: Fix typing issues in latest click

@jcheng5 My questionable change is adding the name to click.group(). Is this an ok change?

pyright
/home/runner/work/py-shiny/py-shiny/shiny/_main.py
  /home/runner/work/py-shiny/py-shiny/shiny/_main.py:24:2 - error: Untyped function decorator obscures type of function; ignoring decorator (reportUntypedFunctionDecorator)
  /home/runner/work/py-shiny/py-shiny/shiny/_main.py:32:7 - error: Cannot access member "command" for type "function"
    Member "command" is unknown (reportFunctionMemberAccess)
  /home/runner/work/py-shiny/py-shiny/shiny/_main.py:370:7 - error: Cannot access member "command" for type "function"
    Member "command" is unknown (reportFunctionMemberAccess)
  /home/runner/work/py-shiny/py-shiny/shiny/_main.py:399:7 - error: Cannot access member "command" for type "function"
    Member "command" is unknown (reportFunctionMemberAccess)
  /home/runner/work/py-shiny/py-shiny/shiny/_main.py:427:7 - error: Cannot access member "command" for type "function"
    Member "command" is unknown (reportFunctionMemberAccess)
5 errors, 0 warnings, 0 informations

cc @karangattu

Test failures for example apps are unrelated to changes. Merging


Add OSEHRAHelper dir to path before running

Ensure that the Python/vista directory is in the system path before
the running of the VistAMComponentExtractor.
Change-Id: Ifb53fe6e1f28567542840be11ff69f5b4d9b8c38

Good catch! rebased and ready for approval.


Not all icons are working

Hi I'm using lates beta of template.
I'm trying to add icon to TheSidebar menu.
I'm adding menu item like following:
children.push({
   _name: "CSidebarNavItem",
  name: "Violation reports",
  to: { name: "reports" },
  icon: "cil-warning"
});

And it is working fine. But when I use another icon, like "cil-heart" or "cil-mobile", it stopping to work, so
children.push({
  _name: "CSidebarNavItem",
  name: "Devices",
  to: { name: "devices" },
  icon: "cil-mobile"
});

does not work.
This issue happens everywhere, not only for sidebar menu.

You have to import icons you need in asets, or whole icons package id you don't mind bundle size.

Ok, for those who will have some issue:
Go to src/assets/icons/icons.js file and add your icon name if it is not appearing.

For the next poor soul that runs into this: make sure to restart the npm server after adding icons in src/assets/icons/icons.js

Any chance the template can just load all icons by default?

For an Angular project, I had to dig in the source code to find a solution :
For those Icons that don't show, do the following :
Example of cil-money not showing
Where you declare your route
import { cilMoney } from '@coreui/icons';
//
const routes : INavData[] = [
  //
  {
    name: 'foo',
    url: '/foo',
    iconComponent: { name: 'cil-money', content: cilMoney }
  }
  //
]

I don't know why some show and some need this extra step. (I did not import those that show anywhere in my code)
But this approach seems to work


Named-entity recognition

How would you approach named-entity recognition with this library?

Any update on NER tasks with this library?

Hi,
As I managed to use this library for NER task i am happy to share my experiences.
Sorry, but I can't share the whole code, but trying to explain the key parts.

The input text is tokenized by the tokenizer module and padded to a specified max lenght (in my case 200 tokens at max)
For each token the output tags are transformed into a one-hot vector and if the tokenizer broke up one word into multiple tokens then I used the belonging tag for the first token and [MASK] for the remaining part of the original word
1+2) So I have X sentences in the trainign set, then the input shape is (X,200) hence 200 is the padded lenght of each sentences. In this case the output shape is (X,200,NUMBER_OF_TAGS). NUMBER_OF_TAGS is the number of your entity types, depends of whether you use BIOE, or just BIO, and here you add the special tokens: [CLS], [PAD], [MASK]. In my case here are the tags:
['B-ORG', 'I-ORG', 'B-MISC', 'I-MISC', 'B-LOC', 'I-LOC', 'I-LOC', 'B-PER', 'I-PER', 'O', '[CLS]', '[MASK]', '[PAD]'].
This way my shapes are (X,200) and (X,200,12)
load the Bert model the same way as in the calssification example but here we will use a different model architecture for the remaining layers, hence it is not just a classification. This is basically the example codes of the packages description with a little tweak:

bert_layer = bert_tf2.BertModelLayer.from_params(bert_params, name="bert")

input = tf.keras.layers.Input(shape=(200))
output = bert_layer(input)
output = tf.keras.layers.TimeDistributed(tf.keras.layers.Dense(units=12, activation='softmax'))(output)
model = tf.keras.models.Model(inputs=input, outputs=output)

model.build(input_shape=(200))

bert_layer.apply_adapter_freeze()
bert_layer.embeddings_layer.trainable=False

The magic here is the TimeDistributed wrapper layer.
My results:
After just 1 epoch on 29k trainign sentences:
loss: 0.0227 - categorical_accuracy: 0.9933 - val_loss: 0.0042 - val_categorical_accuracy: 0.9988
So basically, that's it folks :)


operator mongodb-enterprise (1.16.3)

This PR has been created by MongoDB Release Automation Tool.
If additional details are needed, please contact any authorized
reviewer from MongoDB.

/merge possible

/merge possible


Return in promise data (when error)

For example: i have an input in confirm. How can i get data.inputText in second function after .then()   (error processing)

pass whatever variable you want to the cancel function. That variable will be passed to the error function

@Schlogen but how to pass data on backdrop click?

I don't believe ui-bootstrap modal supports that. if it does, link me the relevant docs


how to change default download behavior to "deny"?

Description
In puppeteerjs, this can be done as below:
const puppeteer = require('puppeteer');

(async () => {
    const browser = await puppeteer.launch({headless: false});
    const page = await browser.newPage();
    await page._client.send('Page.setDownloadBehavior', {
        behavior: 'deny'
    });
    await page.goto("https://s.codepen.io/boomerang/iFrameKey-ece752a2-192a-1f85-b63f-199176b096d4/index.html");
})();

But when I tried to do the following:
await new BrowserFetcher().DownloadAsync(BrowserFetcher.DefaultRevision);

var browser = await Puppeteer.LaunchAsync(new LaunchOptions
{
    Headless = false
});
var page = await browser.NewPageAsync();

var clientProp = page.GetType().GetTypeInfo().GetDeclaredProperty("Client");
var client = clientProp.GetValue(page) as CDPSession;
var method = client.Connection.GetType().GetTypeInfo().GetDeclaredMethod("SendAsync");
await (Task)method.Invoke(client.Connection, new object[]{"Page.setDownloadBehavior", new {
    behavior = "deny"
}});

var resp = await page.GoToAsync("https://s.codepen.io/boomerang/iFrameKey-50c549ef-bab1-2043-847e-1fef0eac751c/index.html");

I cannot get same result.
I have checked the JSON stringified message at Connections.cs@90, compare it against Connections.js@191, i got same string as {"id":12,"method":"Page.setDownloadBehavior","params":{"behavior":"deny"}}
So, any idea why this is not working? And how to fix it?
I have found #172 but in my case, the response type is document, so I cannot simply "Abort" document request.
I am using the latest version of puppeteer-sharp 1.1.0, with dot net core 2.1.300
Thanks very much

oh, one more thing, the test code for the download page is in here: https://codepen.io/Ariex/pen/BPNBLr
the url in the description does not last long, you might need to either create a local page with the code as in the pen, or refresh it then get the url of the preview panel... sorry for the inconvenience

this get fixed, i dived too deep..
var clientProp = page.GetType().GetTypeInfo().GetDeclaredProperty("Client");
var client = clientProp.GetValue(page) as CDPSession;
var m = client.GetType().GetTypeInfo().GetDeclaredMethods("SendAsync").ElementAt(1) as MethodInfo;
await (Task)m.Invoke(client, new object[]{"Page.setDownloadBehavior", new {
    behavior = "deny"
}});

Create created #411 so we can expose that API call.

@Ariex Just a late comment here. Now SendAsync exposes the SendAsync method, you can use it without reflection.

@kblok thanks very much, this is awesome!


Unexpected Dtype Cast Caused By Clipping

Describe the bug
The dtype of input tensor can be unintentionally converted to np.float64, default in numpy, from np.float32, specified explicitly in the config file, by the operation of clipping after enabling random initialization in the protocols such as PGD and FGM. This will later raise an dtype mismatch error between the input (float32) and the weights of model (float64).
The problem is that the tensor after clipped is applied a forced dtype cast to float32 in the code line 309 in the file art\attacks\evasion\fast_gradient.py. I suggest to apply such dtype cast after the clipping in order to fix it.
To Reproduce
Steps to reproduce the behavior:

explicitly pass a tuple of numpy ndarray, default dtype is np.float64, as clip ranges to the constructor of classifier wrapper class.
enable the random intialization by setting the parameter num_random_init greater than or equal to 1 when constructing specific attack class e.g. FGM
normally run the generate method to perturb the input

Expected behavior
the dtype of clip range should not change the dtype of input tensor during the perturbation process.
System information (please complete the following information):

Ubuntu 18.04
Python 3.6
ART latest version
PyTorch

sorry that there is a typo in the description of bug. The mismatch of dtype should be the input (float64) and the weights of model (float32).

Hi @TreeLLi Thank you for reporting this issue! We will investigate and fix it as soon as possible.

Hi, thanks for your great work and concern of this issue. I am happy to give more detail if need.

@TreeLLi I think a similar Dtype change can happen in line 295 if the clip_values are provided as np.float64. Have you observed similar problems with num_random_init=0?
I think we should add in both lines .astype(ART_NUMPY_DTYPE) after np.clip().
@TreeLLi Would you be interested to implement a solution and make a pull request? Otherwise I can I go ahead and make the changes.

There is no problem with num_random_init=0, even though _apply_perturbation method with clipping may change the dtype of its return. In the case without random initialization, the dtype of x_adv variable in the method body is fixed as np.float32 and the slicing assignment operation, line 323, in numpy seem to implicitly perform the dtype cast to the same one as the LHS variable's i.e. np.float32. However, I do agree with you to also care about the potential dtype conversion at the line 295, since it may raise an exception at another place.
I would like to suggest that we conver the dtype of clip_values to ART_NUMPY_DTYPE initially e.g. in the initializer of the class Classifier instead of doing conversion wherever np.clip called. I am happy to make a pull request for this issue.

That's really great and I'm looking forward to the pull request! I think your solution is the best one and the explanation makes sense. We are currently working on branch dev_1.3.0 for the upcoming release, this would be the target branch for this issue. Let us know anytime if you have questions.

Hi, I have implemented a fix and tested in my program which performs FGM and PGD with num_random_init=1. The solution just works well as we expected. However, I noticed that unit tests are required in your contribution guideline, but I think it may be better to modify the existing FGM and PGD attack tests to cover the aforementioned situations instead of creating a new separate test. Please tell me how you think and if I need to do anything regarding the unit test.

That's great news! I also think that these changes don't require new unittests. I would suggest that you go ahead with opening a pull request to target branch dev_1.3.0 and then we can see its Travis CI results and reason which unittests might require updates.


Java Code

We want java code for this app

Have a look at this fork for a Java implementation.

Thanks for the request.  There are currently no plans to write a Java Programming Language version of Sunflower, though there is a third-party fork as mentioned above.


error: use of undeclared identifier 'hint'; did you mean 'link'?

When trying to compile 2.1.1 on FreeBSD I get:
/usr/local/libexec/ccache/cc -DMI_MALLOC_OVERRIDE -DMI_SHARED_LIB -DMI_SHARED_LIB_EXPORT -Dmimalloc_EXPORTS -I/wrkdirs/usr/ports/devel/mimalloc/work/mimalloc-2.1.1/include -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing -O2 -pipe  -fstack-protector-strong -fno-strict-aliasing  -DNDEBUG -fPIC -Wall -Wextra -Wno-unknown-pragmas -fvisibility=hidden -Wstrict-prototypes -Wpedantic -Wno-static-in-inline -ftls-model=initial-exec -fno-builtin-malloc -std=gnu11 -MD -MT CMakeFiles/mimalloc.dir/src/prim/prim.c.o -MF CMakeFiles/mimalloc.dir/src/prim/prim.c.o.d -o CMakeFiles/mimalloc.dir/src/prim/prim.c.o -c /wrkdirs/usr/ports/devel/mimalloc/work/mimalloc-2.1.1/src/prim/prim.c
In file included from /wrkdirs/usr/ports/devel/mimalloc/work/mimalloc-2.1.1/src/prim/prim.c:22:
/wrkdirs/usr/ports/devel/mimalloc/work/mimalloc-2.1.1/src/prim/unix/prim.c:172:184: error: use of undeclared identifier 'hint'; did you mean 'link'?
        _mi_warning_message("unable to directly request aligned OS memory (error: %d (0x%x), size: 0x%zx bytes, alignment: 0x%zx, hint address: %p)\n", err, err, size, try_alignment, hint);
                                                                                ^~~~
                                                                                link
/usr/include/unistd.h:351:6: note: 'link' declared here
int      link(const char *, const char *);
         ^
1 error generated.

The full build log:
mimalloc-2.1.1.log
Environment:
FreeBSD 13.1-RELEASE amd64
clang 14.0.5

thanks for the report, long time I did not build on freebsd, it got unnoticed for a while.

thanks for the report, long time I did not build on freebsd, it got unnoticed for a while.

Thank you for the quick fix. I've just updated the FreeBSD port.

@ehaupt Can you re-open this so we can commit the patch upstream? Thanks.

@yonas, done. Not sure why I closed it.


[analyzer] Static check on yield should use the element type

Consider the following program:
import 'dart:async';

Stream<int> f() async* {
  dynamic d = 1;
  yield d;
}

Iterable<int> g() sync* {
  dynamic d = 1;
  yield d;
}

void main() async {
  await for (var i in f()) print(i);
  for (var i in g()) print(i);
}

The current analyzer (from commit dce0263228c0587fe6258e2cc7ed01ffacbd5c2e) reports an error for each of the two yield statements:
ERROR|COMPILE_TIME_ERROR|YIELD_OF_INVALID_TYPE|/usr/local/google/home/eernst/lang/dart/scratch/202105/n012.dart|5|9|1|The type 'Stream<dynamic>' implied by the 'yield' expression must be assignable to 'Stream<int>'.
ERROR|COMPILE_TIME_ERROR|YIELD_OF_INVALID_TYPE|/usr/local/google/home/eernst/lang/dart/scratch/202105/n012.dart|10|9|1|The type 'Iterable<dynamic>' implied by the 'yield' expression must be assignable to 'Iterable<int>'.

However, the check should actually be performed based on the element type of f and g, namely int, so the question is whether dynamic is assignable to int, not whether Iterable<dynamic>/Stream<dynamic> is assignable to Iterable<int>/Stream<int>.

Analyzer now reports:
  error • 45971.dart:5:9 • A yielded value of type 'dynamic' must be assignable to 'int'. • yield_of_invalid_type
  error • 45971.dart:10:9 • A yielded value of type 'dynamic' must be assignable to 'int'. • yield_of_invalid_type


[ownership] Loosen restrictions around what we specialize and add generic specialization tests behind a flag.

The idea is that this will let me remove these assertions that were in place to
make sure we were really conservative around specializing ownership code. For me
to remove that I need to be able to actually test out this code (since I think
there are some code paths where this will trigger in other parts of the compiler
now).
So to work out the kinks, I added a flag that allows for the generic specializer
to process ownership code and translated most of the .sil test cases/fixed any
bugs that I found. This hopefully will expose anything that is missing.
NOTE: I have not enabled the generic specializer running in ownership in the
pipeline. This is just a step in that direction by adding tests/etc.

@eeckstein I fixed it by using a SmallBitVector. I learned about something new that I didn't know about: SmallBitVector now has an iterator for set bit indices! So you can just do:
for (int index : bitVector.set_bits()) { ... }

instead of:
for (int index = bitVector.find_first(); index != -1; index = bitVector.find_next(index)) { ... }

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 745f482a722942492f37429ef61b2ff1be26468b

Build failed
Swift Test Linux Platform
Git Sha - 745f482a722942492f37429ef61b2ff1be26468b

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 2e6f46c0627e4f51518f83cf06ed92856f4c1ad3

Build failed
Swift Test Linux Platform
Git Sha - 2e6f46c0627e4f51518f83cf06ed92856f4c1ad3

I was correct that we were missing code coverage. I added the missing code coverage of try_apply/begin_apply.

@swift-ci test

@swift-ci test

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 2e6f46c0627e4f51518f83cf06ed92856f4c1ad3

Build failed
Swift Test Linux Platform
Git Sha - 2e6f46c0627e4f51518f83cf06ed92856f4c1ad3

Build failed
Swift Test OS X Platform
Git Sha - 2e6f46c0627e4f51518f83cf06ed92856f4c1ad3

@swift-ci test windows platform

@swift-ci test OS X platform

OS X failure was a sandbox issue

Build failed
Swift Test OS X Platform
Git Sha - 77b094a470e872ee0814eb992487eded08dd6e40

I took a look at why we are failing/hitting the verifier error. The reason why is that there is a debug_value on self that is after the store [init] of self at the beginning of a function to materialize the argument.

Tracked down the problem. The issue was that I was creating a debug_value in the cloner too late. I put in a fix and also put in some things to make it easier to debug this sort of thing in the future:

A constructor for PrettyStackTraceSILFunction that takes a llvm::Twine so we can make more complex messages.
Added an -Xllvm flag that causes us to verify when we produce specializations and also added PrettyStackTraceSILFunction for the original unspecialized SIL function so if we hit a crash we can see the input to the specializer. That turned out to be very useful for me.

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test source compatibility

@swift-ci test source compatibility

@swift-ci test windows platform

@swift-ci test windows platform

Build failed
Swift Test Linux Platform
Git Sha - f4d40c6d974b4288ee3b61e01c9ccf629a12bc67

Build failed
Swift Test OS X Platform
Git Sha - f4d40c6d974b4288ee3b61e01c9ccf629a12bc67

Reproduced the error.

Interesting:
// thunk for @escaping @callee_guaranteed (@inout A, @guaranteed PathArgument) -> (@error @owned Error)
sil shared [transparent] [serializable] [reabstraction_thunk] [ossa] @$sx10TSCUtility12PathArgumentVs5Error_pIeglgzo_xACsAD_pIeglnzo_8Commands11ToolOptionsCRbzlTR : $@convention(thin) <Options where Options : ToolOptions> (@inout Options, @in_guaranteed PathArgument, @guaranteed @callee_guaranteed (@inout Options, @guaranteed PathArgument) -> @error Error) -> @error Error {
// %0                                             // user: %4
// %1                                             // user: %3
// %2                                             // user: %4
bb0(%0 : $*Options, %1 : $*PathArgument, %2 : @guaranteed $@callee_guaranteed (@inout Options, @guaranteed PathArgument) -> @error Error):
  %3 = load_borrow %1 : $*PathArgument            // users: %7, %10, %4
  try_apply %2(%0, %3) : $@callee_guaranteed (@inout Options, @guaranteed PathArgument) -> @error Error, normal bb1, error bb2 // id: %4

bb1(%5 : $()):                                    // Preds: bb0
  %6 = tuple ()                                   // user: %8
  end_borrow %3 : $PathArgument                   // id: %7
  return %6 : $()                                 // id: %8

// %9                                             // user: %11
bb2(%9 : @owned $Error):                          // Preds: bb0
  end_borrow %3 : $PathArgument                   // id: %10
  throw %9 : $Error                               // id: %11
} // end sil function '$sx10TSCUtility12PathArgumentVs5Error_pIeglgzo_xACsAD_pIeglnzo_8Commands11ToolOptionsCRbzlTR'

Bug in the reabstract thunk generation code.

Found the bug. It was my bug. Thank god for ownership verification = ).

I am going to try again tonight.

Tracked down the problem. The problem was that there was some misleading code that seemed like it was only handling apply inst. Instead it was also handling try_apply, but returning the normal block argument as the "result". This seems like a general useful property, so I put it into a helper on ApplySite. Now it all works.

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test source compatibility

@swift-ci test source compatibility

@swift-ci test source compatibility

Build failed
Swift Test Linux Platform
Git Sha - f4d40c6d974b4288ee3b61e01c9ccf629a12bc67

Build failed
Swift Test OS X Platform
Git Sha - f4d40c6d974b4288ee3b61e01c9ccf629a12bc67

@swift-ci test windows platform

Found more missing test coverage. We don't ever generate one of these reabstraction thunks with @out parameters in the test suite...

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test source compatibility

@swift-ci test source compatibility

@swift-ci test source compatibility

@swift-ci test windows platform

@swift-ci test windows platform

Looks like Source Compatibility matches the state on ci.swift.org. It isn't this commit.


Performance

Hi (probably more proper to write it here)
I incorporated in your shader engine into the project (happy ville). For now, I simply only transformed the resulting screen into a texture and rendered with your default shader. It was very simple and easy to use! However, I notised that my FPS dropped to 1 if I rendered each sprite via the shader engine.
I looked through the code but didn't notice anything obvious, and your example 2 seem to be handling many sprites fine. Do you know what could be the reason? Could it be that texture_surface that is the bottle neck? At the moment, this is called every frame for each sprite, and the background spites are quite big in happy ville.

I'll also copy here my reply from https://github.com/MarkelZ/pygame-light2d/issues/4
Yes, surface_to_texture is not meant to be used in every frame with large textures because the conversion from Surface to Texture is expensive. Instead, it's better not to use any pygame surfaces at all, and directly load the textures with load_texture and render them with render. You would need surface_to_texture only when you cannot avoid using pygame surfaces (for example because you need some specific pygame functionality).
I already checked out Happy Ville a while ago and it's really cool! I don't mind helping you increase the FPS but I would need more information about how you render stuff.

Ah, okay I understand. I just call the surface_to_texture in the initialisation of the classes instead and that seems to fix the issue. I notised that I needed to change the following line in util.py to make the "blit" position consistent though:
at line 56 from
x, y = position
to
x = position[0] * scale[0]
y = position[1] * scale[1]

You are right, that is much better. Thank you! :D
btw, do you happen to know an easy way to flip/mirror a sprite/texture? Or do I simply have to calculate the appropriate vertex coordinates?

@OlaKenji Yes! It's one of the arguments of render called flip. You can set flip=(True, False) to flip it horizontally. I added it in a recent update, 1.2.0, so if you don't see it maybe you need to download a newer version.

ah, that's a great feature! I downloaded your most recent code and works perfectly.

@OlaKenji Awesome, thank you so much for the feedback! I'll close the issue now because we fixed it, but feel free to open a new one if needed. Also, if you have any new feature ideas I'll be happy to hear about them :)


Add clarification on approve label for approvers

Issue #, if available:
Description of changes:
Added a clarification for PRs authored by approvers on how to use the approve label.
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Gizmo click detection is off by a constant

I have a Gizmo on a page that includes an app bar and a tool bar:

When I click on the X, -X, Z, -Y, buttons, the Gizmo does not respond. It behaves as though it is not receiving mouse clicks.
BUT, when I press the Y button, the camera moves to -Y. After some experimentation I found that the gizmo is receiving click events from the following locations:

So I suspect there's a hardcoded assumption somewhere that the <Canvas> extends to the top of the viewport.

Digging in a bit, the assumption seems to be made on this line
I'll see if I can make a patch!

PR is here: https://github.com/threlte/threlte/pull/810

closing for now. We have a new gizmo since #1254 was merged 🎉
happy for the issue to be reopen by OP if needed


Hidden Wallets balance should not be shown in total

When you hide a wallet, it’s balance should not appear in the total shown for wallets

Still it is showing a hidden wallet balance.
Tested in keeper app v 1.1.5(243)

https://github.com/bithyve/bitcoin-keeper/assets/62699947/515b7a43-b20c-4950-86c9-de33c4cb36b9

Completed verified on dev


Issue2989

Fixes #2989.
Changes proposed in this PR:

Prevent the project details page from displaying all guidance groups associated with an Org whose org_type is 'organization'.

It Iooks like I added this line over a year ago and don't recall why. Updated it to only use the default org's guidance.

why is something like Org.default_orgs equal to Org.where(abbreviation: Rails.configuration.x.organisation.abbreviation)? It is not documented
in the configuration and it surely has some unintended side effects?


WIP - TestNT

Created to determine differences between this and master

ninja's NT extracted and removed send interval changes:
https://github.com/MirrorNetworking/Mirror/pull/3410


weights and balances logging

wandb requires some additional arguments for logging than tensor board
logger = WandbLogger( save_dir=save_dir,
                                         log_model=True,
                                         project=wandb_config["project_name"],
                                         group=wandb_config["group"],
                                         name=experiment_name,
                                         job_type=wandb_config["job_type"],
                                        )

This will require some changes to the pydantic model that handles logging.   I'm creating this issue because I think we should address it in a separate PR, rather than PR #206 which is already rather large.

This has been addressed in PR #215 .


Introduce metric.Collector interface

This commit wraps the standard Prometheus metrics in interfaces. The idea is to support different ways to collect metrics while keeping Prometheus the default. I haven't addressed the gRPC metrics collection yet, but it's on my radar.
I'm opening this PR to gather feedback and address the ongoing conversation in #355. Happy to discuss anything and everything!

Cleanup!


Feature: languagetree

Here we finally are, language injection is coming.
This is the very first implementation, soon to be upstreamed as the future way to manage parsers within a buffer.
For now this does not do anything appart from actually creating the language tree, in the future we will use this as as way to highlight buffers, with native syntax highlighting.
Even crazier, we might be able to change "filetype" depending on the current cursor position, which I find cool.

lol wtf


feat : Add maven module for the git operations

Description

We have decided to create a new maven module which will handle all the git related operations and it will used in server similar to the way plugins are used today.

Fixes #5839
Type of change

New feature (non-breaking change which adds functionality)

How Has This Been Tested?

Locally

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

LGTM


add old API compatibility for login() to solve get_account_info() return 1 account issue

workaround of this issue, use version 0.2.3 or similar or call get_account_info_v2() in latest version like 0.3.5. Below change provides an alternative. The major limitation is that by calling v1 or old API, the quote_v2() etc cannot be used.
mainly modify the def login() in schwab_api/authentication.py
also add example/example_legacy_v1.py
either use get_account_info_v2() or add version='v1'  as the login() parameter for get_account_info() to correctly return all schwab accounts info. For best backward compatibility , we should change the def login() default to 'version=v1' and explicit claim 'version=v2' for new API. I don't think I can make that decision and it will change the colab example as well.
example usage case
logged_in = api.login(
    username=username,
    password=password,
    totp_secret=totp_secret, # Get this using itsjafer.com/#/schwab.
    version='v1'   # or use 'old'
)

# Get information about your accounts holdings
print("Getting account holdings information")
account_info = api.get_account_info()

@cnMuggle , can you try this alternative to solving the get_account_info problem: https://github.com/WinesProof/schwab-api/tree/get_account_info_all ?
Assuming it works for others, it would preserve compatibility between the v2 login process and get_account_info()

@cnMuggle , can you try this alternative to solving the get_account_info problem: https://github.com/WinesProof/schwab-api/tree/get_account_info_all ?
Assuming it works for others, it would preserve compatibility between the v2 login process and get_account_info()

your solution is better. I will close this. @itsjafer I tested the  https://github.com/WinesProof/schwab-api/tree/get_account_info_all from @WinesProof . It can solve the get_account_info() return 1 account issue without changing login()


Add standalone deriving as equivalent to instance postulate

This PR adds a way to derive type class instances which are available on the Agda side.
This is done by postulating the instance (there is no special pragma needed).
Agda:
data Optional (a : Set) : Set where
  Of    : a → Optional a
  Empty : Optional a
{-# COMPILE AGDA2HS Optional #-}

postulate instance iOptionalEq : ⦃ Eq a ⦄ → Eq (Optional a)
{-# COMPILE AGDA2HS iOptionalEq #-}

Haskell:
data Optional a = Of a
                | Empty

deriving instance (Eq a) => Eq (Optional a)

Deriving Strategies
It is also possible to specify a deriving strategy in the pragma.
NOTE: deriving via is not included, since that's quite a bit more complex.
Agda:
postulate instance iPlanetShow : Show Planet

{-# COMPILE AGDA2HS iPlanetShow strategy:stock #-}

Haskell:
deriving stock instance Show Planet

@lucas, I've added support for compiling implemented as well as postulated instances into a deriving clause. This can now be done with the derive pragma, which has also replaced the strategy annotation.


Feature Request - Changeable Title or Logo

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
I'd like an option to change the title and logo on the left side panel so that I can easily identify a version of Papermerge. I'd like to use two versions for different repositories. I need them to be separate.
Describe alternatives you've considered
Either changing the logo or changing the title will be sufficient

Additional context
Add any other context or screenshots about the feature request here.

Regarding version: you can see it in user's menu (upper right corner of the screen) -> About.
Version in "About" dialog is read from GET /api/version REST API endpoint.
REST API docs reference you can get from same user menu -> REST API.

I understand about the PM version. If there are two instances of papermerge on the same server, it would be helpful to have a visual way of quickly identifying which instance is being used in the browser tab. That's what I mean by version. I'll be using PM version 3 in both instances.
Thanks.


Support Koi Testnet

This PR does NOT need to be merged.
The Latest Staking Rewards doesn't work because the index doesn't exist.

https://docs.darwinia.network/build/getting-started/networks/pangolin/
Pangolin has been removed, please support Koi instead.

https://docs.darwinia.network/build/getting-started/networks/pangolin/
Pangolin has been removed, please support Koi instead.

Done

subql is not working for Koi?
network issues for
https://subql.darwinia.network/subql-apps-pangolin/

https://staking-ds2aseeix-itering.vercel.app

Yeah, subql is only used in Latest Staking Rewards. I'll see if I can deploy one later if necessary.


Update Tree branch and item to use new SLDS HTML tags

Additional description
When the Tree component is used for left hand navigation, which is quite often, when the tree gets big and expands to the whole space, when users hover over a item/branch, the link URL is displayed in the lower left hand corner of the browser window (Chrome).
We've seen that if the link element is long or the tree item is short user's can miss the tree item at the bottom of the screen.
To combat this, we are submitting this PR which removes the href attr from the Tree's branch and item.
After checking W3, we've found the following:

If the a element has no href attribute, then the element represents a placeholder for where a link might otherwise have been placed, if it had been relevant, consisting of just the element’s contents.

Pull Request Review checklist (do not remove)

[ ] npm run lint:fix has been run and linting passes.
[ ] Mocha, Jest (Storyshots), and components/component-docs.json CI tests pass (npm test).
[ ] Tests have been added for new props to prevent regressions in the future. See readme.
[ ] Review the appropriate Storybook stories. Open http://localhost:9001/.
[ ] The Accessibility panel of each Storybook story has 0 violations (aXe). Open http://localhost:9001/.
[ ] Review tests are passing in the browser. Open http://localhost:8001/.
[ ] Review markup conforms to SLDS by looking at DOM snapshot strings.
[ ] Add year-first date and commit SHA to last-slds-markup-review in package.json and push.
[ ] Request a review of the deployed Heroku app by the Salesforce UX Accessibility Team.
[ ] Add year-first review date, and commit SHA, last-accessibility-review, to package.json and push.
[ ] While the contributor's branch is checked out, run npm run local-update within locally cloned site repo to confirm the site will function correctly at the next release.

@interactivellama does this look good?

Looks good! Thanks for the update.


Slider does not seem to respect click handlers

Describe the bug
Not sure exactly what is going on but I am trying to stop clicks going through to SliderView in TGD.  This approach seems to work for other views.
I tried looking at gui.cs\UnitTests\Views\SliderTests.cs` for mouse tests but couldn't see any to adapt for repro.
if (subView.GetType().IsGenericType(typeof(Slider<>)))
{
    // TODO: Does not seem to work
    subView.MouseEvent += (s, e) => SuppressNativeClickEvents(s, e,true);
    subView.MouseClick += (s, e) => SuppressNativeClickEvents(s,e, true);
}

...

private void SuppressNativeClickEvents(object? sender, MouseEventEventArgs obj, bool alsoSuppressClick = false)
{
    if (alsoSuppressClick)
    {
        obj.Handled = true;
    }
    else
    {
        // Suppress everything except single click (selection)
        obj.Handled = obj.MouseEvent.Flags != MouseFlags.Button1Clicked;
    }
}

Perhaps the SliderView respond to ButtonPressed and thus you must also suppress it?

I don't see a ButtonPressed event.
The above code passes true so it suppress everything, making the method effectively just be blanket:
obj.Handled = true;

Slider overrides OnMouseEvent. it should not as that method is internal in v2. This is a legacy from v1 that has not been fully addressed yet. The shole mouse eventing neeeds to be fixed. See:

#3029

When that's done, Slider needs to be refactored to be correct.
In the meantime... The bug is in Slider's override of OnMouseEvent
It's returning true somewhere where it should be returning false or vice versa.


[Feature Request] Support Specifying InfluxDB Database Name

Is your feature request related to a problem? Please describe.
Shared InfluxDB service where I can't choose my own database name.
Describe the solution you'd like
Add support for a database variable in the config file.
[influxdb]
database = database-name

we intentionally removed this long ago. i highly doubt you have any other databases named varken

As describe in the request I'm using a service that provides me with an influxdb account and a database. Its a shared service. The database name is auto-generated.

That is an unfortunate service you have. An edge case does not validate the need for something that the masses will mess up often. In its current state you will need to build from source and modify https://github.com/Boerderij/Varken/blob/8877b7b3c1be76f445d5637b32f4c4bef4d30928/varken/dbmanager.py replacing varken with the name of your db. in the appropriate lines.