Add static error tests for DDC and dart2js

https://dart-review.googlesource.com/c/sdk/+/130733 adds some static checks that apply only in DDC and Dart2JS for now. We need to add tests for these, but the current infrastructure expects to run tests for static errors with front end and analyzer only.
@munificent - do you have any ideas on the best approach for this?

Do these tests still work?
https://github.com/dart-lang/sdk/blob/15b6f19008e34e5cdcfb555ac899d29dcbd0f1f1/tests/compiler/dart2js_extra/non_jsinterop_test.dart#L23
cc @sigmundch

cc @johnniwinther - I see a note about sharing these tests with DDC:
https://github.com/dart-lang/sdk/blob/15b6f19008e34e5cdcfb555ac899d29dcbd0f1f1/tests/compiler/dart2js_extra/non_jsinterop_test.dart#L5
Do you have any background you can share on these tests? How do I run them? How would I update these if I fix some of the missing compile time errors? Is it enough to remove some lines from the legacy_status_dart2js.csv file? https://github.com/dart-lang/sdk/blob/d99f6bffcb11f21def4cee7032039512b220684c/tests/legacy_status_dart2js.csv#L37
What do you expect it would take to have use this test for DDC?

tests/compiler/dart2js_extra/non_jsinterop_test.dart and it's sibling
tests/compiler/dart2js_extra/jsinterop_test.dart can be as multitests with
test.py:
python ./tools/test.py --arch=x64 -mrelease -cdart2js -rd8
dart2js_extra/jsinterop
This tests that error case behaves as expected - which it current doesn't.
This way of running the tests should be fairly easy to use for DDC since it
only relies on an error being reported or not.
The expectations in these tests (in comments like //
JS_INTEROP_FIELD_NOT_SUPPORTED ) are tested with the dart2js unittest:
dart tests/compiler/dart2js/model/native_test.dart
This tests that dart2js reports the expected error for the error cases, as
well as reasons as expected about which classes and members are
native/jsinterop.
This test is hard to use for DDC since it relies on the exact kinds of
errors reported and these error kinds are currently internal to dart2js.
When reporting some more errors should remove the corresponding line
numbers mentioned in the 'skipList' entries in
tests/compiler/dart2js/model/native_test.dart to verify that dart2js now
emits the expected error.
I didn't know about tests/legacy_status_dart2js.csv so I don't know whether
it is necessary to remove the lines here, but it seems that we should.
On Fri, 28 Feb 2020 at 02:02, Nate Bosch<EMAIL_ADDRESS>wrote:

cc @johnniwinther https://github.com/johnniwinther - I see a note about
sharing these tests with DDC:
https://github.com/dart-lang/sdk/blob/15b6f19008e34e5cdcfb555ac899d29dcbd0f1f1/tests/compiler/dart2js_extra/non_jsinterop_test.dart#L5
Do you have any background you can share on these tests? How do I run
them? How would I update these if I fix some of the missing compile time
errors? Is it enough to remove some lines from the
legacy_status_dart2js.csv file?
https://github.com/dart-lang/sdk/blob/d99f6bffcb11f21def4cee7032039512b220684c/tests/legacy_status_dart2js.csv#L37
What do you expect it would take to have use this test for DDC?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dart-lang/sdk/issues/40360?email_source=notifications&email_token=AC6ZYJKWWD6ICQD4EYEBVYLRFBPBBA5CNFSM4KM2G3V2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOENGR5WQ#issuecomment-592256730,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC6ZYJMGQQCY4O5DR3DDRRDRFBPBBANCNFSM4KM2G3VQ
.

I didn't know about tests/legacy_status_dart2js.csv so I don't know whether
it is necessary to remove the lines here, but it seems that we should.

Deleting the relevant entries sounds good. My understanding is that Karl added this file to track the comments that long ago were written in .status files. It was added to make it possible to delete the extra entries in the status files without loosing the information that linked test failures and github issues. Besides being data, I believe the .csv file has no other purpose and is not involved in any test execution/status.

Looks like there are more similar tests at https://github.com/dart-lang/sdk/blob/1fe6ca96d0665fe57af0d14a156aa97b361f480c/tests/compiler/dart2js/jsinterop/declaration_test.dart

Off the top of my head, one option would be to add a new requirement like:
// Requirements=web-compiler

And then add a little special logic to the test runner to only run static error tests if:

The configuration is front end or analyzer.
Or the configuration is DDC or dart2js and this requirement is present.

That would cause these tests to not get skipped while also avoiding running all of other the static error tests on DDC and dart2js.
It feels a little hacky, though. I was hoping the limited Boolean logic supported by the requirements stuff would be sufficient but it seems we keep running into cases like this where we want to express something more complex. Maybe we should do actual Boolean expression support like the status files support for matching test groups, but place it in the test file itself.

Here's a better idea now that I've put a little brain juice into it:
In the test runner, we use the specific static error test markers to determine which platforms to run a static error test on. So if it contains a [cfe] marker, then we run it on the CFE. [analyzer] gets it run on analyzer. On any other platforms, the test is skipped. This mirrors the behavior we see today since every static error test does contain both [cfe] and [analyzer] markers.
Then we add a third marker like [web] for errors that should be reported by DDC and dart2js. Any test containing one of those markers is run by DDC and dart2js as a static error test. If the test only contains that marker, then the other platforms will implicitly skip it.
How does that sound?

love it!

This is all done now.


Multiple misformatted blocks

There are multiple misformatted blocks:
1)
> [!CAUTION]
> To activate an app and
...
2)
> [!NOTE]
> ListenFor elements cannot
...
3) csharp code sample doesn't have syntax highlighting

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

ID: d89fa6b4-6807-4461-59a4-e87df41ee821
Version Independent ID: 96edbcb1-a8c9-9cf5-1f5a-1a8421a5745e
Content: Activate a foreground app with voice commands through Cortana - Cortana UWP design and development - Cortana
Content Source: docs/voice-commands/launch-a-foreground-app-with-voice-commands-in-cortana.md
Product: cortana
GitHub Login: @JohnBucyMSFT
Microsoft Alias: jobucy

Fixed. Thanks for telling us!


Split out interpreter path related settings from general configuration service

Ideally we should separate each setting type to its own component. But for now interpreter path settings has grown to have a lot of special cases in configSettings.ts.

It is especially manipulated/validated before use.
It should be handled asynchronously to solve many of these issues: https://github.com/microsoft/vscode-python/issues/12452
In many cases we are forced to use workspace service to access other settings instead of configuration service, due to tangled or cyclic dependency issues with interpreter path settings: https://github.com/microsoft/vscode-python/blob/f530a5c0e60b6b2ef7a04a10eddbf929cd6b2064/src/client/extensionActivation.ts#L117
https://github.com/microsoft/vscode-python/blob/4bc4dc6f5faafebd20a3c83c64e15caf71a5edf0/src/client/interpreter/configuration/interpreterSelector/commands/setInterpreter.ts#L165

Actually, every component should have it's own settings class. Just having an issue open for interpreter setting seems not so useful. We can do this as and when we split the extension up.


Feature/enhance adddebt duplicate detection

Resolves #166

Codecov Report
Base: 72.63% // Head: 72.82% // Increases project coverage by +0.18% :tada:

Coverage data is based on head (d10c1a3) compared to base (d1e618d).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@             Coverage Diff              @@
##             master     #178      +/-   ##
============================================
+ Coverage     72.63%   72.82%   +0.18%
- Complexity      673      676       +3
============================================
  Files           104      105       +1
  Lines          2229     2237       +8
  Branches        290      291       +1
============================================
+ Hits           1619     1629      +10
+ Misses          504      501       -3
- Partials        106      107       +1

Impacted Files
Coverage Δ

...n/java/paymelah/logic/commands/AddDebtCommand.java
97.29% <100.00%> (+0.32%)
:arrow_up:

src/main/java/paymelah/model/debt/DebtList.java
71.79% <100.00%> (+0.74%)
:arrow_up:

.../model/debt/exceptions/DuplicateDebtException.java
100.00% <100.00%> (ø)

src/main/java/paymelah/model/ModelManager.java
73.97% <0.00%> (+2.73%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


⚠ SceneTime has degraded performance

In b18cd3e, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 3515 ms

Resolved: SceneTime performance has improved in 22abc2f after 22 minutes.


Add Ability for User to Specify Rebase Rate instead of APY on Staking Simulator

A nice to have to allow the user to input either the APY (as it is now) or the current rebase rate.

Using APY seems to be the preferred approach from beta testers


python311Packages.feedparser: 6.0.10 -> 6.0.11

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 275358 run on x86_64-linux 1

3 packages marked as broken and skipped:

home-assistant-component-tests.abode
home-assistant-component-tests.feedreader
netbox_3_5

2 packages failed to build:

pubs
pubs.dist

82 packages built:

appdaemon
appdaemon.dist
calibre
canto-curses
canto-curses.dist
canto-daemon
canto-daemon.dist
comic-mandown
comic-mandown.dist
flexget
flexget.dist
foxtrotgps
gnome-feeds
gpodder
greg
greg.dist
netbox (netbox_3_6)
octoprint
octoprint.dist
offpunk
offpunk.dist
python310Packages.feedparser
python310Packages.feedparser.dist
python310Packages.jaraco-abode
python310Packages.jaraco-abode.dist
python310Packages.jaraco-net
python310Packages.jaraco-net.dist
python310Packages.limnoria
python310Packages.limnoria.dist
python310Packages.mandown
python310Packages.mandown.dist
python310Packages.nptyping
python310Packages.nptyping.dist
python310Packages.pynrrd
python310Packages.pynrrd.dist
python310Packages.rsskey
python310Packages.rsskey.dist
python310Packages.weboob
python310Packages.weboob.dist
python311Packages.feedparser
python311Packages.feedparser.dist
python311Packages.jaraco-abode
python311Packages.jaraco-abode.dist
python311Packages.jaraco-net
python311Packages.jaraco-net.dist
python311Packages.limnoria
python311Packages.limnoria.dist
python311Packages.mandown
python311Packages.mandown.dist
python311Packages.nptyping
python311Packages.nptyping.dist
python311Packages.pynrrd
python311Packages.pynrrd.dist
python311Packages.rsskey
python311Packages.rsskey.dist
python311Packages.weboob
python311Packages.weboob.dist
quodlibet
quodlibet-full
quodlibet-full.dist
quodlibet-full.doc
quodlibet-without-gst-plugins
quodlibet-without-gst-plugins.dist
quodlibet-without-gst-plugins.doc
quodlibet-xine
quodlibet-xine-full
quodlibet-xine-full.dist
quodlibet-xine-full.doc
quodlibet-xine.dist
quodlibet-xine.doc
quodlibet.dist
quodlibet.doc
rss2email
rss2email.dist
rss2email.doc
rss2email.man
sabnzbd
tartube
tartube-yt-dlp
tartube-yt-dlp.dist
tartube.dist
unbook

Result of nixpkgs-review pr 275358 run on x86_64-linux 1

3 packages failed to build:

quodlibet-xine
quodlibet-xine.dist
quodlibet-xine.doc

81 packages built:

appdaemon
appdaemon.dist
calibre
canto-curses
canto-curses.dist
canto-daemon
canto-daemon.dist
comic-mandown
comic-mandown.dist
flexget
flexget.dist
foxtrotgps
gnome-feeds
gpodder
greg
greg.dist
netbox (netbox_3_6)
octoprint
octoprint.dist
offpunk
offpunk.dist
pubs
pubs.dist
python310Packages.feedparser
python310Packages.feedparser.dist
python310Packages.jaraco-abode
python310Packages.jaraco-abode.dist
python310Packages.jaraco-net
python310Packages.jaraco-net.dist
python310Packages.limnoria
python310Packages.limnoria.dist
python310Packages.mandown
python310Packages.mandown.dist
python310Packages.nptyping
python310Packages.nptyping.dist
python310Packages.pynrrd
python310Packages.pynrrd.dist
python310Packages.rsskey
python310Packages.rsskey.dist
python310Packages.weboob
python310Packages.weboob.dist
python311Packages.feedparser
python311Packages.feedparser.dist
python311Packages.jaraco-abode
python311Packages.jaraco-abode.dist
python311Packages.jaraco-net
python311Packages.jaraco-net.dist
python311Packages.limnoria
python311Packages.limnoria.dist
python311Packages.mandown
python311Packages.mandown.dist
python311Packages.nptyping
python311Packages.nptyping.dist
python311Packages.pynrrd
python311Packages.pynrrd.dist
python311Packages.rsskey
python311Packages.rsskey.dist
python311Packages.weboob
python311Packages.weboob.dist
quodlibet
quodlibet-full
quodlibet-full.dist
quodlibet-full.doc
quodlibet-without-gst-plugins
quodlibet-without-gst-plugins.dist
quodlibet-without-gst-plugins.doc
quodlibet-xine-full
quodlibet-xine-full.dist
quodlibet-xine-full.doc
quodlibet.dist
quodlibet.doc
rss2email
rss2email.dist
rss2email.doc
rss2email.man
sabnzbd
tartube
tartube-yt-dlp
tartube-yt-dlp.dist
tartube.dist
unbook


Find ways to work with the React framework

If the application has its own model, Yorkie will provide a change handler that can synchronize with the application's model in the document.
On the other hand, we decided to find a way to use Yorkie directly as a model for the application.
First, Yorkie provides a native interface using Javascript Proxy like Immer, so we will find a way how to interact with the React framework in a similar way to Immer.
https://github.com/immerjs/immer

@lqez tweeted that when there is a new idea, he starts development with the following flow:
https://twitter.com/lqez/status/1245246793429864449
It would be nice if Yorkie could naturally help with this flow.

BTW, do you have a plan to rename the project from Yorkie to Yoki? 😄

It was a typo. 👍

For now, we simply implemented TodoMVC on create-react-app using Yorkie.
https://github.com/yorkie-team/yorkie-react-todomvc
Similar to the kanban board example implemented with Vue.js lately, whenever there is a change, the entire model is delivered to the React state.
https://github.com/yorkie-team/yorkie-team.github.io/blob/master/static/js/demo-kanban.js#L101-L106
https://github.com/yorkie-team/yorkie-react-todomvc/blob/master/src/App.tsx#L68-L72
I think we should check performance optimization later.

@easylogic told me Nowadays, React developers use Function component and Hooks API instead of Stateful Component. I think It would be nice to change the code style.
https://github.com/yorkie-team/yorkie-react-todomvc

Could you elaborate further on what is expected with this issue?
Are you thinking of refactoring this? https://github.com/yorkie-team/yorkie-react-todomvc

I'm not familiar with React, so I'm not sure if the way we are providing is appropriate, so I left this open. We are waiting for feedback from developers familiar with React.

I've interested in this issue. I think if yorkie-js-sdk provides the wrapper using React Context, it can improve the usability of the SDK for React. In terms of that the Document in yorkie-js-sdk looks like the central data of Redux, so studying the implementation of Redux will be helpful to get some ideas.
However, the Document in yorkie-js-sdk is the central data, which is irrelevant to the data in React. So, the update of Document cannot automatically lead the re-render of the React view. Therefore, in our React SDK, we may save the same data twice, one for Document and the other for React state. The implementation will update the React state using setState after  the update of Document. Then, this state value will be added to React Context. (This idea is basically same with Redux, even I'm not sure the details of the Redux implementation.)
I don't like the idea of this duplication, but, at this point, I don't have any nicer idea.

Firestore has Redux bindings.
https://github.com/prescottprue/redux-firestore

We are providing a React-based TodoMVC example.
https://github.com/yorkie-team/yorkie-react-todomvc
We will reopen if additional requirements arise.


"Access control using whitelists" subtask needs verification action

https://istio.io/docs/tasks/security/basic-access-control.html
Once the config is created, there should be some small section on validation -- even if it only involves telling users to delete the old deny rule and repeat the v3 validation bits again. It isn't clear what observable effect users should expect.
This may, in part, be because the text:

We would like to cut off access to version v3 of the reviews service.

lives inside of the other subtask and not at a higher level.

FIxed in https://github.com/istio/istio.github.io/pull/639


end-to-end example of UCI Dataset

Initial start for the UCI Dataset Airfoil. I will further add code for plotting and scaling the input using ZScoreTransform from ScikitLearn.jl.

Hello! thanks for this, it's a good start. I would suggest:

adding a few rounds of hyperparameter tuning with cross validation
adding a comparison with another classifier

yes plots would be very welcome too, thanks :+1:

Readme changes are all fine by me, thanks!

@tlienart I have added the comparison of DecisionTreeRegressor with RandomForestRegressor and have performed hyperparameter tuning too. I have made  use of Standardizer and also plotted a heatmap.
Could you please review the same.

Thanks a lot for your contribution @ashryaagr , looks good to me at first glance, I'll do another full depth pass within the next few days. Cheers!

Sorry for the delay, there seems to be a bug in how CSV reads requests like this, the line to recover the data doesn't seem to work anymore.

nvm, it's an issue with CSV, fixed by upgrading.

ok that looks good, I've done a few fixes/changes and added your name at the top (thanks!!) and will merge this.

closing in favour of #51 , thanks!

Thanks for this both @tlienart @ashryaagr ! 💪


Do not treat a class as automatically-convertible bean if it has a me…

…mber which is not injectable
Motivation:
The server cannot be started if there is a parameter when there is a parameter unable to be injected on a constructor or method of a bean specified as @RequestObject. This behavior makes a user confused when he or she adds a member variable of one of the automatically-injectable types, such as HttpRequest and RequestContext, to his or her class which is not an automatically-convertiable class. We need to skip checking the class for this case because the class may be converted by one of the user-defined request converters.
Modifications:

Throw NoAnnotatedParameterException instead of IllegalArgumentException when there is a parameter unable to be injected on a constructor or method of a bean specified as @RequestObject.

Thanks, @hyangtack !


Fixed

Before filing an issue
Check Frequently Asked Questions
Describe the bug
A clear and concise description of what the bug is.
Expected behavior
A clear and concise description of what you expected to happen.
Enable logging at the debug level and attach/past to the issue
Attach logs
Code To Reproduce the Issue
Show code that reproduces the issue
Additional context
Add any other context about the problem here.

https://github.com/moozzyk/SignalR-Client-Swift.wiki.git

Seems like a mistake. Closing.


Use an rbd pool per tenant

When we create a new tenant we need to create a new pool in rbd and then change the ciao-storage code to also take a tenant ID.

needed for #713

Evaluated this but pools are not the right layer of grouping for this problem as they are a fixed partitioning of the cluster.


[Feature request] Is there a release date for the FromConfiguration method to come back?

Context / Scenario
In my project, I was using the KernelMemoryBuilder.FromConfiguration extension method, but after a package update I can't do it anymore.
I saw the method has been reduced and is now present in the package named "Microsoft.KernelMemory.Service". The thing is I can't find the nuget package for my project so I can't use the method anymore.
What happened?
You already responded to me that the Service project where the method is is not deployed. I already tried to import only the data I need but it requires to copy all the Service project.
Importance
a fix would make my life easier
Platform, Language, Versions
.net, last Microsoft.KernelMemory.Core version
Relevant log output
No response

See https://github.com/microsoft/kernel-memory/issues/283


dart2js: serialization failure with ContainerTypeMask for very large array

https://dart-review.googlesource.com/c/sdk/+/107922/2 fails
Patch the cl and run tools/test.py -n dart2js-hostasserts-linux-x64-d8 language_2/list_test
The crash is in serializing a ContainerTypeMask with a large size that originates from the expression new List(0x7ffffffffffff000).
The compiler crashed: 'package:compiler/src/serialization/abstract_sink.dart': Failed assertion: line 237 pos 12: 'value >= 0 && value >> 30 == 0': is not true.
#0      _AssertionError._doThrowNew (dart:core-patch/errors_patch.dart:40:39)
#1      _AssertionError._throwNew (dart:core-patch/errors_patch.dart:36:5)
#2      AbstractDataSink.writeInt (package:compiler/src/serialization/abstract_sink.dart:237:12)
#3      DataSinkMixin.writeIntOrNull (package:compiler/src/serialization/mixins.dart:395:7)
#4      ContainerTypeMask.writeToDataSink (package:compiler/src/inferrer/typemasks/container_type_mask.dart:56:10)
#5      CommonMasks.writeAbstractValueToDataSink.<anonymous closure> (package:compiler/src/inferrer/typemasks/masks.dart:867:42)
#6      AbstractDataSink.writeCached.<anonymous closure> (package:compiler/src/serialization/abstract_sink.dart:99:31)
#7      IndexedSink.write (package:compiler/src/serialization/helpers.dart:355:17)
#8      AbstractDataSink.writeCached (package:compiler/src/serialization/abstract_sink.dart:99:10)
#9      CommonMasks.writeAbstractValueToDataSink (package:compiler/src/inferrer/typemasks/masks.dart:866:10)
#10     GlobalTypeInferenceMemberResultImpl.writeToDataSink (package:compiler/src/inferrer/types.dart:438:25)
#11     GlobalTypeInferenceResultsImpl.writeToDataSink.<anonymous closure> (package:compiler/src/inferrer/types.dart:264:20)
#12     DataSinkMixin.writeMemberMap.<anonymous closure> (package:compiler/src/serialization/mixins.dart:529:10)
#13     __InternalLinkedHashMap&_HashVMBase&MapMixin&_LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:367:8)
#14     DataSinkMixin.writeMemberMap (package:compiler/src/serialization/mixins.dart:527:11)
#15     GlobalTypeInferenceResultsImpl.writeToDataSink (package:compiler/src/inferrer/types.dart:261:10)
#16     serializeGlobalTypeInferenceResults (package:compiler/src/serialization/task.dart:32:11)
#17     BytesInMemorySerializationStrategy.serializeData (package:compiler/src/serialization/strategies.dart:59:5)
#18     Compiler.compileFromKernel.<anonymous closure> (package:compiler/src/compiler.dart:431:37)

The options to fix this are:

Serialize the container length with a method capable of serializing all lengths. This may include constants from constant-folding to values outside the int64 range.
Constrain the discovered length to the range of values that may be serialized.

/cc @johnniwinther WDYT?

Fixed via 327f5eb82653e3ccfe0b5920af5c8e01335cee12


add support to deploy to gh-pages

Not sure whether this has been done or not, but apparently I was trying to use the techniques found from
https://medium.freecodecamp.org/surge-vs-github-pages-deploying-a-create-react-app-project-c0ecbf317089
and
https://github.com/rafrex/spa-github-pages
to deploy the react-static generated site to github through gh-pages.
Anyone?

I would suggest just uploading the dist folder to GitHub pushed like you
would any other site. But use the hash router by placing the type='hash'
on the Router component.
On Sat, Nov 18, 2017 at 7:38 PM killvung<EMAIL_ADDRESS>wrote:

Not sure whether this has been done or not, but apparently I was trying to
use the techniques found from
https://medium.freecodecamp.org/surge-vs-github-pages-deploying-a-create-react-app-project-c0ecbf317089
and
https://github.com/rafrex/spa-github-pages
to deploy the react-static generated site to github through gh-pages.
Anyone?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/185, or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCcdDF6QJbWr_nF1jqW-MXZHZAViIks5s35SqgaJpZM4QjOwr
.


[SPARK-19353][CORE] Generalize PipedRDD to use I/O formats

This commit allows to use arbitrary input and output formats when
streaming data to and from the piped process. The API uses
java.io.Data{Input,Output} for I/O, therefore all method operating
on multibyte primitives assume big-endian byte order.
The change is fully backward-compatible in terms of both public API
and behaviour. Additionally, existing line-based format is available
via TextInputWriter/TextOutputReader.
Note 1: this change is 1.6.X specific but it includes some bug fixes implemented only in 2.X.
Note 2: for 2.X version see pipe-binary-io branch.

Don't merge just yet: there is a performance regression for text data, see apache/spark#17230.

Decided to keep this outside of Spark.


Link on top of your github page has extra s

Hello,
This looks interesting.
The link on the top of https://github.com/bashtage/linearmodels points to
https://bashtage.github.io/linearmodels/docs
I think there is an extra "s" in "docs"

Thanks - I changed it to doc at some point and missed that one.


Storybook 8 compatibility

Hey @hwookim ! I’m reaching out from the core SB team :)
Storybook 8 (our next major release) is coming soon, and it introduces some breaking changes that your addon might need to account for.
We’ve listed all the key changes in a new Storybook 8 migration guide, and we’d encourage you to check it out and see if your addon is impacted.
We also have an addons channel in our Discord community, which we’d like to use to better communicate with addon authors in the future. If you’re not part of the server, consider joining here and message me (@joevaugh4n) so that I can give you the addon creator role! If you’re already in the server, please just ping me and I’ll respond to you there.
Thanks for being a part of our addon community!
Joe

I had a go at pulling the repo and upgrading those dependencies and then upgrading the demo Storybook to v8.0 and all seemed to work well, with the exception of the demo Storybook autogenerated docs page throwing a type error. Happy to push a PR if that's any help.

I had a go at upgrading:

"@storybook/blocks": "^7.0.0",
"@storybook/components": "^7.0.0",
"@storybook/manager-api": "^7.0.0",
"@storybook/preview-api": "^7.0.0",
"@storybook/types": "^7.0.0",

"@storybook/blocks": "^8.0.0",
"@storybook/components": "^8.0.0",
"@storybook/manager-api": "^8.0.0",
"@storybook/preview-api": "^8.0.0",
"@storybook/types": "^8.0.0",

and then the demo Storybook up to v8.0 and seemed to work well

i threw this together. https://github.com/hwookim/storybook-addon-cookie/pull/11

I apologize for the delay in handling this issue.
I'll do my best to get it taken care of this week.

Thank you for the update! Is there anything in particular why the alpha release for 4.0 and not a full one?

@fernandopasik
There are a few issues we haven't resolved yet. #12  T.T
There is an issue with the parameter not being called properly on initial load and therefore not being properly exposed in the toolpane, which i'm still trying to resolve.
I'll try to resolve them as soon as possible!


chore(ci): error if uncomitted changes found on build

Description
This addition will fail the CI workflow if any uncommitted assets are found at the end of the build process.
How and where has this been tested?
On a fork branch of this PR, remove one or more of the mods.md assets from any component.

[x] Expect CI to fail after the build step with a note that the mods.md assets are missing. Said note will exist in the log for the GitHub Action workflow.  https://github.com/adobe/spectrum-css/pull/2340

To-do list

[x] I have read the contribution guidelines.
[x] ✨ This pull request is ready to merge. ✨

A todo for later might be to report that information back to the pull request. I'll open a Jira ticket for that feature though because it's probably about an hour or so of work to do that.


Unbound methods, interest in autobinding?

I noticed methods on all objects are unbound, e.g.
// https://tonicdev.com/marionebl/5755b0178b908f130020fd9d
var Github = require('github-api');
var github = new Github();
var getRepo = github.getRepo;

var repo = getRepo();
// => Cannot read property '_getFullName' of undefined

Of course this can be fixed easily by changing it to:
// https://tonicdev.com/marionebl/5755b4e28b908f130020fedb
var Github = require('github-api');
var github = new Github();
var getRepo = github.getRepo.bind(github);

var repo = getRepo();

This is rather clumsy and moves the work to bind the methods to their respective host objects to users although it could easily be done by the library.

Are you interested in a PR that auto binds all methods?
Which would be the preferred way to do it?

Assignment in constructor:

// https://tonicdev.com/marionebl/5755b612c91caa1300f72617
...
this.bar = this.bar.bind(this);
...

Tool-facilitated assignment in constructor

https://tonicdev.com/marionebl/5755b612c91caa1300f72617
import autobind from '...';
...
autobind(this);
...

Class properties (needs additional experimental babel plugins)

...
  bar = () => {
    return this.__barMessage;
  }
...

An autobind decorator (needs experimental/disabled decorator babel plugin)

@autobind()
class Foo {
...
}

While the issue you document will currently occur–Javascript in general behaves in this manner–is there a reason to have everything bound by default?
Could you elaborate on your use case for having methods bound?

The reason is purely to provide a more convenient developer interface. An example use case would be e.g. conversion to promise based / async-await control flows:
import denodeify from 'denodeify';
import Github from 'github-api';

const github = new Github();
const getRepo = denodeify(github.getRepo);

async function main() {
 const repo = await getRepo();
 return repo;
}

main()
  .then()
  .catch(error => {
     // barfs with:
     // => TypeError: Cannot read property '_request' of undefined
  });

Why not:
import Github from 'github-api';

const github = new Github();

async function main() {
 const repo = await github.getRepo('michael', 'github');
 return repo;
}

main()
  .then(repoJson => {
    // do stuff
  }).catch(error => {
  });

You're going to need to pass things around (whether they're functions or the github instance) so I don't see any advantage to pulling instance methods off of the instance.
I guess to answer the question you asked I don't think that this is something we'd like to support by default. However, if you submit a PR that enables this behind a flag or option upon instantiation then I guess I don't have a problem with it. It just doesn't feel very javascript-y.
See React's reasoning for dropping support for auto-bound methods like this as they transition to ES6+ usage.

Thanks for the clarification and fast response. Makes a lot of sense to me. 👍


Preparing release 1.1.3

Coverage remained the same at 92.759% when pulling b385ed065bc0aafd9dba2186d424f71ded6c0795 on deniszh:DZ-1.1.3 into 19b789580c2217da975d7f871e6bbda59441c166 on graphite-project:1.1.x.


boscore-polkadot-bridge

Grant Application Checklist

[x] The application-template.md has been copied, renamed ( "boscore-polkadot-bridge.md") and updated.
[x] A BTC address for the payment of the milestones is provided inside the application.
[x] The software of the project will be released under the Apache license version 2.0 as specified in the terms and conditions.
[x] The total funding amount of the project is below 30k at the time of submission.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks David, the smart contracts are for WASM execution and C++ / Rust implementations for relay nodes. I’ve moved the principle and design documentation from milestone 1 to 2 (item 2) so it can be updated to including applicable differences in transaction data, signature addressing, block structures, and so on. FTE and costs amended accordingly.
With that said, we are reviewing the open application and considering the progressing of the general grant application.

Thanks, let me know how you want to proceed.

change to general grant and close this pr


Login "stay signed in"

Hello,
I would like to ask if its possible to deactivate this feature / to modify it.

That the "Stay signed in" Checkbox is always checked, is from my perspective, a bad idea.
It would be better, to leave it unchecked for a better user expierence.
Feel free to correct me on this.

If you really want to, you can edit this line:
https://github.com/thelounge/lounge/blob/d4e02d96fa4a9d6d25262b552e9ddabae50e9952/client/index.html#L102

Hey @RaymondSchnyder, thanks for your interest 😊
However, when it comes to user experience actually, I disagree: by default, most users will not want to be signed out when closing their browser.
I checked with a bunch of website and most often, that "Remember me option" is checked in. In fact, most websites I have checked do not even have such an option (!) and none of them ask me to re-login when I close and re-open my browser, meaning they assume that users want to stay logged in by default.
Closing as it is unlikely we will go in that direction (I would actually be okay removing it like these other websites) and @xPaw gave you an alternative if you decide you want to apply this locally :)
Thanks!


Fix TextInput 'defaultValue' propTypes to 'string'

Because TextInput only render the defaultValue of string, when using other types of values, it will render empty('') without any Warnings.

This looks accurate to me. Just sign the CLA and we can accept it.

Finished.

What else do I need to do? Please give me some Instructions, Thanks!

It looks like there is some code at Facebook that actually does not use a string here, it uses some other weird type that somehow resolves to a string, and thus this PR borks flowchecking when we ran internal tests. I'm not quite sure what to do here. Is it clear what non-string types would actually work here?

According to the code in TextInput.js, Only string type work.

@facebook-github-bot shipit

Trying to merge again.

Trying again.


cp: implement --sparse option

The --sparse option to cp is not implemented yet. This is an option that controls whether an optimization is applied in storing the file on the filesystem, so if we just want to get things running, it probably suffices for us to just add this argument and ignore it.
GNU cp:
$ touch a && cp --sparse=always a b
# no output

uutills cp
$ touch a && ./target/release/cp --sparse=always a b
./target/release/cp: Option 'sparse' not yet implemented.

I think it is now done


main is ahead of dev - may I merge main->dev?

There are 4 commits in main (related to poetry maintenance) that are not in dev. May I merge these commits into dev to keep them in sync?

Figured it was harmless so I went ahead and did it.


File exists example

Closes #117

Thanks! Path::exists is already documented with an example here so I would prefer not to reproduce that in the cookbook. Ideally the cookbook would show common use cases for which an example does not fit well in the standard library's documentation. Would you be able to update this to show how to find a particular executable command in the PATH? Like Python's shutil.which. That's what I meant in #117.

Ah so that's what you meant. Yes, I can do that. Sorry for the confusion.

On second thought, this may not make a good cookbook example. It is way more complicated than I thought. Let's hold off until the libz blitz gets a chance to look at the which crate.

Should I close this PR then and write some notes on the issue?

Sorry for the confusion too. How about one of the other examples?


feat: support using add_node as a decorator

graph.add_node can be used as a decorator now.
Examples:
graph = Graph(...)

# All of the following are supported

@graph.add_node("search node")
def search():
    pass

# Uses search.__name__ as the name of the node

@graph.add_node()
def search():
    pass

@graph.add_node
def search():
    pass

The default behavior is still supported as well
def search():
    pass

graph.add_node(search)

graph.add_node("search tool", search)

Note: in #209, @nfcampos supported a PR that implements similar functionality to the one in this PR.

Closing since a duplicate of #940


[nrfconnect/pigweed-app] Added support for the USB transport.

Problem
Pigweed-app console currently supports using only UART interface, while nRF52840 dongle needs to use USB.
Summary of Changes

Added an overlay enabling USB, which is added to build in case of using nrf52840dongle_nrf52840 board.
Disabled logs for Pigweed-app to avoid interference with the command frames.

Fixes #3747

@kkasperczyk-no this is great!
Can we add a small note in pigweed's README, explaining how to build an image for nRF52840 dongle (west build -b nrf52840dongle_nrf52840)?

@LuDuda of course that I should have done it, I also added information about dongle flashing as it's not so obvious. Is it ok now?

@kkasperczyk-no this is great!
Can we add a small note in pigweed's README, explaining how to build an image for nRF52840 dongle (west build -b nrf52840dongle_nrf52840)?

@LuDuda of course that I should have done it, I also added information about dongle flashing as it's not so obvious. Is it ok now?

Perfect! :+1:


reconstruction

It seems that the project has not been maintained for a long time
I recently tried using the software and modified it extensively
I'm very interested in this project and hope to continue to maintain it
The changes are still in progress. If you don't have time to manage it, I hope you can add me as a collaborator or transfer the project
[Note] These changes are destructive changes I rewrote it

@rxtur

@farzindev

Added you as a collaborator to the project. Just please remember this adds you responsibility to maintain code, specially react to security issues that often sneak in with new code.


Bug Report: No Condition in Login

Reproduction steps
Steps -:
1 . Go to Login Page .
2. Click the Submit Button .
3. See the results .
Expected behavior
In login form , even nothing is filled there and we click the submit button . It redirects us to home page but actually it should show some thing like it shows in sign up page .
https://github.com/SauravMukherjee44/Aec-Library-Website/assets/85991449/5507ff15-772c-4d5e-902e-77bd38d65960
Actual Behavior
It directly redirects us to home page .
👀 Have you spent some time to check if this issue has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Can you assign this issue to me under GSSOC ' 23 .


What to return if implication is trivially satisfied?

Attached is a bug report: bug_report.tar.gz. Where I'm adding tests for this in pyk: https://github.com/runtimeverification/pyk/pull/184
I have a simple IMP definition, and I am feeding the following term into the Haskell backend simplify endpoint:
CT1 = <k> int $n ; $n = X ; </k> <state> .Map </state> #And X <Int 3 #And 3 <Int X
CT2 = <k> int $n ; $n = Y ; </k> <state> .Map </state>

The first RPC call in the bug report is simplify: CT1, which returns basically the same thing as CT1, but I expect it to return #Bottom. The second call in the bug report is implies: CT1 => CT2, which as expected returns #Top (because the antecedent is bottom), with empty substitution and empty predicate. Some differences I would expect:

The first call to simplify should return #Bottom, because the implication endpoint is able to detect that the antecedent is bottom.
The second call to implies should not return #Top for the predicate, but #Bottom. It should be that if implication endpoint returns condition { "substitution": SUBST, "predicate": PRED }, then I can construct SUBST(CT2) #And PRED and have that be equal to CT1. But right now, Subst(CT2) == CT2 (empty substitution), and PRED == #Top, so SUBST(CT2) #And PRED == CT2, and we do not have that CT1 == SUBST(CT2) #And PRED (because CT1 is bottom).

There is no way I can find for me to work around this, and it's blocking progress on pyk RPC prover. An immediate fix to the simplifies endpoint (so it returns #Bottom correctly) would fix this. So would a separate fix to the implies endpoint.

This does not appear to be fixed:
[dev@dev-ubuntu pyk]% kup list
┌───────────┬──────────────────────────────────────────┬──────────────┐
│ Package   │ Installed version                        │ Status       │
├───────────┼──────────────────────────────────────────┼──────────────┤
│ kup       │ 04f0c0033ada3aa001458bfa7ebe413d7d9f50b0 │ 🟢 installed │
│ kore-rpc  │ b74e9f8d5b88f4550145abf90d7fb3e69e072963 │ 🟢 installed │
│ k         │ 0465cd2d61bee8ce4bfb7be1bc5b8ed51e8fa271 │ 🟢 installed │
│ kavm      │                                          │ 🔵 available │
│ kevm      │                                          │ 🔵 available │
│ kplutus   │                                          │ 🔵 available │
│ kore-exec │                                          │ 🔵 available │
│ pyk       │                                          │ 🔵 available │
└───────────┴──────────────────────────────────────────┴──────────────┘

Attached is a bug report:
bug_report.tar.gz
Now, it's returning:

Implication is satifiable: true
Substitution is None
Predicate is None

It should really be returning:

Implication is satisfiable: true
Substitution is #Top
Predicate is #Bottom

Basically, I should not need to make this extra check here: https://github.com/runtimeverification/pyk/pull/184/files#diff-6c924e837929a3c2ac3f64cd281dbf78a290c9deb1fc2980b46864f34408be86R127
It's OK if I have to make that extra check, because current design of implication endpoint does not allow the above specification, but it's more expensive to make the extra call into the RPC server.

From meeting

Please see https://github.com/runtimeverification/haskell-backend/pull/3497/files for the updated specification, it should make it possible for users to distinguish between several cases.


issue with MULTIPART_UNMATCHED_BOUNDARY [id "200003"] v2.9.2

I get with upload a image this error:

[:error] ModSecurity: Access denied with code 44 (phase 2). Match of "eq 0" against "MULTIPART_UNMATCHED_BOUNDARY" required. [file "/etc/httpd/conf.d/mod_security.conf"] [line "34"] [id "200003"] [msg "Multipart parser detected a possible unmatched boundary."] [hostname "www.example.com"] [uri "/myupload"] [unique_id "W...w"], referer: https://www.example.com/myupload
[http:error] AH01579: Invalid response status 44, referer: https://www.example.com/myupload

like https://github.com/SpiderLabs/ModSecurity/issues/652
I upload simple with
<form action="myupload" method="post" accept-charset="utf-8" enctype="multipart/form-data"><input type="file" name="image"><button type="submit" name="submit">Upload</button></form>
one of many many many image-files with this error "--"

I use modsecurity2.9.2-1.el7 and its set as "off". So why its catch this issue?

SecPcreMatchLimit 1000
SecPcreMatchLimitRecursion 1000

SecRule TX:/^MSC_/ "!@streq 0" \
        "id:'200004',phase:2,t:none,deny,msg:'ModSecurity internal error flagged: %{MATCHED_VAR_NAME}'"

SecResponseBodyAccess Off
SecDebugLog /var/log/httpd/modsec_debug.log
SecDebugLogLevel 0
SecAuditEngine RelevantOnly
SecAuditLogRelevantStatus "^(?:5|4(?!04))"
SecAuditLogParts ABIJDEFHZ
SecAuditLogType Serial
SecAuditLog /var/log/httpd/modsec_audit.log
SecArgumentSeparator &
SecCookieFormat 0
SecTmpDir /var/lib/mod_security
SecDataDir /var/lib/mod_security

Related to #1747

@Daijobou this should not be an issue with libModSecurity (aka v3.0). https://github.com/SpiderLabs/ModSecurity/commit/7def498c4c043fd857689c7cc47a64d2bdf0badb Please consider upgrading.
I'm going to close this one. If you believe this is still an issue please let us know and we can reopen it. Thanks.

hi
I get with upload a file by 48M size this error:
ModSecurity: Access denied with code 403 (phase 2). Matched "Operator Eq' with parameter 0' against variable MULTIPART_UNMATCHED_BOUNDARY' (Value: 1' ) [file "/etc/nginx/modsec/modsecurity.conf"] [line "60"]
and by comment rule i can upload:
SecRule MULTIPART_UNMATCHED_BOUNDARY "!@eq 0"
"id:'200004',phase:2,t:none,log,deny,msg:'Multipart parser detected a possible unmatched boundary.'"

yes my version is 3.0
very very tanks
my problem is solved

Can someone tell me if this issue is related to this error? This is on fedora28 with mod_security-2.9.2-5.fc28.x86_64
[Fri Feb 08 22:06:50.144344 2019] [:error] [pid 11255:tid<PHONE_NUMBER>02464] [client <IP_ADDRESS>:54982] [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 2). Match of "eq 0" against "MULTIPART_UNMATCHED_BOUNDARY" required. [file "/etc/httpd/conf.d/mod_security.conf"] [line "35"] [id "200003"] [msg "Multipart parser detected a possible unmatched boundary."] [hostname "linuxsecurity.com"] [uri "/index.php"] [unique_id "XF5Dyf3kxTYC2M5TGQgxsAAAANU"], referer: https://linuxsecurity.com/index.php?option=com_content&task=new&sectionid=9&itemid=0


Test show_in_file_manager cross platform

Currently only checked in Windows

It's not clear at all how this could be tested, and it will also be a pain. The package itself doesn't seem to have any tests. This is only a quality-of-life feature and is non-critical, so will leave untested and let user report in case of problems.


Feature/market ui

New visual components:

Arena
Home
TopBar
Footer
TopRank

Canceled the PR as we detected some issues with the changes.

What issue? I would like to learn from it 😊

The responsive design is broken. Sorry that I don't know the details as I didn't code those changes.


NON mercy corps gmail accounts cannot login, faced with an error upon execution

I created a partner user with a gmail account, and can login with username and password. If I try to login via GMAIL (non mercycorps gmail account), I am shown an error page.
Additionally, if I have a mercy crops gmail account, i CANNOT use the gmail option to login, and MUST use the "login with mercycorps.org email address" option
Heres what I am greeted with attempting login with the following user :
<EMAIL_ADDRESS>

QA - PASSED

Tried this again with<EMAIL_ADDRESS>and was able to login successfully through the gmail option.


NOWTV: Latest version of Plex Client?

I bought a NowTV as its a cheap rebranded roku to sideload plex, I installed this version and its ancient version! Where can I find the latest updated Plex Client to sideload? Please don't tell me that this is the only version...

There's some information on the two versions on the support site. The only way to sideload is to have the source code, and only Plex Classic is open source. The new version of the client cannot be sideloaded.


Jlee/add tail/#229

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #229
Summary:
Added Icelandair tail.
Please summarize the scope of the changes you have submitted, what the intent of the work is and anything that describes the before/after state of the project.
Type of change:

[x] New capability
[ ] Revision of an existing capability
[ ] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

Updates to http://alaska.iconstails.surge.sh/ deployed.

:tada: This PR is included in version 4.33.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Highlight regex comments

It would be nice to be able to highlight regex comments explicitly with this, since I'm using this lib to highlight a regex that I split into parts, and indent and comment to explain. Something like the # character perhaps.
Thanks for the awesome library! I might even just do it myself and send a PR, we'll see :)

PRs welcome. It would need to be some kind of optional mode since the JavaScript regex flavor doesn't support comments.


Add new client_rekey resource

Based on https://github.com/chef-boneyard/client-rekey only with none of the legacy, written as a custom resource.

@lamont-granquist what's left here before we can ship this?

@lamont-granquist anything else that needed to be done to this one?

yeah still needed decent manual testing i think which i ran into snags trying to do

(or decent non-manual testing but that would require a chef-zero that could do auth or spinning up a chef-server for testing)

Closing this one out for now since we don't have a way to test this and we shouldn't pull it in without that.


WebUI/Talk: failed to render: template: views/talk:79:29

LocalAI version:
quay.io/go-skynet/local-ai:v2.18.0-cublas-cuda12-ffmpeg

Environment, CPU architecture, OS, and Version:

Kubernetes 1.29
Describe the bug
I randomly klicked "Talk" on the webui and it gives me this error:
{"error":{"code":500,"message":"failed to render: template: views/talk:79:29: executing \"views/talk\" at \u003c.Name\u003e: can't evaluate field Name in type schema.OpenAIModel","type":""}}

To Reproduce
Install 2.18 i guess
Expected behavior

Logs

Additional context
Pretty sure it was working in 2.17

yup confirm this - should be fixed by https://github.com/mudler/LocalAI/pull/2685

Closing as fixed in v2.18.1


Won't work for sub functions

Now the sub functions such as assert.doesNotThrow won't be removed. Probably this is a bug on the upstream.

@twada Is this working on your projects?

I found this is caused by espurify.

@falsandtru Oh thank you for reporting. I'm going to investigate this issue.

Thanks.

@falsandtru I cannot reproduce the case since assert.doesNotThrow still removed properly. Would you make a small reproduction case?
https://github.com/unassert-js/unassert/pull/19

Did you test after clean install?

yes
$ mkdir pd-unassert
$ cd pd-unassert
$ npm init -y
Wrote to /Users/takuto/work/pd-unassert/package.json:

{
  "name": "pd-unassert",
  "version": "1.0.0",
  "description": "",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC"
}

$ npm install --save-dev unassert-cli
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN<EMAIL_ADDRESS>No description
npm WARN<EMAIL_ADDRESS>No repository field.

+<EMAIL_ADDRESS>added 43 packages from 130 contributors and audited 43 packages in 3.71s

9 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities

$ cat <<EOT >> prod.js
heredoc> const assert = require('assert');
heredoc> function fail() {
heredoc>   throw new Error('fail');
heredoc> }
heredoc> assert.doesNotThrow(function () {
heredoc>   fail();
heredoc> });
heredoc> EOT
$ cat prod.js
const assert = require('assert');
function fail() {
  throw new Error('fail');
}
assert.doesNotThrow(function () {
  fail();
});
$ npx unassert prod.js
function fail() {
    throw new Error('fail');
}
$

Indeed. I couldn't make a simple repro. FYI, the leaked assertions are this: https://github.com/falsandtru/securemark/commit/fcaa749a97d203c64f75eb661ea8d1411303c5c7. Since they are few (almost all assertions are removed), this bug is stateful. Can you release the updated version at first?

The current repro:

Clone https://github.com/falsandtru/securemark
Checkout 541badbd48d789c8c95f0ebf41eae5723b0b4730
Run npm i
Run gulp dist
See dist/securemark.js

@falsandtru Thank you for your repro case! I'm going to find the root cause and fix it.

Since the current espurify is broken, can you release v2.0.1 as the latest?

No, no, espurify is not broken but unssert do. I'll cut some bugfix releases ASAP.

OK.

Since the current espurify is broken, can you release v2.0.1 as the latest?

First I've tagged<EMAIL_ADDRESS>as latest.

That's what I intended. Thanks.

FYI: Released espurify 2.1.1 as bugfix


Generalized Text Search Solution

Users want to use Griptape to perform web searches with various search backends (https://github.com/griptape-ai/griptape/pull/296, and https://github.com/griptape-ai/griptape/pull/289). Similar to how we search vectors, I propose adding a generalized solution for non-vector search.

Tools

TextQueryClient (Replaces WebSearch)

Engines

TextQueryEngine

Drivers

GoogleSearchDriver
BingSearchDriver
DuckDuckGoSearchDriver
ArxivSearchDriver

Tasks

TextQueryTask (already exists, would use new TextQueryEngine)

Can we include image search as part of this offering? For drivers, please also add Unsplash.

Any plans to implement this soon?


adds flag to support skipping processing of street segments...

...and inserting after the output XML is generated.
https://www.pivotaltracker.com/story/show/156324653
There is still some work to be done here, but this is ready for a preliminary review.
A quick summary of how this is supposed to work:

prep the 5.1 feed if it is in XML format by converting it to CSV using the vip-feed-format-converter
using the upload script, add the :post-process-street-segments? flag set to true to the SQS message args (doc here).

That's it. What this will do is bypass loading of the street_segments.txt CSV file into the database, and at the end after an XML output file has been produced, will insert the street segments one-by-one, doing a very basic validation on each one (checks precinct id against what we've stored, and ensures the required fields exist for that street segment entry).
Testing has shown this speeds up the OH feed, for example, to about ~24 minutes vs. the ~12 hours it was taking.
TODO: more docstrings

@ddellacosta Is this PR ready to review, or is there more coming?

@sduckett
I may add more docstrings, but it's been ready for a while--I was hoping to get a preliminary review in any case, as I stated in my initial comments.


Updating Javascript article to Spin 2.0

@karthik2804 Working on it, and closed by accident. Give me a few minutes :-)


Some sensor entities are broken for chunmi.cooker.eh1

Any sensors in SENSOR_TYPES with stage as the _child property do not work, as the condition in line 96 of sensor.py seems to ignore updating these sensors.
Also some of these sensors are incorrectly mapped to properties in CookerStatus, e.g. rice_id should be rice, stage_name should be stage

I can confirm this issue


Update array compatibility tests

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (ba63035) 100.00% compared to head (f067b4a) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #625   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           30        30
  Lines         2568      2572    +4
  Branches       330       334    +4
=========================================
+ Hits          2568      2572    +4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Invalid regex with multiple repetition flags is accepted

What version of regex are you using?
Latest
Describe the bug at a high level.
The following regexes are accepted while they shouldn't:
[0-9]++
[0-9]+++
...

Looks like the extra repetition flags have no effect after all.
What are the steps to reproduce the behavior?
Link to the playground
What is the expected behavior?
Invalid regular expression: /[0-9]++/: Nothing to repeat.

The following regexes are accepted while they shouldn't

On what basis are you claiming that they "shouldn't" be valid?
Anyway, this is probably duplicate of https://github.com/rust-lang/regex/issues/765.

These patterns are invalid in other regex engines - does this qualify for a good enough reason? :)
I understand that each regex engine may have slightly different rules as there's no unique standard. Maybe it should be mentioned in the documentation that extra flags are ignored?
Anyway, thanks for your tremendous work!

These patterns are invalid in other regex engines - does this qualify for a good enough reason? :)

No. Think about what that would mean if this were actually applied.

Maybe it should be mentioned in the documentation that extra flags are ignored?

I don't think so. At least, not in the existing syntax docs. Those was brought up before in the linked issue (or another one), but this is a pathological case and there is nothing in the docs that suggests this pattern would be illegal. The only reason people seem to think it's weird is because other regex engineers reject it. But I see no reason to reject it. Again, I wrote out a full explanation in the linked issue. And suggested this is something that belongs in "differences with other regex engines" doc. There's an issue for that too.


recurring 403 errors while provisioning the conflict-practices repositories

Problem:
The generation of the conflict-practices repositories cannot be handled unattended. It requires a lot of reruns on bigger classes and takes full concentration that you cannot give your class while resolving this. The bigger the class the bigger the problem
Observed behavior:
The generation of the conflict-practices repositories (option 4 in the scrip) is giving recurring 403 errors. Every 4th repository it is trying to make results into HTTP 403 Forbidden warning. Every consecutive repos gets the same.
Workaround:
This requires you to rerun the script, skipping every repository you already created. You will need to do this roughly for the #contributors / 4.
Expected behavior:
Script generates conflict-practices repositories unattended while I can focus on teaching the class
I have provided a the full log and console log
console log.txt
log.txt

This part immediately looks strange to me:
Username for 'https://github.com': ericksegaar
Password for<EMAIL_ADDRESS>
Do you have your class tokens properly set up?  I never get asked for a username or password.

Ther are two ways to authenticate with the scripts, first is the .trainingmanualrc which contains the token for the GH commands. There is another authentication required for the git commands, that is what you see here.
I believer ther is a separate issue for that.
The only thing this part is doong is asking for authentication for git. As iam using wsl and normally dont use wsl for day to day work I run into all kind of issues. Most of them are already known in other issues (OSTYPE for the sed command, git credential manager so i use a pat token, the missing validation vor correct httpie version that support —quiet)
this is just a line asking me for a git token

I've been running on Mac for years with no issues like you're seeing.  Max class size around 30 or so but typically around 20.  I wonder if there's some weird quirk specific to WSL.

My guess is you use your mac for day 2 day development work too and have it set up correctly in that manner. I only use WSL to run the scripts. Normally pscore is my script of choice on windows. If the credential manager is set up it will take care of the git authentication, that's why you are not asked to put in username:token. Also the script has some more if statement like if [[ "$OSTYPE" = "msys" ]] then that should be if [[ "$OSTYPE" = "msys" || "$OSTYPE" = "linux-gnu" ]]; then to work in the create-files. Just as an example stated that there are some alternative code flows

When following the flow just before the first 403 I track it down to a function in the shared_functions:300
  if http --check-status --ignore-stdin --quiet --auth \     "$TOKEN_OWNER:$TEACHER_PAT" "$org_repos_endpoint/$repo/pulls" \     title="$title" \     head="$head" \     base="$base" \     body="$body"; then     echo "Done."   fi
This is using the token from the .trainersmanualrc and is not related to the Git authentication that was discussed above

I have the same issue on mac and also have to rerun the script several times. Also the cleanup scripts are not working.


Link to correct editor config

Microsoft's version has been deprecated in favor of the community version.

Good catch @Tyriar !


what is the META parameter used for in SETHOOK?

A few questions:

When I submit a command like this:

SETHOOK testhook http://httpbin.org/post META field val1 NEARBY fleet FENCE POINT 33.637276 -84.434006 500
it happily accepts it, but I'm not sure what META actually does, and can't find any description of it in your docs. The webhooks documentation page suggests that META may accept multiple name/value pairs, but if I try this:
SETHOOK testhook http://httpbin.org/post META field val1 field2 val2 NEARBY fleet FENCE POINT 33.637276 -84.434006 500
I get an error "invalid argument 'field2'"

I'm assuming that SETHOOK supports all of POINT, GET, BOUNDS, OBJECT, TILE, QUADKEY, HASH, is that correct?  Which of these can a radius be specified with... Just POINT or all others as well?
Just want to make sure my node driver can support all the options....
thanks

The META are just any key/value pairs you would like to be returned in the callback as additional data. The reason why you second example fails is you must use the META keyword in front of each pair, like so: META field val1 META field2 val2
2.
Only POINT and ROAM have the radius option, see the documentation here:
http://tile38.com/commands/nearby/

thanks for the clarification


Resize glitch using Autoresizer after upgrading to 8.8.0

Hello, first of all thanks for this great library!
I'm here to report a resize glitch using Autoresizer after updating to the latest version (8.8.0).
I've created a plunker to show the glitch: https://plnkr.co/edit/4ykww2k5yFWkbpUm0Aje
To reproduce, run the plunker in a separate window (which should not be maximized), enlarge it a bit, then scroll down the table for some rows and then scroll it to the top: you should see that the rows which enter the viewport have the correct size, while the old ones keep their size pre-resize.
If you change the plunker's index.html to use<EMAIL_ADDRESS>you could see that the problem wasn't there, the rows update their size as the window is enlarged, so no glitch there.

Hi @ingro
I'm having the same issue with Grid component (Table uses it underneath). AFAIK the problem is related with the recent addition of styleCache #506, so when AutoSizer is involved cached dimensions are not cleared. They're cleared only when scrolling, so if you try to scroll the table after resizing you'll see that eventually all cells get the right dimensions.
There's another option to force styleCache clearing which is using recomputeGridSize method of Grid component (this is what I'm currently using as a workaround). For Table component you may use recomputeRowHeights which proxies to Grid one. You should call this method whenever resize occurs, for that you may use onResize callback of AutoSizer. Let me know if that works for you :wink:
Btw, @bvaughn what do you think about providing a method for manually clearing styleCache? Does it make sense?

Whoa thanks for the insights @edulan, I will try your workaround tomorrow!
On 14 Dec 2016 16:44, "Eduardo Lanchares"<EMAIL_ADDRESS>wrote:

Hi @ingro https://github.com/ingro
I'm having the same issue with Grid component (Table uses it underneath).
AFAIK the problem is related with the recent addition of styleCache #506
https://github.com/bvaughn/react-virtualized/pull/506, so when AutoSizer
is involved cached dimensions are not cleared. They're cleared only when
scrolling, so if you try to scroll the table after resizing you'll see that
eventually all cells get the right dimensions.
There's another option to force styleCache clearing which is using
recomputeGridSize method of Grid component (this is what I'm currently
using as a workaround). For Table component you may use
recomputeRowHeights which proxies to Grid one. You should call this
method whenever resize occurs, for that you may use onResize callback of
AutoSizer. Let me know if that works for you 😉
Btw, @bvaughn https://github.com/bvaughn what do you think about
providing a method for manually clearing styleCache? Does it make sense?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bvaughn/react-virtualized/issues/509#issuecomment-267068115,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AA1rR8uVCPIYMpuICd0MI7dT9kWAbF8Zks5rIA73gaJpZM4LMyyi
.

Sorry for the regression @ingro. And thanks for chiming in @edulan!
Ideally we should clear the cache any time columnWidth or rowHeight changes, although that's a little tricky due to the fact that those props can be functions and users may inline them (so we'd get false positives).
A method to manually clear the cache would also work but I'd really prefer for users not to have to think about the cache at all.
Maybe List and Table should trigger this reset any time their widths change, since a vanilla Grid's cells wouldn't (in theory) be impacted by width.
Unfortunately I can't do anything about this for the next several hours because I'm at work. If someone else would like to take a stab at it, that'd be great. Otherwise I'll get to it when I can.

Maybe a better solution would be to use a key comprised of the style information (as was initially proposed in PR #483). I wasn't a fan of this because it would continue to grow but...perhaps we could use an LRU cache to address that aspect. I'm not sure if it would be as performant as the current implementation, but it would simplify edge cases like this.

Fixed in version 8.8.1
Compare the previous version:
https://rawgit.com/bvaughn/react-virtualized/master/playground/render-counters.html?source=8.8.0
To the new version:
https://rawgit.com/bvaughn/react-virtualized/master/playground/render-counters.html?source=8.8.1
Resizing the window will increment the render counters in the new version. Scrolling slowly should not increment them (in either version).
Forking your Plnkr to use 8.8.1 shows the correct behavior as well:
https://plnkr.co/edit/VAJ83L0j8XTBsV4jeydi?p=preview
Thank you for the quick bug report.

Thanks for the fix @bvaughn :+1:

Yep I can confirm that it's working now, thanks for the fast fix @bvaughn !

Great! Thanks for confirming
On Dec 15, 2016 12:44 AM, "Emanuele Ingrosso"<EMAIL_ADDRESS>wrote:

Yep I can confirm that it's working now, thanks for the fast fix @bvaughn
https://github.com/bvaughn !
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/bvaughn/react-virtualized/issues/509#issuecomment-267270355,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABznRzfckg_oDsRm2yqZcxbY3_gqaJrks5rIP3QgaJpZM4LMyyi
.


Adding kubernetes support

Added kubernetes support.

Thats all

+1

up

apiVersion: apps/v1
kind: Deployment
metadata:
name:
labels:
app:
spec:
replicas: 256
selector:
matchLabels:
app:
template:
metadata:
labels:
app:
spec:
containers:
- name:
image:
ports:
- containerPort: 80


POCO F1 WIFI and Cellular Network Bug

After Installing Windows 11 on Poco f1 WIFI and Cellular Network is not showing on Windows boot how to fix this issue

@ClouDROID-Dev Both work fine on Windows 10. In Windows 11 afaik, WiFi works fine after Windows setup is done but Cellular Network doesn't.


Update documentation on using Azure blob store as UFS

Minor tuning on docs on Azure blob store

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2335/
Test PASSed.


"Link Advance Letter" action not working

The action "Link Advance Letter" seems to always results in

That is because in https://github.com/microsoft/ALAppExtensions/blob/6228f5f16ca84173df68f969410263095feffeca/Apps/CZ/AdvancePaymentsLocalization/app/Src/Codeunits/SalesAdvLetterManagement.Codeunit.al#L234 the return value of the inner procedure is not returned by the outer procedure, so in https://github.com/microsoft/ALAppExtensions/blob/6228f5f16ca84173df68f969410263095feffeca/Apps/CZ/AdvancePaymentsLocalization/app/Src/Codeunits/SalesAdvLetterManagement.Codeunit.al#L213 the InsertedEntryNo is always 0.

Hi! Please take a minute to read the guidelines for this repository https://github.com/microsoft/AL and our collection of frequently asked questions https://github.com/Microsoft/AL/wiki/frequently-Asked-Questions .
This repository is only for extensibility requests for Dynamics 365 Business Central. We suggest that you open a support case or file a bug to ensure that all Business Central users benefit from your catch as soon as possible:
•	On premises - https://support.microsoft.com/en-us/supportforbusiness/productselection?sapId=93d37907-ad94-d591-22e9-593cfa09dd3f
•	On line – contact your partner, or if you are a partner open a support incident through Partner Center - https://partner.microsoft.com/en-us/pcv/dashboard/overview


Could not load unit test config from launch.json

Issue Type: Bug
I've been having issues with unit testing since updating to the latest vscode. I've got it mostly running but I'm still having one issue. I've managed to get test discovery working and I can run my tests from the test explorer or by using F1 Python:Run Tests.
But the Run Test | Debug Test code annotations still don't work (they did before I upgraded).
I get "Could not load unit test config from launch.json"
Not sure if I missed something as I never had to create a launch config for unit tests before, it just used to work once settings.json was configured correctly
Extension version: 2019.4.11987
VS Code version: Code 1.33.0 (0dd516dd412d42323fc3464531b1c715d51c4c1a, 2019-04-04T15:08:57.775Z)
OS version: Linux x64 4.15.0-47-generic

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 x 4399)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwaresurface_synchronization: enabled_onvideo_decode: unavailable_offwebgl: enabledwebgl2: enabled

Load (avg)
2, 1, 1

Memory (System)
31.33GB (2.72GB free)

Process Argv
--unity-launch

Screen Reader
no

VM
0%

Please provide the following details,

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

Output from Console under the Developer Tools panel (toggle Developer Tools on under Help; turn on source maps to make any tracebacks be useful by running Enable source map support for extension debugging)

Closing this until further info is provided. Feel free to reopen with more info.


Add NODE_MEM env variable to control memory usage

Allow user to configure v8's max_old_space_size parameter using NODE_MEM environment variable

Thanks, LGTM!
(Sorry for the very late response. I wasn't able to keep up with my GH projects as of late.)


Chunk encoding support

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue, please leave a comment

Describe the Feature
Support chunk encoding

There is a SEP in progress that will need to be interpreted and scoped accordingly.  We currently do not have any additional context for this feature.
SEP in progress: /reviews/CR-7526002/revisions/8#/diff

Need to review priority as this is marked as "must" for GA in feature matrix

Priority 3 seems fine as discussed with Rust.

SEP : dynamic-payload-trait.md
Updated priority as this needs to be implemented fully to support flexible checksums for streaming scenarios.

Will review the related SEPs during Friday review meeting. After reviewing the SEPs we will fill out this issue with relevant details.
SEP : dynamic-payload-trait.md (Not Accepted)
SEP: seps/accepted/shared/requires-length-trait.md (Accepted)


WIP: Continue running ppc64le and aarch64 on Bionic

Setting these to Focal has the neat effect of forcing the builds to run on x86 instead.

Nevermind, this was a Travis bug.


Added VPC Tenancy

Added VPC Tenancy to the VPC Stack

Hi @Seblat5ch
Thanks for your contribution! Can you please confirm that your contribution is under the Apache 2.0 license terms?
Thanks,
Santiago

Yup my contribution is under the apache 2.0 license terms.


Review and merge PR's >= 1219

This issue is imported from pivotal - Originaly created at Feb 20, 2023 by Thijs Kinkhorst

@thijskh I finished review of your PR\'s. I did leave some nitpicks on some of the approved PR\'s. And requested changes on: `https://github.com/OpenConext/OpenConext-engineblock/pull/1220` (Michiel Kodde - Mar 2, 2023)

I have updated all PRs now, so another round is welcome. (Thijs Kinkhorst - Mar 3, 2023)


Master vm doc - data preparation

Description

Add VM data preparation doc

Linked issue(s)/Pull request(s)

issue_number

Type of Change

[ ] Non-breaking bug fix
[ ] Breaking bug fix
[ ] New feature
[ ] Test
[x] Doc update
[ ] Docker update

Related Component

[ ] Simulation toolkit
[ ] RL toolkit
[ ] Distributed toolkit

Has Been Tested

OS:

[ ] Windows
[ ] Mac OS
[ ] Linux

Python version:

[ ] 3.6
[ ] 3.7

Key information snapshot(s):

Needs Follow Up Actions

[ ] New release package
[ ] New docker image

Checklist

[ ] Add/update the related comments
[ ] Add/update the related tests
[ ] Add/update the related documentations
[ ] Update the dependent downstream modules usage

Codecov Report

Merging #285 (380173b) into master (d8c511d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #285   +/-   ##
=======================================
  Coverage   64.37%   64.37%
=======================================
  Files         113      113
  Lines        5553     5553
=======================================
  Hits         3575     3575
  Misses       1978     1978

Flag
Coverage Δ

unittests
64.37% <ø> (ø)

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

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 d8c511d...380173b. Read the comment docs.


docs: config.md updatation for new flag

Description
PR contains the FLAG "USE_IMAGE_TAG_FROM_GIT_PROVIDER_FOR_TAG_BASED_BUILD" description in config.md

Merged after discussion with Rupin on Discord


Add AppsandFeaturesEntries Elgato.CameraHub.installer.yaml

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow
Resolves #125262

@stephengillie Waiting for you.

@wingetbot waivers Add Validation-Executable-Error

Verifying:


failed to cherry pick PR 2919 from cyclinder, to branch release-v0.7

commits fe936b58b0b429add7133513312d72e20ac2483b of cyclinder conflict when merging to branch release-v0.7, please manually cherry pick it by yourself.
PR https://github.com/spidernet-io/spiderpool/pull/2919 ,  action https://github.com/spidernet-io/spiderpool/actions/runs/7219445069
Auto-merging pkg/networking/networking/route.go
CONFLICT (content): Merge conflict in pkg/networking/networking/route.go
error: could not apply fe936b58... Merge pull request #2919 from cyclinder/coordinator/move_ipv6_route
hint: After resolving the conflicts, mark them with
hint: "git add/rm <pathspec>", then run
hint: "git cherry-pick --continue".
hint: You can instead skip this commit with "git cherry-pick --skip".
hint: To abort and get back to the state before "git cherry-pick",
hint: run "git cherry-pick --abort".

/cc @cyclinder

There are huge changes from v0.7 to the main, It's hard to cp this, so I'll close it.


Update azure-stack-register.md

Clarify instructions for registering the Microsoft.AzureStack resource provider prior to running the script to register with Azure.

@BradleyBartlett,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

#sign-off

@BradleyBartlett - This request cannot be merged due to a conflict between the branch and the repository. Please resolve the merge conflict to enable the merge.  Thanks

@GitHubber17  Merge conflicts resolved. Thank you!


Spacing around References text needs to be improved

occurs in https://www.hydroshare.org/resource/1a116e5460e24177999c7bd6f8292421/

@Maurier - the text of the references has changed, but the spacing is still a problem:

These just need some additional white space surrounding them. I'm going to change the title of this issue to reflect that it's now a spacing issue.

@horsburgh perhaps this was resolved some time in the last 2 years. Does this look okay to you now? thx
https://www.hydroshare.org/resource/1a116e5460e24177999c7bd6f8292421/

@devincowan This was fixed as part of #3261 and deployed in the latest release 1.52. I think we can close it.


Timeout running Cypress test

Where to find the issue
https://github.com/corona-warn-app/cwa-website
Describe the issue
Executing npm test will sometimes time out.
Error: Timed out waiting for: http://localhost:8000
at ...\cwa-website\node_modules\wait-on\lib\wait-on.js:132:31````

According to https://github.com/bahmutov/start-server-and-test#readme
"Timeout
This utility will wait for maximum of 5 minutes while checking for the server to respond (default). Setting an environment variable WAIT_ON_TIMEOUT=600000 (milliseconds) sets the timeout for example to 10 minutes."
Steps to reproduce
In terminal of clone of cwa-website

Execute npm test
Note that sometimes the following error message appears:

Error: Timed out waiting for: http://localhost:8000
at ...\cwa-website\node_modules\wait-on\lib\wait-on.js:132:31

This seems to happen more often on the first run of npm test and on the second attempt it succeeds. This is sure to be dependent of the performance abilities of the host system (CPU, memory, etc.).
Current solution
Currently the script npm test
invokes npm start which causes:
// Build the site, run the server, and watch for file changes
gulp.task('default', gulp.series('build', server, watch));

to run. The default timeout starts at the beginning of the build session, not at the beginning of the server start function call in gulp. As cwa-website has grown in size and complexity, the time to build the web has increased, so that the likelihood of timing out has now also increased.
Workarounds
There are two immediate workarounds:

increasing the timeout through an environment variable WAIT_ON_TIMEOUT
separating build and Cypress start in two different terminal windows

See below for further details:
Increase timeout through parameter
Create or edit .bash_profile in the user's home directory to increase the timeout from the default 5 minutes to 10 minutes.
Add
export WAIT_ON_TIMEOUT
WAIT_ON_TIMEOUT=600000

This sets an environment variable which will be used by start-server-and-test and its use will show up in the log.
Split build and test start
This is equivalent to npm test.
Execute:
npm start
in a terminal window and wait for a browser window with http://localhost:8000/en/ to open.
In a separate terminal window execute:
npx cypress run -b chrome
Suggested change
Restructure the scripts so that the default timeout for start-server-and-test starts running after the build has completed.
For instance:

add a new task in gulp.js which only runs server and watch, not build
modify the scripts in package.json so that the test scripts run the build task before running start-server-and-test and this in turn only starts the server without building the server contents

I tried this out, however I don't really have the experience in npm and gulp to be sure to implement the suggested change cleanly, so I'd be happy for somebody else with the right skills to implement it (assuming that the suggestion is accepted).
I already used the workaround successfully in my own environment. That is a quick (temporary) solution.

There is another workaround to the timeout, which I will add to the main issue:
This is equivalent to npm test.
Execute:
npm start
in a terminal window and wait for a browser window with http://localhost:8000 to open
In a separate terminal window execute:
npx cypress run -b chrome

I changed my mind and I plan to submit a PR for this myself soon. Stand by!

I have submitted https://github.com/corona-warn-app/cwa-website/pull/1997 now which separates out the build process from the web server start and Cypress test. This avoids a timeout because the clock doesn't start counting down until the build process has completed.
I have tested it on Windows and I will test it also on Ubuntu next.
I would like to wait for PR https://github.com/corona-warn-app/cwa-website/pull/1996 from @brifemu to be merged first, so that there is a clean base of Cypress tests which all work before changing anything in the higher level build / test scripts.

PR #1997 is now tested and ready for review.

Unfortunately PR #1997 did not work on all Windows systems, although it was fine on Ubuntu, Mac and Windows 10 Home.
I am working on a replacement PR which is (hopefully!) platform independent.

PR #1997 did not work on all Windows environment because it needed the npm key shell-script to point to the bash shell executable.
The new PR #2067 is less stringent, however to successfully run the complete Cypress suite of tests defined in https://github.com/corona-warn-app/cwa-website/tree/master/cypress/integration it is still necessary to follow the instructions in https://github.com/corona-warn-app/cwa-website#cypress-under-microsoft-windows concerning setting the npm key shell-script, i.e. execute npm config set script-shell "C:\\Program Files\\git\\bin\\bash.exe".
This is because the https://github.com/corona-warn-app/cwa-website/blob/master/cypress/integration/blog_spec.js script relies on executing npm run test:prepare first which will only run correctly in a bash shell. This is not a change from previously.

PR #2067 is now merged, which resolves this issue.
Note that anybody testing locally will need to run npm ci or npm install to update their Node package installation.

@MikeMcC399 Thanks for the PR and all the feedback!


1.17 ore gen

mc 1.17 (java)
fabric-api-0.35.1+1.17.jar
indrev-1.10.0-alpha.1.jar
non of the ore's are generated
not in existing word ( new chunks)
not in new test world
regards

found the problem 👍
everthing is ok if you
DONT't USE the "CavesAndCliffsPreview.zip"
that means worlds high only 0+ not 0 to -64 or +512
NOT USABLE in EXISTING 1.17 snapshot worlds


Update tanks.js

Added critical bug fixes for the sprig console for tanks (issues did not exist on emulator).
Author: Om Raheja
Already filled out the checklist: https://github.com/hackclub/sprig/pull/1874
This is just a bug fix update because the game didn't actually work on the sprig, courtesy of @grymmy
Thanks!

Cool! Looks Good to Me


Style/MethodCallWithoutArgsParentheses option for methods with args

Is your feature request related to a problem? Please describe.
As an alternative to Style/MethodCallWithArgsParentheses where there are methods where we do not want parenthesis around method calls that take args, it would be nice to enforce consistency for the negative case as well.
Describe the solution you'd like
I'd like to have something like an IncludedMethods option where we can specify methods that should never have parens:
Style/MethodCallWithoutArgsParentheses:
  IncludedMethods:
    - exit
    - puts
    - require
    - warn

Describe alternatives you've considered
This might also make sense as some sort of a NeverParens option under Style/MethodCallWithArgsParentheses.

Duplicate of #6967.

@tejasbubane I saw that issue before, but it didn't look like the same thing as what I'm asking for here. It looks like they're asking for more sophisticated ways to ignore methods, but I'm looking for a more strict "inverse" option.

This issue is still relevant.


easier way to get number of rows in DELETE

If I issue a DELETE it would be nice to know whether 0, 1, or more rows were deleted, in an easy way.
I tried doing this, FYI
DELETE FROM queued_jobs
WHERE id = $1
RETURNING count(id) as rows_deleted;

And got this at runtime (not compile time)
pq: aggregate functions are not allowed in RETURNING

Well this is a issue outside of sqlc, but that can be addressed trough code generation.
The Exec() method of the sql.DB type, from the database/sql package, returns two values: an sql.Result interface and an error.
The sql.Result interface has two methods:  LastInsertId(), that is self-explanatory, and RowsAffected(), that returns the amount of rows that were inserted, updated, or deleted, and this is what you want.
My proposed solution is to have all generated methods that were marked with an exec tag in the generating sql script to also return a sql.Result in addition to the error.
If you can't wait for a change in the library like this, you can go use this Stack Overflow answer to solve your problem.

Reading better the code, I've noticed that there is a execrows tag. After testing a little, this does provides the functionality you want.

Ah, forgot about one. Maybe the issue should be better documentation of what the meta fields do.


sklearn.utils._param_validation.InvalidParameterError: The 'eps' parameter of DBSCAN must be a float in the range (0.0, inf). Got nan instead.

Sorry to bother you, I have a bug when reproducing your code, can you help take a look

 Sorry to bother you, I have a bug when reproducing your code, can you help take a look

Hello, have you solved this problem? I also encountered this problem


[ja] Update command addition and removal static pods

en PR https://github.com/kubernetes/website/pull/34403/files
/assign @atoato88
/assign @nasa9084

/approve
thank you always~

Sorry for my delayed respose, it's LGTM.


zh  video and article content do not match

Issue in ./help/cloud-service/underlying-technology/introduction-jcr.md
In this Article ，en version is right content，when i turn to Chinese ver. Its become OSGi video.  XD
plz fix it.

Thank you. We are looking into this issue.

Thank you for your feedback. This is being reviewed and tracked in .


Using date picker logs user out if "exitScript" is true on IE

For v4.0.32, when using the date picker coupled with the wet.builder.refFooter exitScript set to true, the exitURL is hit when selecting attempting to select a date in Internet Explorer 11.
The issue also occurs for v4.0.31 but not previous versions.
This issue does not occur for Chrome, Edge or Firefox.

Thx,
We have fixed it
You could test here
https://ssl-templates.services.gc.ca/app/cls/WET/gcweb/v4_0_32c/cdts/samples_test/zzz_exitscript-datepicker-en.shtml
It will be include in the next release

@nicholas-ly Could you confirm this issue has been fixed in version 4.0.39 ? Thanks.

@patricehernert In 4.0.39, the date picker no longer shows up in Internet Explorer 11. The date picker is showing up correctly in Chrome, Edge and Firefox.

IE is no longer supported. Closing this issue.


Matching Error Injection Client

What changed?
Add an error injection client for persistence layer

Why?
Injection random client error during in bench test to expose potential error handling bugs.

How did you test it?
Tested locally using canary with 0.001 error rate

Potential risks
No risk. Error injection client won't be created if error rate is 0 on service start up.

Coverage decreased (-1.0%) to 58.747% when pulling d35dd0dc60d996394e4b2fcdf6284017b490fa33 on yycptt:matching-err-inject into 436bb56214a6726948371ff08541a5ee605ab9ab on uber:master.


Doesn't work for play routes downloads

Trying to use the play_2_x_routes generator results in an error when decoding the response from apibuilder.

I think the issue is that for the routes file there is no dir property in the files objects that are returned.


Merge pull request #1 from TixiaoShan/master

pull from TixiaoShan

I'm really sorry...It's a misoperation...


Update install script instructions

Follow up to #1558
Trying this out myself, I noticed that it wasn't being run interactively. To make that work, you need to redirect the source directly into a sh process. Piped execution doesn't support interactivity.
$ curl -fsSL https://cog.run/install.sh | sh
On OS X, it is recommended to install cog using Homebrew instead:
`brew install cog`
Do you want to continue with this installation anyway?

This PR updates to use process substitution syntax. As discussed in https://github.com/fish-shell/fish-shell/issues/5181, fish (my preferred shell) uses a different syntax, so I added special instructions for that. I also removed instructions for fetch, because I think wget and curl cover the vast majority of use cases.

Also, I'm hard-wired to notice "OS X", so I updated that to "macOS".


chore: Use released code for publishing docs

Removes the need to set INCLUDE_RELEASED_CODE when building docs, and just builds off the published images of sandbox and l1-contracts on dockerhub. This ensures that the API reference we are generating is actually from the latest release and not from whatever's on master (which is a bug we have today).
Note that we keep the INCLUDE_RELEASED_CODE logic in our docs build script just to try it out locally.

Note that this doesn't work as-is since include-code macros need access to both released code and latest code (as a fallback). This only gives access to latest code.

Comments from Charlie on this PR from back in the day, so they don't just sit on my Slack:

We generate docs from l1-contracts as well? Sad face. (edit: ah, I see it's all around messaging stuff)
Docker ignore files can be next to their Dockerfile if named same as Dockerfile and postfixed .dockignore e.g. Dockerfile.prod.dockerignore
Why do we need a second Dockerfile and job/manifest entries? Do we not just make docs always build from released version? i.e. why not replace Dockerfile with Dockerfile.prod, what do we need Dockerfile for now?
buildDir can now be docs, which means in theory you can just name the dockerignore file .dockerignore.
No rebuild patterns required now, as we only need rebuild if docs changes, which is the default pattern if buildDir is docs and no rebuildPatterns are provided. (edit: Hmmmmm. This is true in the master case, but not in the tagged case, as the code may have changed, but the docs may not have. But it's also unnecessary to rebuild the docs if master code changed, as we don't use it in the docs. Perhaps the "correct" solution, is to use release-please to update the version tag on the FROM , this means its always clear what it's building off, and that the content-hash changes. Technically we could inject the version into any file covered by the rebuildPatterns, but that might be the most sensible thing.)
Shouldn't the job that depends on deploy-and-release deploy-docs, be the one that runs only for tags? and then we want to run the same job, but with no dependencies, on master. In fact for simplicity (otherwise we actually need to duplicate the same job), can we just have the same job run for both master and tags? Means that a master release has to wait for the whole pipeline but think that's ok for simplicity.
Also we're kind of using the term "release" for publishing stuff, and "deploy" for running infrastructure. So maybe name  job release-docs.

And also an issue with this approach:

I spotted an issue with the solution I pushed: new docs that reference code from unreleased files need to be able to read from master. [...] We can handle this by building FROM the dockerhub released version and FROM the ecr cache, and copying them to different folders. It's doable, we just need to tweak this script a bit.

Closing in favor of #4928


Add ability to flash / launch a fap from Rust

It would be good to remove the remaining python/fbt tooling from the development toolchain/flow entirely. I had a quick looksies at how the official flipper zero tooling does file transfers and it looks like it might actually be very easy:
https://github.com/flipperdevices/flipperzero-firmware/blob/663eb6cd6d4a14d00caf93d402b71eadb9a4d63f/scripts/flipper/storage.py#L203
I'm getting back into Flipper stuff again (needless to say I need to rewrite all my trash onto your mature crates lol), so I might give this a go if you don't get around to it first.

Hi @twitchyliquid64,
That would be great! That was part of the intent for the tools crate (a simple serial client, storage client, etc.), but hadn't had the opportunity.
Would happily accept something like that.

I've started working on serial support in #54.

I had attempted to do it in bash but gave up once i saw how easy it was to copypasta storage.py and call one method.
The draft looks great!

Merged in support for serial_cli and storage tools. 🎉
Would greatly appreciate if you could check it also works on your platform.

I was able to run the serial_cli tool, but the CTRL+] to exit thing didnt work for me.