[BUG] After pushing RUN button got an error on the terminal page.

WHen i try to push the RUN button, got an error on the terminal page and the program does not do anything.

It means running "certuil" command failed. Make sure you have this command.
By default windows 10 has this command.

I'm running windows 11, should i install it somehow?

OK i can confirm I have certutil on windows 11, probably the program is not able to find it and i dunno if i can force that

windows 11 has this, I guess it is caused by antivirus don't allow you run this program. Please add the whole folder into whitelist and try.

can you run the command using admin in the folder and see any output?
certutil -delstore -f root .\\certs\\cert.crt

root "Autorità di certificazione radice attendibili"
CertUtil: - Esecuzione comando delstore riuscita.
so it looks like it runs

hmm, that's weird

yep indeed i dunno what else to try :-(

looks like the app cannot find certutil, but if i run it manually it works (or at least the certutil part)
there's something i could try to do?

Can you try copy the "certutil" into the mod folder?

mmm i'll try, let me see

cannot locate certutil.exe where should it be?

Should be "C:\windows\system32\certutil.exe"

copied, no success

Sorry, I don't have any idea now.

ah i forgot i installed anaconda (i am python developer too)....dunno if it could be related.....i'll trying uninstalling it

that's cool, hope you can find out the source code and debug on it :)

ok uninstalling anaconda did not help....i really don't know what should i try....

Not getting anywhere. Ran the following and this is the reply:-
"C:\Users\Owner>c:\Windows\system32\certutil.exe
CertUtil: -dump command completed successfully"
Nothing changed and I get the same message from Lmsfs2020-google-map-2021-11-24 when I run the program.


[Task]: Storybook build and deploy for Appsmith WDS

Is there an existing issue for this?

[X] I have searched the existing issues

SubTasks
We need the WDS (Widget Design System)'s Storybook website be built and deployed to subdomains for both release and prod.
This is currently done in the build.sh script that builds the client code, at https://github.com/appsmithorg/appsmith/blob/a5d9285ff08025df9f9591ded16a69cd57455611/app/client/build.sh#LL21C13-L21C13.
But this is not needed in the final Appsmith Docker image. So we need to pull this out.

Take the build of Storybook to a separate build-wds-storybook.sh script, placed next to the client/build.sh script.
Run this script and deploy to a Vercel project, only on release, master and DP environments, and not in GitHub releases / tags.
The Storybook build should not be included in the Appsmith Docker image, of any tag/version.

Consider using release-wds.appsmith.com and wds.appsmith.com for this, since this naming style will be inline with CS.
Slack thread with additional context.

Informed: @SatishGandham @jsartisan


Feat/dropdown hidelabel

added prop hidelabel

I approved, but I think we should have a story for this, its a unique prop

Thank you @rayyan224. I'm agree with you, will add ASAP

@Y0moo Might be out of this scope but it might be nice to have this go into this smaller view as soon as, the width of the item is under a certain width? You can use a ref to get the width of the item. It would give a nice developer experience

@Y0moo you clearly need this feature and explained your reasons very clearly.
If we can improve later, great. For now i don't want to block your progress. TY both guys, great input

wow i closed that PR by accident, MY BAD!
it merged now


[PE-D][Tester C] Inconsistent spelling convention for the phrase "IC number"

In the documentation, it seems that the phrase "IC_NUMBER" should always be in a code block, whereas outside code blocks, "IC number" should be used.
However, there are several instances of "IC_NUMBER" being used outside of code blocks. For example, in the image below, both "IC number" and "IC_NUMBER" are used outside of code blocks. This could be a little confusing.

Labels: severity.VeryLow type.DocumentationBug
original: narwhalsilent/ped#14

Pure UI Change for consistency


Wildcard facet retrieval not working in react-instantsearch

🐛 Current behavior
When using the wildcard property to retrieve all facets *, the facets are not being returned by the useInstantSearch() hook.

When using the js library search function, you can retrieve all facets using wildcard. see codesandbox for repro.
This is also the same behavior on v6 using connectStateResults:
https://codesandbox.io/p/sandbox/algolia-facets-v6-5hn9rn?file=%2Fsrc%2FApp.tsx
🔍 Steps to reproduce

Setup instant search:

  <InstantSearch
      searchClient={searchClient}
      indexName="instant_search"
      routing={true}
      insights={true}
    >
      <Configure ruleContexts={[]} facets={["*"]} />
      <SearchState />
 </InstantSearch>

Use hook useInstantSearch() to retrieve results
Check the facets retrieved and it will be empty

Live reproduction
https://codesandbox.io/p/sandbox/algolia-facets-issue-9xpw2d?file=%2Fsrc%2FApp.tsx
💭 Expected behavior
Expecting to receive all facets available when using the wildcard property just like when you can retrieve them using the js client.
Package version
"algoliasearch": "4.23.2",
"instantsearch.js": "4.68.1",
"react": "18.2.0",
"react-dom": "18.2.0",
"react-instantsearch": "7.8.1"
Operating system
macOS 12.7
Browser
Chrome Version 124.0.6367.208
Code of Conduct

[x] I agree to follow this project's Code of Conduct

This has indeed always been the case, facets retrieved from the SearchResults class are only those that are manually set, as they require a second query if anything is refined.
You can however read the facets (which would be conjunctive) from rawResults.


Enable Go modules in Travis

This could help: https://arslan.io/2018/08/26/using-go-modules-with-vendor-support-on-travis-ci/
Will look into the problem when I find some time, but if somebody else wants to take a stab at it, please go ahead.


Setting --profile from the snakemake function

OS: Red Hat Enterprise Linux Server release 6.3 (Santiago)
conda version: 4.12.0
Snakemake version: 7.3.7
Is your feature request related to a problem? Please describe.
While the command-line version of Snakemake has the option to set profile (i.e.: snakemake --profile P ... works), the function version does not (i.e.: doing snakemake(profile = P, ...) from a Python script does not work). I've been using a Click-based wrapper to streamline Snakemake parameters and conditions and it would be really useful to be able to be able to switch between Slurm and bash profiles from the wrapper as well.
Describe the solution you'd like
Ability to set profiles like snakemake(profile = P, ...).
Describe alternatives you've considered
My current workaround involves setting the the environment variable SNAKEMAKE_PROFILE within the wrapper by using os.environ['SNAKEMAKE_PROFILE']. Not a lot of extra code but the suggestion would make it cleaner.

See here #1488 for why this isn't super viable right now and for other workarounds.

Understood! Thanks for the explanation. Could you provide an example of setting the profile parameter using snakemake.main(["arg1", "arg2", etc...])? I went through __init__.py to see how main() is implemented but I'm still a little confused as to how to set parameters using main()'s arguments.

Exactly the same way you call from the cli
snakemake.main(["--profile", "profile_name", "other_arg", "other_arg2", ...])


[feat] add trackByFunctionRule

closes #378

@wKoza good job! Left only one comment.

Awesome, thanks for your work on this @wKoza! 👍


WebApp - Add the "View on explorer" button on the Token details screen

Describe the task
Add the "View on explorer" button on the Token details screen

[x] Add on the Token details screen in case specific account
[x] Add on the Token details screen in case All accounts

Link design: https://www.figma.com/design/aEnkI859zkZaIpyzPidYwh/SubWallet-Apps?node-id=24085-236606&t=eg7PB3edkG4pgGnP-4

Version test : https://4bd9b850.subwallet-webapp.pages.dev/

[ ] Update button color

Version test : https://fcdf3289.subwallet-webapp.pages.dev/

[ ] UI bug in case token hasn't explorer

Version test : https://6a2ffc65.subwallet-webapp.pages.dev/
Validation passed in case :

Responsive

All account mode

Specific account mode


Python 3 support?

I'm going to file this, even if we close it as "will not fix", just to have a record.
Basically, it isn't too hard to change a Python program to make it support both 2 and 3, using six - a single file solution.
Also, this task can be done "piece at a time" - you don't have to do it all it once or even all of one file at a time.  Of course, you can't fully test it until it's all converted.
The reason to do this is because as a "patriotic" Python developer, I feel bad doing new development in 2 only.

Agreed. This will be a will not fix for master/dev, but we can tag this as
v3.0 branch only. Will be good to have. The lack of 3 support was orginally
because some dependencies didn't support it, but that's not such an issue
anymore. The main culprit was py-spidev, but v3.0 supports python 3, so
we're good.
On Wed, Mar 23, 2016 at 1:33 PM, Tom Swirly<EMAIL_ADDRESS>wrote:

I'm going to file this, even if we close it as "will not fix", just to
have a record.
Basically, it isn't too hard to change a Python program to make it support
both 2 and 3, using six https://pypi.python.org/pypi/six - a single
file solution.
Also, this task can be done "piece at a time" - you don't have to do it
all it once or even all of one file at a time. Of course, you can't fully
test it until it's all converted.
The reason to do this is because as a "patriotic" Python developer, I feel
bad doing new development in 2 only.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/44

We can support both 2 and 3 in the same codebase, though, so this isn't really a breaking change!

I realize... but at this point the v2 branch is stable and we have so many
changes planned for v3, that I'd rather just put anything that's not bug
fixes to v2 into the new v3 branch for future release. I might through a
couple new changes into v2 related to some other projects I'm working on,
but only because those projects won't want to wait for v3 to be stable.
On Wed, Mar 23, 2016 at 4:13 PM, Tom Swirly<EMAIL_ADDRESS>wrote:

We can support both 2 and 3 in the same codebase, though, so this isn't
really a breaking change!
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/ManiacalLabs/BiblioPixel/issues/44#issuecomment-200524695


Add comments and clean up code a bit

Only 3 code changes here, all trivial. I'd appreciate a read-through of the new comments, though, to make sure they're salient!

Gonna merge, we just gotta be on the lookout for little merge-conflicts later. 👍


OLS-1174: bump-up OpenAI to version 1.53.3

Description
OLS-1174: bump-up OpenAI to version 1.53.3
Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[x] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Related Tickets & Documents

Related Issue #OLS-1174

/approve

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

Project coverage is 94.01%. Comparing base (677472d) to head (56add12).
Report is 14 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1874   +/-   ##
=======================================
  Coverage   94.01%   94.01%
=======================================
  Files          62       62
  Lines        2842     2842
=======================================
  Hits         2672     2672
  Misses        170      170

see 2 files with indirect coverage changes

/lgtm

/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

/test unit

/test unit

/override "ci/prow/e2e-ols-cluster-4-16"

/override "ci/prow/e2e-ols-cluster-4-17"


Minimal version of gradle_wrapper

I download many projects and use gradle wrapper. It would be nice to be able to specify a minimal version. For example this project can be executed with any version 5.x
Expected Behavior
Use version 5.x that you have already downloaded but download the latest 5.x
Current Behavior
Download the fixed version placed in the configuration file

This could be a good idea in some ways, but it's important that a build is repeatable. Your build may work with 5.0-5.3, but fail with 5.4 and work again with 5.5.
The wrapper is intended to bootstrap the build into a good state, so I don't think we're likely to add something like this soon.


Visual Studio Test Task - surface / set resolution when running UI tests.

In 2.* of the task “Visual Studio Test” when the "Test mix contains UI tests" checkbox is ticked could you surface the resolution that the test will run at (by default) and allow this to be set greater that the default of 1024x768.
I've tried a large number of solutions to this issue but nothing seems to reset the size of the resolution the test are running at?
Thanks!
Ross

Okay so I've already tried that - things I've tried and did not work are as follows:

The extension listed above
Setting the resolution in VMware
Setting the resolution in the registry
Creating an app that sets the resolution on login

None of these actually worked, I'm assuming, due to the task setting the resolution itself, hence my request for the task to surface the resolution it's setting into the mstsc command. I'm further assuming that it's not explicitly setting a resolution hence the resolution always being 1042*768


Ethan hackpad

MyReady to submit your project? Nice job! Hopefully you've read the submission guidelines. If not, make sure to read them first.
If you're unsure about the format, make sure to check out the Orpheuspad example and follow the format there.
If this PR isn't a submission, that's okay too! If there's anything about this PR template that seems confusing, let me know in #hackpad on the slack!
I accidentally closed my pull request
This is a submission for Ethan Pope

CAD looks good as long as your USB-c cable's metal part is able to fit in there. @Hyatt B.

okay. This CAD looks good to me then. @Hyatt B.

how do i do that?

No I need the source files e.g. *.kicad_pro or *.kicad_sch or *.kicad_pcb

does that work

can someone check mine

can someone check mine

Hey @ethanJPope! I just reviewed your PR and everything looks good besides for one small issue. In the root folder, please add a folder called production, and within the folder please put in your uf2 file and your gerber.zip. Along with that, please add a sub-folder within production called cad, and put all your stls in there. After that, please let me know, so I can give my approval.

Amazing Job @ethanJPope! It looks amazing! I approve #256!
PS: My slack handle is Scooter Y

Fantastimazing Job @ethanJPope! It looks muy bien! I approve https://github.com/hackclub/hackpad/pull/254!
My slack handle is Eli

ok!
On Mon, Oct 28, 2024 at 4:37 PM M0HID @.***> wrote:

@.**** requested changes on this pull request.
Again its missing the KiCad source files!
I need the schematic (Keyboard.kicad_sch)
And the PCB (Keyboard.kicad_pcb)
Please add them to your PR so I can review!
—
Reply to this email directly, view it on GitHub
https://github.com/hackclub/hackpad/pull/254#pullrequestreview-2400436775,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BJNQNNJ2C3WVS5L2J5KLRQ3Z524BDAVCNFSM6AAAAABQNGUTDKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMBQGQZTMNZXGU
.
You are receiving this because you commented.Message ID:
@.***>

--
I am The-E

I added the source files


test: build rhel bootc image with bib

This PR uses -v /var/lib/containers/storage:/var/lib/containers/storage and --local to build RHEL image (private image repo). But it still needs to use bootc switch to do the first upgrade from container image registry, like quay.io. Otherwise system will upgrade from localhost.
@cgwalters This is the only solution to build cloud image from private image repo with bib.
cc @shi2wei3

/test-rhel94-bib-image

/test-cs9-dev-bib-image

/test-rhel94-bib-image

/test-cs9-dev-bib-image

/test-rhel94-bib-image

/test-cs9-dev-bib-image

Test passed. The aarch64 related tests are waiting for aarch64 testing farm runner to run test.


Use typescript recommended-type-checked rules

We switch from @typescript-eslint/recommended to @typescript-eslint/recommended-type-checked.
The new configuration extends the previous one with additional rules related to type information.

Do we have a reference PR with the kinds of changes this might trigger in code we've written?

Please find the reference PR here: https://github.com/thesis/acre/pull/98


Sample PowerShell cmdlet under "Accessing Metrics" contains a typo

The sample PowerShell cmdlet under "Accessing Metrics" contains a typo:
Get-AzMetric -ResourceId $resourceId -MetricNames "UsedCapacity" -TimeGrain 01:00:00
The correct parameter is  -MetricName (without a trailing 'S')

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

ID: 1dd1c1ed-ebf6-4606-b7cd-cc005fee74b2
Version Independent ID: d32aec41-af2c-82ac-e1ac-d5b7105e48cc
Content: Monitoring Azure Blob Storage
Content Source: articles/storage/blobs/monitor-blob-storage.md
Service: storage
GitHub Login: @normesta
Microsoft Alias: normesta

@W1ll1amz Thanks for the question! We are investigating and will update you shortly.


CAMEL-10443: fixing findById with ObjectId

Thanks for the PR it has been merged. Do you mind closing this?


Using Xcode Build Tool Plug-ins

Hi together,
I have written a swift package that contains a plugin which is defined as a build tool.
Am I right with my assumption that it is not yet possible to configure my project setup in a way to add the named swift package build tool plugin under my project's Build Phases, Run Build Tool Plug-ins?
Any help is highly appreciated.

XcodeGen Version: 2.32.0

Hey @nico-dkd  - my understanding is that a build tool plugin needs to be installed as a dependency on a specific target as defined in your Package.swift file. You can then integrate your local or remote package via XcodeGen by following the project spec.

Hey @nico-dkd - this is because you're applying the MySwiftPackageBuildPlugin product directly to your Xcode target. Instead, you should apply the plugin as a dependency to a Package target. That package target should then be included in the final product that you decide to build into XcodeGen as a dependency to your project "App" target.
targets:
  App:
    dependencies:
      package: MySwiftPackage
      product: MySwiftPackageProduct

and Package.swift
let package = Package(
    name: "MySwiftPackage",
    products: [
        // Products define the executables and libraries a package produces, and make them visible to other packages.
        .library(
            name: "MySwiftPackageProduct",
            targets: ["MySwiftPackageTarget"]),
    ],
    dependencies: [
    ],
    targets: [
        // Targets are the basic building blocks of a package. A target can define a module or a test suite.
        // Targets can depend on other targets in this package, and on products in packages this package depends on.
        .target(
            name: "MySwiftPackageTarget",
            dependencies: [],
            plugins: [
                <my_plugin_target>
            ]
        )
    ]
)

With Xcode 14 there is a new XcodeProjectPlugin framework available to integrate Swift Package Plugins with Xcode: https://developer.apple.com/documentation/xcode-release-notes/xcode-14-release-notes (search "XcodeProjectPlugin" on that page). I don't have experience with it to help you out @nico-dkd, but you are right that you should be able to integrate your plugin with Xcode projects.

Let us know how you go @nico-dkd. See if you can get it working by manually configuring the Xcode project within Xcode, to confirm whether it's something that needs to be added to XcodeGen.

@yonaskolb What exactly do you mean when you say, to be clear what do I need to do?

...manually configuring the Xcode project within Xcode...
I'm able to add my build plugin accordingly manually by hand.

Discussion on implementation here https://github.com/yonaskolb/XcodeGen/issues/1290


select/bsp-select.tmpl.html 404 (Not Found)

Hi Guys,
First at all, thank you very much for developing this directive. I have a question.I am new in directive Do I need to copy the  bsp-select.tmpl.html?
Best Regards
Hank

No.
Either you have to access it through other means, HTTP request, or add it to your existing code with
<script id="bsp-select.tmpl.html" type="text/ng-template">


Add additional card fields to project query

Currently cards are missing tags, assignee and deadline

Blocked by #10


Execution optimizations have been disabled warning when sourcesJar task is configured.

Jte gradle plugin throws the Execution optimizations have been disabled warning when  withSourcesJar is enabled for java + kotlin project. Seems like the proper fix should be done in the plugin to add the explicit dependency to source jar.

Environment

Gradle: 7.4.2
Java: JDK 19
JTE: 2.0.2
Kotlin: 1.6.21

Gradle config

java {
    withSourcesJar()
    withJavadocJar()

    toolchain {
        languageVersion.set(JavaLanguageVersion.of(19))
    }
}
...

jte {
    contentType.set(ContentType.Plain)
    generateNativeImageResources.set(true)
    generate()
}

Gradle warning

> Task :processResources
Execution optimizations have been disabled for task ':processResources' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: 'xxxx/build/generated-resources/jte'. Reason: Task ':processResources' uses this output of task ':generateJte' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.

> Task :sourcesJar
Execution optimizations have been disabled for task ':sourcesJar' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: 'xxxxxxx/build/generated-resources/jte'. Reason: Task ':sourcesJar' uses this output of task ':generateJte' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
  - Gradle detected a problem with the following location: 'xxxxxxx/build/generated-sources/jte'. Reason: Task ':sourcesJar' uses this output of task ':generateJte' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.

Workaround to avoid the warning

listOf("sourcesJar", "processResources").forEach {
    tasks.named(it) {
        dependsOn(tasks.generateJte)
    }
}

Thanks for reporting!
While trying to reproduce this I ran test/jte-runtime-cp-test-gradle-convention and got a similiar output there:
> Task :processResources
Execution optimizations have been disabled for task ':processResources' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: 'xxx/jte/test/jte-runtime-cp-test-gradle-convention/build/generated-resources/jte'. Reason: Task ':processResources' uses this output of task ':generateJte' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.

I'll have a look if I can get it to work with help of the commit you shared.

@sureshg Since https://github.com/casid/jte/commit/531c11fbcdd9656f6c88b9071bd185fc331952de the warning is gone 👍

@sureshg version 2.0.3 is finally released, including this fix :-)


Listener should return vendor.

Example on the Mac OSX listener,
GET http://localhost:59840/
{
"vendor": {
"name": "Couchbase Lite (Objective-C)",
"version": "1.2.1 (build 13)"
},
"couchdb": "Welcome",
"CouchbaseLite": "Welcome",
"version": "1.2.1 (build 13)"
}

Example on the Android listener,
GET http://<IP_ADDRESS>:5984/
{
"couchdb": "Welcome",
"CBLite": "Welcome",
"version": "1.2.1"
}

According to @snej, the vendor property is part of the CouchDB REST API.
Expected: vendor is returned when issuing a GET to the host:port that CBL Lite Android listener is running on.
Actual: vendor is returned when issuing a GET to the host:port that CBL Lite Android listener is running on.
Also, as an enhancement, it would be really nice if the vender could return the version AND build to provide more explicit validation and debugging when looking into issues.

Hi @sethrosetter,
About version field, I think you are using 1.2.1 release version. There is no build number for release build.

@hideki Thanks


LessWrong 1.0 URLs with comment anchors don't point to the intended comment

LW 1.0 has specific "comment URLs" (the slug after the final /) and in addition has "comment anchors" (the optional slug after #). It looks like LW 2.0 only has the latter, but uses the former from LW 1.0 to point to a comment. This means if a LW 1.0 URL has both a comment URL and comment anchor, the information contained in the comment anchor is lost.
Some examples to show what I mean:

http://lesswrong.com/lw/nzp/astrobiology_iii_why_earth/dfyq?context=1#dg24 In LW 1.0, this points to CarlShulman's comment "Primates and eukaryotes would be good" while the comment above it by CellBioGuy is highlighted in yellow. If I go to the corresponding link by replacing lesswrong.com with lesserwrong.com, I am taken to CellBioGuy's comment at https://www.lesserwrong.com/posts/PJ4RPks9GkWYgdmxx/astrobiology-iii-why-earth#cTSbRieWQKJWLpJ9x and there is no indication that Carl's comment was somehow relevant to the original URL.
http://lesswrong.com/lw/mrp/a_toy_model_of_the_control_problem/#cr6t should point to CarlShulman's comment starting with "Of course, with this model it's a bit of a mystery why A gave B", but http://lesserwrong.com/lw/mrp/a_toy_model_of_the_control_problem/#cr6t points nowhere on the new page (the scrolling just stays at the top).
http://lesswrong.com/lw/mrp/a_toy_model_of_the_control_problem/cr6t#cr7a should point to Kyre's comment, but on LW 2.0 it just goes to Carl's comment above.

Oh, thanks a lot for letting us know about that. I was totally unaware of that functionality and we should restore it. Do you have any suggestions for what the best way to restore that information in the new LW 2.0 design would be?

For me, it would be most intuitive if it worked basically like LW 1.0. So the LW 1.0 comment anchor would be used to decide where to scroll down to on LW 2.0, and the LW 1.0 comment URL would be used to decide which comment on LW 2.0 to highlight (LW 2.0 currently doesn't do a stable highlight, and I'm not sure how difficult this would be to implement).
Alternatively (to preserve the current "LW 1.0 comment URL = LW 2.0 anchor" relationship), the comment corresponding to the LW 1.0 comment anchor could somehow be marked (perhaps with a background color).


Small README improvements

Simple change so there is not so much whitespace at the top of the README. I also downsized the logo a bit and added a more verbose title.

I made another change to downsize the logo further and add a more verbose description of PySurfer in the title.

Coverage remained the same at 77.92% when pulling 3b3ee90a354a6b90b9c8d0e1ea0c94ebec034a50 on mwaskom:crop_readme_image into 99594f9a741f6314607fab46d4a1ad113cdb4354 on nipy:master.

Coverage remained the same at 77.92% when pulling 3b3ee90a354a6b90b9c8d0e1ea0c94ebec034a50 on mwaskom:crop_readme_image into 99594f9a741f6314607fab46d4a1ad113cdb4354 on nipy:master.

Still LGTM

thx @mwaskom


Added troubelshooting section

Troubleshooting section with known errors. Added workaround for #362

Welcome to the Ignite contributor list! 🎉


Update README.md

Add Stack and Cause to error check for documentation

Thanks for the PR!
I think in this case, it would be good to use errors.As.  Though, what do you think?
var evalErr *quickjs.Error
if errors.As(err, &evalErr) {
    fmt.Println(evalErr.Cause)
    fmt.Prnitln(evalErr.Stack)
}

Also, it would be good to update the example code at examples/main.go. Thanks once again!

I didn't know this existed 😄 Thanks for the info!

LGTM.


Add SELinux support

You should also add in the conf dir since selinux assumes the conf files are /etc/redis.*\.conf
selinux_policy_fcontext "#{current['configdir']}(/.*)?" do
  secontext 'redis_conf_t'
end

Okay, added that.

Think it would be relatively easy to add testing in test-kitchen, can you have a look at that?

Done! I think the Travis failure was unrelated.

Re-triggered travis and it passes


Implement Enable-SSHRemoting cmdlet

We need an Enable-SSHRemoting cmdlet, similar to existing Enable-PSSession cmdlet for WinRM based remoting, to set up SSH remoting on supported platforms.  This would make using SSH remoting easier to use and also allow automated testing of SSH remoting.
https://github.com/PowerShell/PowerShell-RFC/blob/master/1-Draft/RFC0012-Enable-SSH-Remoting.md

Agreed
Configuring SSH for remoting is tsk that is better automated if at all possible

Per conversation with @SteveL-MSFT, we might want to push this out depending on how the Win32-OpenSSH work lands.
It might even make sense to push this work out to after the OpenSSH work lands to make sure that we don't end up having to do breaking changes if/when the configuration mechanisms for Win32-OpenSSH change.

I think what we may end up doing is just having a setup script in the demo folder and we can blog about it to inform users of it's existence who don't work out of GitHub

I am working on a set up script right now as a prototype for the Cmdlet.  I don't think we should worry about Win32-OpenSSH breaking PowerShell remoting since it is intended to be closely compatible with other platform versions of SSH.

I think we can publish this in PowerShellGallery initially and target inclusion in the package for 6.1.0

Two years later I'm still hoping this is implemented. I just had to write PS scripts to do this while provisioning Windows 7 and Windows 10 PCs. For windows 10 I followed several articles on docs.microsoft.com [1][2]. For Windows 7 I used chocolatey.
For configuring the keys I followed the guide at https://docs.microsoft.com/en-us/windows-server/administration/openssh/openssh_keymanagement. It'd be nice to see Repair-AuthorizedKeyPermission fixed with this effort too.

@PaulHigin has a working version, just need to publish to PSGallery.  Won't be in PS7, but can be in 7.1.

A version 0.1.0 of PowerShell remoting tools module has been published, and which contains the Enable-SSHRemoting cmdlet.
https://www.powershellgallery.com/packages/Microsoft.PowerShell.RemotingTools/0.1.0


Generating only the best and last parameters

Which parameter can I use when I only want to generate the best and last params, in order to save storage space?

The training arguments to control this are:
  --keep-last-params KEEP_LAST_PARAMS
                        Keep only the last n params files, use -1 to keep all files. Default: -1
  --cache-last-best-params CACHE_LAST_BEST_PARAMS
                        Cache the last n best params files, as distinct from the last n in sequence. Use 0 or negative to disable. Default: 0

Thank you, @mjdenkowski. It's working!
Are there also parameters to reduce the decode.output.0.x files as well?

Currently there is no option to clean up decoding outputs.

Thanks again. It's a pity that the decoding outputs can't be reduced so easy.
Question is answered.

Do you actually need the checkpoint BLEU scores? If not you can disable the checkpoint decoder: --decode-and-evaluate 0.

Yes, I need the BLUE scores to evaluate my translation.


Decoder is only considering unlabeled data?

Starting from line 205 of ladder.py it looks like only the unlabeled data is considered for the decoder.
This is different from how I understood the paper, where it seem like all data is used for the encoder and decoder.
If that is really not the case, shouldn't then in the fully supervised scenario the ladder turn just into a normal MLP? Where is then the boost in classification accuracy coming from?

Thanks for the question!
Disclaimer: I work at the Curious AI Company.
That part of the code is indeed a bit unclear how exactly we do the decoder. In Fuel, we have the labeled data stream and unlabelled data stream. In the unlabelled data stream, the label data indices are included already. Check: https://github.com/CuriousAI/ladder/blob/master/run.py#L130
Therefore, if we have unlabelled data only in the decoder, we actually have the labeled data already through the decoder part.
Hope this solves some of your doubts.
Again, sorry for being not so responsive on this channel. We will get on speed better now!
Cheers!

Thanks, that helped a lot to understand this issue.

I'm a bit confused about the SemiDataStream class.
Here the iterator cycles through labeled data until unlabeled data depletes:
def get_epoch_iterator(self, **kwargs):
        unlabeled = self.ds_unlabeled.get_epoch_iterator(**kwargs)
        labeled = self.ds_labeled.get_epoch_iterator(**kwargs)
        assert type(labeled) == type(unlabeled)

        return imap(self.mergedicts, cycle(labeled), unlabeled)

    def mergedicts(self, x, y):
        return dict(list(x.items()) + list(y.items()))

It seems like, for example, if there are 10000 unlabeled samples and 1000 labeled samples, labeled samples are fed to the network 10 times in each epoch and unlabeled samples are used once. Also there are both unlabeled samples and labeled samples in each batch.
Am I correct?
Thanks!


Add Great Empires showcase

Name: Great Empires
Description: Building ancient era metaverse on Cardano Blockchain. Phase 01 : Digital Collectible Card Game, Phase 02 : Metaverse, Utility token of the ecosystem GREMP
Link:  https://greatempires.io/
Source: null
Tags:

game
nativetoken
nft

also (@katomm @rdlrt @fill-the-fill) are we violating a naming convention by allowing _ in the image filename?  All the others currently only use - for a delimiter.

Based on requirements taken from showcase.js file, imho the project is not ready to be added to the list. I don't see anything except seed sale.

REQUIREMENTS FOR ADDING YOUR PROJECT TO THE SHOWCASE SECTION:

It has to have a running product. (no presale, no protected pages, no coming soon messages)

Hi all,
Thank you very much for your inputs..We are working toward the product, Will have the demo product soon.

are we violating a naming convention by allowing _ in the image filename?

I'm not sure if we require that anywhere, but I agree it would just be nice to be consistent with naming.

Closing this as it violates "no presale" rule.


tvOS and watchOS support break release

Describe the bug
tvOS and watchOS support was recently added in #18  , unfortunately this seems to have broken the release. Cocoapods believes these are incompatible with SwiftEventBus, which already have a dependency on in this project
Steps to reproduce the bug
No response
Expected behavior
No response
Logs, error output, etc.
No response
Screenshots

Additional context
No response
Unleash version
N/A
Subscription type
No response
Hosting type
No response
SDK information (language and version)
N/A

Hi @tylerjonesio!
Thought I'd ask for your advice on this one since you seem to know a bit more than us. It looks like the recent PR to add this has broken the release process, so we can't actually release the new changes to support tvOS and watchOS. Internally we depend on the SwiftEventBus package, which is pretty deeply integrated into the SDK, and that seems to conflict with tvOS/watchOS. If you have some suggestions on making this work we would love to hear them (but if they're a bit complex to implement then it might have to go onto our backlog for a bit).
Right now we'd like to leave this change in, in the hopes that someone is able to take a closer look in the next few weeks but if we can't get this resolved, we're planning on reverting the commit start of next month so that the main branch stays clean and we don't forget about it

Closed by https://github.com/Unleash/unleash-proxy-client-swift/pull/23


Models are broken when inserting from Fuel

I've tried to drag and drop several models from Fuel, but they're not loaded correctly.
The red hatchback model cannot find the wheel textures, the PR2_SDF17 has some problems at the joint description, and the x4_uav model doesn't give any errors, but it is exploded.

I've copied the empty.sdf file in my own folder and changed the rendering to ogre, as described here: https://github.com/ignitionrobotics/ign-gazebo/issues/344#issuecomment-691182579
When I'm running the updated file the ignition collapses as soon as I try to insert any model from Fuel.

Some problems loading models are issues with the model, others are issues on Ignition. This is the flow to address these issues:

Is it a bug in Ignition, such as a crash or some mesh that's loading incorrectly?

Ticket an issue in the appropriate library if there isn't yet an issue for that specific bug.

Is it a problem with the model description itself (i.e. it doesn't follow the guidelines in https://github.com/ignitionrobotics/ign-gazebo/pull/400)?

Is the models in the Open Robotics account?

Ticket an issue on https://github.com/ignitionrobotics/docs/ if there isn't one yet.

Otherwise, contact the model owner.

That said, about the specific models you're trying to load:

https://app.ignitionrobotics.org/chapulina/fuel/models/hatchback_red: not an Open Robotics model (I'm the owner and I put experimental models in my account that may not work)
https://app.ignitionrobotics.org/OpenRobotics/fuel/models/PR2_SDF17 and https://app.ignitionrobotics.org/OpenRobotics/fuel/models/X4 UAV: it looks like you ran into a bug, but they load fine for me. Can you provide information about your system? What Ignition version, what operating system, graphics card...

I was able to reproduce this on both Citadel and Dome (both source build) on Bionic 18.04.
It looks like a sdformat bug.
Here's the terminal output and screenshot:
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [torso_lift_link] as parent and [torso_lift_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_r_finger_tip_link] as parent and [r_gripper_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_l_finger_tip_link] as parent and [r_gripper_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_r_parallel_link] as parent and [r_wrist_roll_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_l_parallel_link] as parent and [r_wrist_roll_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_r_parallel_link] as parent and [r_gripper_r_finger_tip_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_l_parallel_link] as parent and [r_gripper_l_finger_tip_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [r_gripper_r_finger_tip_link] as parent and [r_gripper_l_finger_tip_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_r_finger_tip_link] as parent and [l_gripper_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_l_finger_tip_link] as parent and [l_gripper_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_r_parallel_link] as parent and [l_wrist_roll_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_l_parallel_link] as parent and [l_wrist_roll_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_r_parallel_link] as parent and [l_gripper_r_finger_tip_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_l_parallel_link] as parent and [l_gripper_l_finger_tip_link] as child, but the child link already has a parent joint of type [RevoluteJoint].
[Err] [SDFFeatures.cc:720] Asked to create a joint between links [l_gripper_r_finger_tip_link] as parent and [l_gripper_l_finger_tip_link] as child, but the child link already has a parent joint of type [RevoluteJoint].

Thanks for checking @claireyywang . I think there are 2 separate issues. I also get the error messages, but I don't see any broken behaviour on the robot, pressing play all the joints seem to be in place.
The most pressing issue are the distorted meshes, and I'm not sure how to reproduce that.

Some problems loading models are issues with the model, others are issues on Ignition. This is the flow to address these issues:

Is it a bug in Ignition, such as a crash or some mesh that's loading incorrectly?

Ticket an issue in the appropriate library if there isn't yet an issue for that specific bug.

Is it a problem with the model description itself (i.e. it doesn't follow the guidelines in #400)?

Is the models in the Open Robotics account?

Ticket an issue on https://github.com/ignitionrobotics/docs/ if there isn't one yet.

Otherwise, contact the model owner.

That said, about the specific models you're trying to load:

https://app.ignitionrobotics.org/chapulina/fuel/models/hatchback_red: not an Open Robotics model (I'm the owner and I put experimental models in my account that may not work)
https://app.ignitionrobotics.org/OpenRobotics/fuel/models/PR2_SDF17 and https://app.ignitionrobotics.org/OpenRobotics/fuel/models/X4 UAV: it looks like you ran into a bug, but they load fine for me. Can you provide information about your system? What Ignition version, what operating system, graphics card...

I'm using Ignition Citadel, Ubuntu 20.04, and my graphics card is: NVIDIA Corporation GP106BM [GeForce GTX 1060 Mobile 6GB]

The distorted meshes appear to be similar to https://github.com/osrf/subt/issues/438. Can you try testing with the instructions in this or this comments?
The [Err] [SDFFeatures.cc:720] Asked to create a joint between links [torso_lift_link] as parent and [torso_lift_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint]. errors are most likely due to the fact that ign-gazebo doesn't currently support kinematic loops with DART.

Oh so this is another locale issue. Here are other related issues: https://github.com/ignitionrobotics/ign-rendering/issues/101, https://github.com/ignitionrobotics/ign-rendering/issues/136

@anindex fyi

The distorted meshes appear to be similar to osrf/subt#438. Can you try testing with the instructions in this or this comments?
The [Err] [SDFFeatures.cc:720] Asked to create a joint between links [torso_lift_link] as parent and [torso_lift_motor_screw_link] as child, but the child link already has a parent joint of type [RevoluteJoint]. errors are most likely due to the fact that ign-gazebo doesn't currently support kinematic loops with DART.

I've tried to run Ignition with an english locale like suggested in the links above and it worked! Thanks!
I haven't changed the whole system locale I just used the following command to run Ignition:
LC_ALL=C LANG=C ign gazebo empty.sdf

I still receive some errors, but the meshes are rendered properly.

Closing this issue. Summary:

The hatchback model in the chapulina account is experimental
The PR2 and X4 distortions are locale issues that are being tracked on https://github.com/ignitionrobotics/ign-rendering/issues/136


Parsing PrimaryPackagePurpose of OPERATING-SYSTEM fails

If a SPDX 2.3 tag/value file contains PrimaryPackagePurpose: OPERATING-SYSTEM then attempts to convert the file, or to deserialize it using SpdxToolsHelper.deserializeDocument will fail with org.spdx.tag.InvalidSpdxTagFileException: Unknown Package Purpose: OPERATING-SYSTEM
This value is perfectly valid according to the spec:
https://spdx.github.io/spdx-spec/v2.3/package-information/#724-primary-package-purpose-field
The problem seems to be that the enum member is named OPERATING_SYSTEM (note the underscore)

Thanks @medcrypt-matt for reporting this.  This should be a straightforward fix, but it may be a while before I get to it myself.  If you want to create a PR, I can review / merge otherwise I'll take a look once I finish the 3.0 upgrades to the library.


Connectivity issues with IPsec after node reboot

Bug report
We run flatcar-linux in our production clusters and since we updated to cilium 1.9 pods don't get connectivity after node reboots.
To fix it, we need to manually delete the cilium-agent pod on the corresponding node.
cilium-health status reports host connectivity to other nodes, but both ICMP to stack and HTTP to stack report timeouts.
Reproducible on both cilium 1.9.6 and 1.9.7, against recent Flatcar Linux stable versions (tested against 2765.2.3, 2765.4, 2765.2.5)
/cc: @johannwagner @Jasper-Ben
General Information

Cilium version: 1.9.7
Kernel version: 5.9.11, 5.9.16, 5.10.16, 5.10.25, 5.10.32, 5.10.37
Orchestration system version: Kubernetes 1.20.7
Link to relevant artifacts: To be followed, I'm working on building a reproducible deployment set.
Generate and upload a system zip: (To be followed from reproducible deployment)

How to reproduce the issue

Setup Cilium 1.9.7 on a Cluster consisting of Flatcar Linux nodes
Reboot one node
See that the pods don't get connectivity on the rebooted node, until the cilium agent on this node is deleted and recreated

Just got it reproduced in a test environment, I'll be preparing that into a repo and link it here.
After deploying the connectivity test and rebooting one node, I see the following:
cilium-health status (on the master node, not rebooted)
Probe time:   2021-05-22T12:37:04Z
Nodes:
  master-test-node (localhost):
    Host connectivity to a.b.c.110:
      ICMP to stack:   OK, RTT=546.361µs
      HTTP to agent:   OK, RTT=404.004µs
    Endpoint connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=528.017µs
      HTTP to agent:   OK, RTT=405.057µs
  worker-test-node:
    Host connectivity to a.b.c.233:
      ICMP to stack:   OK, RTT=1.081699ms
      HTTP to agent:   OK, RTT=1.396567ms
    Endpoint connectivity to <IP_ADDRESS>:
      ICMP to stack:   Connection timed out
      HTTP to agent:   Get "http://<IP_ADDRESS>:4240/hello": context deadline exceeded (Client.Timeout exceeded while awaiting headers)

On the worker node (after reboot):
Probe time:   2021-05-22T12:39:37Z
Nodes:
  worker-test-node (localhost):
    Host connectivity to a.b.c.233:
      ICMP to stack:   OK, RTT=627.376µs
      HTTP to agent:   OK, RTT=520.044µs
    Endpoint connectivity to <IP_ADDRESS>:
      ICMP to stack:   OK, RTT=580.217µs
      HTTP to agent:   OK, RTT=319.138µs
  master-test-node:
    Host connectivity to a.b.c.110:
      ICMP to stack:   OK, RTT=1.461229ms
      HTTP to agent:   OK, RTT=655.739µs
    Endpoint connectivity to <IP_ADDRESS>:
      ICMP to stack:   Connection timed out
      HTTP to agent:   Get "http://<IP_ADDRESS>:4240/hello": dial tcp <IP_ADDRESS>:4240: i/o timeout (Client.Timeout exceeded while awaiting headers)

Connectivity test was deployed before the worker node was rebooted and afterwards I get this result:

My cilium config looks like this:

# Source: cilium/templates/cilium-configmap.yaml
apiVersion: v1
kind: ConfigMap
metadata:
  name: cilium-config
  namespace: kube-system
data:
  identity-allocation-mode: crd
  cilium-endpoint-gc-interval: "5m0s"

  debug: "false"
  enable-policy: "default"
  enable-ipv4: "true"
  enable-ipv6: "true"
  custom-cni-conf: "false"
  enable-bpf-clock-probe: "true"
  monitor-aggregation: medium
  monitor-aggregation-interval: 5s
  monitor-aggregation-flags: all
  bpf-map-dynamic-size-ratio: "0.01"
  bpf-policy-map-max: "16384"
  bpf-lb-map-max: "65536"
  preallocate-bpf-maps: "false"

  sidecar-istio-proxy-image: "cilium/istio_proxy"

  cluster-name: default
  cluster-id: ""

  tunnel: vxlan
  enable-l7-proxy: "true"

  wait-bpf-mount: "false"

  masquerade: "true"
  enable-bpf-masquerade: "true"
  enable-ipsec: "true"

  ipsec-key-file: /etc/ipsec/keys
  enable-xt-socket-fallback: "true"
  install-iptables-rules: "true"

  auto-direct-node-routes: "false"
  enable-bandwidth-manager: "false"
  enable-local-redirect-policy: "false"
  kube-proxy-replacement:  "probe"
  kube-proxy-replacement-healthz-bind-address: ""
  enable-health-check-nodeport: "true"
  node-port-bind-protection: "true"
  enable-auto-protect-node-port-range: "true"
  enable-session-affinity: "true"
  enable-endpoint-health-checking: "true"
  enable-health-checking: "true"
  enable-well-known-identities: "false"
  enable-remote-node-identity: "true"
  operator-api-serve-addr: "<IP_ADDRESS>:9234"
  enable-hubble: "false"
  ipam: "cluster-pool"
  cluster-pool-ipv4-cidr: "<IP_ADDRESS>/8"
  cluster-pool-ipv6-cidr: "fd00::/104"
  cluster-pool-ipv4-mask-size: "24"
  cluster-pool-ipv6-mask-size: "120"
  disable-cnp-status-updates: "true"
---

I think I've got a pretty good view of what is actually going on here. As far as I can tell it's OS-independent, but affects all users with IPSec enabled, possibly more.
What happens when I reboot a node, cilium_host gets a new IP address assigned which the cilium operator writes into the kubernetes corev1.Node (Annotation) as well as the CiliumNode
What now happens is that the agent only adds the new address to the list of addresses to the CiliumNode, and does not remove the old addr.
This then leads to an array where the new address is appended at the end. When generating IPSec policies (and possibly consuming CiliumNode objects from third party code), the cilium code only parses the first CiliumInternalIP and uses that for policy generation, which is now outdated.
Therefore, to fix that the agent needs to remove the old CiliumInternalIP from the CiliumNode or even regenerate the whole node addr list.

Thanks to comment https://github.com/cilium/cilium/issues/15568#issuecomment-847735854 we can now confirm, that this is indeed an OS-independent bug and should affect anyone using IPsec. @martin31821: could you change the issue title to reflect the issue and impact more precisely? Thanks!

@Jasper-Ben @martin31821 I've created https://github.com/cilium/cilium/pull/16307 to fix this. Could you try it out and confirm that it resolves your reboot issue?

Unfortunately, a quick test did not seem to work. Could be a case of PEBCAK though :smile:. I'll take a closer look tomorrow.

@Jasper-Ben Were you able to confirm or did it not solve your issue? If not, could you provide the cilium-agent logs?

Hi @christarazi,
After testing it I can confirm the PR indeed solves our issue.
The cilium_host device gets the same IP assigned as before the reboot.

thanks @martin31821! I didn't get around to test it again yesterday


suggest

能否记录下返回的结果呢，因为这个插件在用于测试API接口的时候需要这个功能，这样子便于调试。
Can record the result returned, because this plug-in when used to test the API interface to need this functionality, it easy to debug.

Indeed, it can be a useful functionality. It would be better to have a settings directive to turn this functionality on or off because some API outputs may be too large to store.

@yubang would you like to participate as a coder in the implementation of this?


crash at untrackState method

xcode 8.2
earlgrey 1.6
it happened many times and not in the same test.
this issues also in xcode 8.1 and earlgrey1.5.3.
all the tests spend about 3 hours to complete.（this test about 30 minutes.）
but if re-run the tests maybe it will be pass.

This seems like EG is waiting for a tracked objected to get untracked. Are there any console logs generated? You should be able to see what EG is waiting on there. It would also be great if you could please give us an idea of what you're testing over here for the error to be seen. Is it the same ViewController? Are there any animations / network requests etc. happening?

there is another call stack.

it looks like this controller is dead when it is being requested.
but there is no issue running xcodebuild test command under the terminal .

Hi @heemoe, is this still an issue with latest release (1.7.0) of EarlGrey?

@khandpur After a few days I'll try this new version

Fixed, thank for your help.


Unable to download deployment content (walkthrough fails)

https://raw.githubusercontent.com/iainfoulds/architecture-center/aks-devops/docs/sample-solutions/app-modernization/templates/devops-with-aks/nested/grafana.json
does not exist, walkthrough fails
{
  "code": "InvalidContentLink",
  "message": "Unable to download deployment content from 'https://raw.githubusercontent.com/iainfoulds/architecture-center/aks-devops/docs/sample-solutions/app-modernization/templates/devops-with-aks/nested/grafana.json'. The tracking Id is 'b71a850c-815c-4226-872a-23743588861e'. Please see https://aka.ms/arm-deploy for usage details."
}

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

ID: fbbd6dbf-a5be-f8cf-4f8d-08809db1d973
Version Independent ID: 50b13de9-334d-0db5-492c-862935df2cd9
Content: Create and use an SSH key pair for Linux VMs in Azure - Azure Virtual Machines
Content Source: articles/virtual-machines/linux/mac-create-ssh-keys.md
Service: virtual-machines
GitHub Login: @cynthn
Microsoft Alias: cynthn

@naspinski Where are you seeing a link to https://raw.githubusercontent.com/iainfoulds/architecture-center/aks-devops/docs/sample-solutions/app-modernization/templates/devops-with-aks/nested/grafana.json in this article? I'm not finding it at all.

I can't remember which page you are referring to, please give me the link.
Stan Naspinski

The Lumberjack https://www.thelumberjackmn.com/
Cohesive Real Estate http://cohesive.condos
Chili Lime Restaurant & Tavern https://chililime.net/

On Wed, Sep 8, 2021 at 6:32 PM Cynthia Nottingham @.***>
wrote:

@naspinski https://github.com/naspinski Where are you seeing a link to
https://raw.githubusercontent.com/iainfoulds/architecture-center/aks-devops/docs/sample-solutions/app-modernization/templates/devops-with-aks/nested/grafana.json
in this article? I'm not finding it at all.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/80287#issuecomment-915641468,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGMADOFTVWHU6WP2EQFJADUA7XARANCNFSM5C6FRJ5Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

This is the page that the Issue was created for: Create and use an SSH key pair for Linux VMs in Azure.  I'm not finding any mention of the this file: https://raw.githubusercontent.com/iainfoulds/architecture-center/aks-devops/docs/sample-solutions/app-modernization/templates/devops-with-aks/nested/grafana.json on that page. It looks like the link might have been in an article on the architecture center, maybe an aticle about AKS?

I suspect that this issues should have been filed on https://github.com/MicrosoftDocs/architecture-center-pr/blob/master/docs/example-scenario/apps/devops-with-aks-content.md. I don't have a way to move this issue, so I'm going to close it for now.
#please-close


Support DAI permit

Adds support for DAI special permit

Something I forgot to mention on DAI’s permit is that it does not let you choose a “value” for the allowance, you either give infinite allowance or revoke it to 0:
IDAI(asset).permit(owner, address(this), nonce, expiresAt, true, v, r, s);

you can see the true value there that means giving infinite allowance


[Bug]: uncaught exception: Cannot use 'in' operator to search for 'displayName' in undefined

Contact Details
No response
What happened?
Hi Team,
My Adapter is crashing and unload will be triggered With

uncaught exception: Cannot use 'in' operator to search for 'displayName' in undefined
TypeError: Cannot use 'in' operator to search for 'displayName' in undefined at ChromecastDevice._updateClientStatus (/opt/iobroker/node_modules/iobroker.chromecast/lib/chromecastDevice.js:639:41) at MediaPlayer.emit (events.js:400:28) at PersistentClient.emit (events.js:412:35) at PersistentClient._updateStatus (/opt/iobroker/node_modules/castv2-player/lib/persistentClient.js:334:12) at /opt/iobroker/node_modules/castv2-player/lib/persistentClient.js:262:20 at /opt/iobroker/node_modules/castv2-client/lib/controllers/receiver.js:31:5 at fn.onmessage (/opt/iobroker/node_modules/castv2-client/lib/controllers/request-response.js:27:7) at fn.emit (events.js:412:35) at Channel.onmessage (/opt/iobroker/node_modules/castv2-client/lib/controllers/controller.js:16:10) at Channel.emit (events.js:400:28)
Cannot use 'in' operator to search for 'displayName' in undefined
unload will be triggred

Help would be Great! If more infos needed, just request.
Adapter Version
2.3.1
JS-Controller Version
4.0.24
Node JS Version
14.21.2
NPM Version
6.14.17
Operating System
Debian
Relevant log output
Cannot use 'in' operator to search for 'displayName' in undefined at ChromecastDevice._updateClientStatus (/opt/iobroker/node_modules/iobroker.chromecast/lib/chromecastDevice.js:639:41) at MediaPlayer.emit (events.js:400:28) at PersistentClient.emit (events.js:412:35) at PersistentClient._updateStatus (/opt/iobroker/node_modules/castv2-player/lib/persistentClient.js:334:12) at /opt/iobroker/node_modules/castv2-player/lib/persistentClient.js:262:20 at /opt/iobroker/node_modules/castv2-client/lib/controllers/receiver.js:31:5 at fn.onmessage (/opt/iobroker/node_modules/castv2-client/lib/controllers/request-response.js:27:7) at fn.emit (events.js:412:35) at Channel.onmessage (/opt/iobroker/node_modules/castv2-client/lib/controllers/controller.js:16:10) at Channel.emit (events.js:400:28)

Anything else?
No response

2.3.1 is quite an old version. Could you please try 3.0.3? Although note this is a breaking change as the channel names will change.

Good and valid point, my repo setup was not accurate. Update was helpful! Thanks for the support!


Backfill polymer gas metrics

Backfill is in progress and should take around 13 days assuming processing speed of 1 packet/sec.
The progress can be seen by using this query
query MyQuery {
  backfill {
    channels
    channelsWithErrors
    packets
    packetsWithErrors
  }
}


feat(auth): add github proxy authentication

Hi there, here's a production-grade-aspiring implementation (w/o tests yet) of the GitHub "proxy" authentication, which provides the same access permissions to a Git LFS org/repo as are those for the same GitHub repo. It uses Github's HTTP API personal access tokens, which are used to retrieve the particular user's permissions.
The module has been developed with the focus on minimizing GitHub API traffic where feasible, so it uses a lot of [configurable] API response caching.
The next aim was to keep the new 3rd party dependencies low, which so far worked, except for the use of a small package called cachetools and marshmallow, which both are already (transitively) used by existing code. I looked around for various libs, but eventually ended up doing something that badly feels like inventing the wheel in case of thread-safe caching wrappers for the [idempotent] GitHub API calls. I didn't find any alternative, tho :shrug:, so there it is.
Everything is in a single file to avoid back-and-forth merging hassles, but it might be worth splitting some parts into separate files once/if the PR gets merged.
Originally, this was a very simple file, but then came config values, their validation, persistent connection reuse, robust error handling, caching, and ultimately further thread-safety measures.
There is also an option to change the GitHub API URL so it could be used for "enterprise servers", which have a different API endpoint than the public cloud GitHub.
I'm opening this as a draft, because I'm aware that I didn't write any docs or tests, but I also deeply desire someone to review the code, so we'd know we're on the right track and I didn't create some design issues along the way so far. Thank you.
PS: Again, thanks @athornton for letting me know about his own custom implementation which I sure used for inspiration.
Closes: https://github.com/datopian/giftless/issues/128

Do you feel like fixing the typing stuff in the test failures?  If you don't, I'll get to that when I can, but I'm kinda swamped with my day job right now.
Other than that, this looks very good.

Done... that took my last breath today :weary:
FYI, it seems the "requirements.txt" dependencies generated by pip-tools are python-version-specific. Did you notice? I guess this should be somehow reflected in the CI scripts/makefiles, right?

Nice.
Yeah, requirements.txt varies because some versions of packages require Python 3.11 or 3.12 and pip-compile uses the latest available that will work with the python you're using.  I generally develop with the mininum version (3.10 in this case) and then have the CI check that it works with 3.11 and 3.12.

I'm going to let it sit a bit in case anyone who actually works for Datopian wants to weigh in, but if not, I'll merge it tomorrow and make a new release over in lsstsqre space.  I'm still waiting for someone at Datopian to figure out what we want to do about making an official release (and pipeline), but I've been pretty swamped so I haven't been pushing them.

Well, I see no objections, so let's go ahead and merge it.

Just want to say this looks great and big props @vit-zikmund 👏👏 and thanks for the great PR management and review @athornton 👏
thanks all!


Customize the keyPadConfig of the confirm screen.

I am using your package well.
Thank you.
In confirmation:true I want to be able to customize the keyPadConfig of the confirmation screen.
I would like to have different keypads for the two screens of confirmation:true.
Thank you.

Hi, the keypads cannot be different because the inputs are compared and have to match for the user to continue.
Can you elaborate on how you would like this feature to look like?


CUB200 training result issue

hi there I trained bird dataset for 800000 iters，yet the results remain blur. Does this have somthing todo with my mask  setting?
I opened mask with mode='RGB' and deleted the code        'masks = torch.cat([masks]*3, dim = 1)'

I would assume this is due to some issues in the input mask format. Opening the mask/image with different mode is dangerous as it changes the range of value, e.g. the mask image could either be within range 0~1 (gray scale) or range 0~255 (8 bit). This then influence the values of the output images. One rule-of-thumb is to ensure that the masks used in generating composed image in model.py have only 0s and 1s in it. Otherwise things could be wired.

will, i did set mask.jpg with only 0 and 1 pixel. the celeba dataset generates better results at samilar iters. i guess it depends on the complicity of trainiing images


feat: add func invoker

What this PR does:
This PR supports local method calls (including methods within structs).
Which issue(s) this PR fixes:

Fixes #729
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Can this invoker match err to retry?

support retry now


Is pruning of quantized models supported?

Hello,
I'm attempting to train a model for a micro-controller that only supports 8-bit precision or lower.
This works perfectly when training using your QuantizationAwareTrainingConfig.
In addition to this we also want to prune the network to also reduce the number of parameters in our model.
Luckily, the prepare_compression method accepts multiple configurations to be passed to it, so I attempted to also introduce a WeightPruningConfig.
This fails however with the following traceback:
Traceback (most recent call last):
  File "test.py", line 8, in <module>
    compression_manager.callbacks.on_train_end()
  File "/lib/python3.11/site-packages/neural_compressor/training.py", line 420, in on_train_end
    callbacks.on_train_end()
  File "/lib/python3.11/site-packages/neural_compressor/compression/callbacks.py", line 226, in on_train_end
    get_sparsity_ratio(self.pruners, self.model)
  File "/lib/python3.11/site-packages/neural_compressor/compression/pruner/utils.py", line 145, in get_sparsity_ratio
    linear_conv_cnt += module.weight.numel()
                       ^^^^^^^^^^^^^^^^^^^
AttributeError: 'function' object has no attribute 'numel'

I was wondering if this is supposed to be a supported use case, and I'm doing something wrong, or is combining multiple compression methods not yet supported?
The following code can be used to minimally reproduce the error:
from neural_compressor import QuantizationAwareTrainingConfig
from neural_compressor.training import prepare_compression, WeightPruningConfig
from timm.models import create_model
quant_config = QuantizationAwareTrainingConfig()
prune_config = WeightPruningConfig([{"start_step": 1, "end_step": 10000}])
compression_manager = prepare_compression(create_model("resnet50"), [quant_config, prune_config])
compression_manager.callbacks.on_train_begin()
compression_manager.callbacks.on_train_end()

Hi,
Thanks for your interest in our project.
I will take a look into your proposed situation combined with quantization and pruning. If it is a bug, I will try to fix it. Furthermore, I would like to note that our most pruning process requires an additional training process, which may cause weight shift and make your aforementioned quantization process invalid. If you have any further questions, please do not hesitate to contact us.
Best,
Frank

Hi,
Thank you for looking into this!
I am indeed aware that the pruning process would require additional training, but would it not be possible to do this training quantization-aware?
It would not be a problem that the low-precision model weights would shift during the pruning process, that was more my intention actually.
Kind regards,
Thomas


Add support for custom hot reload config

Fixes #757 #96

Shall we document this as well.

@arunoda definitely, wanted you to check it first :)

I'm not sure if this is required, since ideally, typescript files also should be transpiled via webpack (maybe by https://github.com/TypeStrong/ts-loader). In this case you don't have to change the ignored option.

I have no good idea about #757 though :|

@nkzawa That's a good case of having this API. But not sure we should do it now or wait for 2.0?

@arunoda was thinking about this myself. I guess 2.1 since it's a new feature.

Added to readme. Also added the poweredByHeader option, since it was undocumented.

@timneutkens this looks great. Thank you.
@nkzawa in my (limited) experience of using TypeScript loaders (both ts-loader and awesome-typescript-loader) is they can introduce additional problems and confusion especially when babel plugins are also used.

@nkzawa what is the state of this PR? would love to see this merged, b.c. using next with external sheets is a bit painful :/

@nkzawa This couldn't come any sooner... Thanks for this @timneutkens

Created a new PR, cause merging master with this branch was not feasible

@timneutkens couldn't find your new PR

Hi @timneutkens!
I'm having hard times (to the point of giving up) trying to hot-reload the .sass on this example (and it mentions this PR): https://github.com/zeit/next.js/tree/v3-beta/examples/with-external-scoped-css
Do you have any documentation / example / tip on how the functionality added by this PR can be used to customize the hot-reload to detect changes on the sass files?
My goal is to have a folder per component, with a hot-reloaded js and a scss file, using scoped css, and without needing to add <style dangerouslySetInnerHTML /> on every component.
I have tried a lot without success, so any tip would be really appreciated.
Thanks a lot in advance!

Any news ? Thanks in advance !

We need this feature, resolved 👍

Stats from current PR

Default Server Mode

General

zeit/next.js canary
zeit/next.js canary
Change

buildDuration
16.1s
17.4s
⚠ +1.4s

nodeModulesSize
48.3 MB
48.3 MB
✓

Client Bundles (main, webpack, commons)

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.js
18.9 kB
18.9 kB
✓

main-HASH.js gzip
6.79 kB
6.79 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

4952ddcd88e7..2b8407376.js
21.9 kB
21.9 kB
✓

4952ddcd88e7..7376.js gzip
7.81 kB
7.81 kB
✓

de003c3a9d30..6604acae7.js
43.2 kB
43.2 kB
✓

de003c3a9d30..cae7.js gzip
15.5 kB
15.5 kB
✓

framework.5b..dbaff70d3.js
125 kB
125 kB
✓

framework.5b..70d3.js gzip
39.4 kB
39.4 kB
✓

Overall change
211 kB
211 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.module.js
17.2 kB
17.2 kB
✓

main-HASH.module.js gzip
6.52 kB
6.52 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..42.module.js
45.6 kB
45.6 kB
✓

de003c3a9d30..dule.js gzip
16.5 kB
16.5 kB
✓

framework.5b..d3.module.js
125 kB
125 kB
✓

framework.5b..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
190 kB
190 kB
✓

Client Pages

zeit/next.js canary
zeit/next.js canary
Change

_app.js
1.81 kB
1.81 kB
✓

_app.js gzip
873 B
873 B
✓

_error.js
12 kB
12 kB
✓

_error.js gzip
4.73 kB
4.73 kB
✓

hooks.js
12.7 kB
12.7 kB
✓

hooks.js gzip
4.79 kB
4.79 kB
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
8.14 kB
8.14 kB
✓

link.js gzip
3.5 kB
3.5 kB
✓

routerDirect.js
408 B
408 B
✓

routerDirect.js gzip
281 B
281 B
✓

withRouter.js
419 B
419 B
✓

withRouter.js gzip
280 B
280 B
✓

Overall change
35.8 kB
35.8 kB
✓

Client Pages Modern

zeit/next.js canary
zeit/next.js canary
Change

_app.module.js
1.7 kB
1.7 kB
✓

_app.module.js gzip
832 B
832 B
✓

_error.module.js
23.3 kB
23.3 kB
✓

_error.module.js gzip
8.59 kB
8.59 kB
✓

hooks.module.js
1.52 kB
1.52 kB
✓

hooks.module.js gzip
793 B
793 B
✓

index.module.js
294 B
294 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js
8.53 kB
8.53 kB
✓

link.module.js gzip
3.68 kB
3.68 kB
✓

routerDirect.module.js
394 B
394 B
✓

routerDirect..dule.js gzip
281 B
281 B
✓

withRouter.module.js
404 B
404 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
36.1 kB
36.1 kB
✓

Client Build Manifests

zeit/next.js canary
zeit/next.js canary
Change

_buildManifest.js
81 B
81 B
✓

_buildManifest.js gzip
61 B
61 B
✓

_buildManifest.module.js
81 B
81 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
162 B
162 B
✓

Rendered Page Sizes

zeit/next.js canary
zeit/next.js canary
Change

index.html
3.62 kB
3.62 kB
✓

index.html gzip
946 B
946 B
✓

link.html
3.66 kB
3.66 kB
✓

link.html gzip
954 B
954 B
✓

withRouter.html
3.67 kB
3.67 kB
✓

withRouter.html gzip
942 B
942 B
✓

Overall change
10.9 kB
10.9 kB
✓

Serverless Mode

General

zeit/next.js canary
zeit/next.js canary
Change

buildDuration
17.1s
18.2s
⚠ +1.2s

nodeModulesSize
48.3 MB
48.3 MB
✓

Client Bundles (main, webpack, commons)

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.js
18.9 kB
18.9 kB
✓

main-HASH.js gzip
6.79 kB
6.79 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

4952ddcd88e7..2b8407376.js
21.9 kB
21.9 kB
✓

4952ddcd88e7..7376.js gzip
7.81 kB
7.81 kB
✓

de003c3a9d30..6604acae7.js
43.2 kB
43.2 kB
✓

de003c3a9d30..cae7.js gzip
15.5 kB
15.5 kB
✓

framework.5b..dbaff70d3.js
125 kB
125 kB
✓

framework.5b..70d3.js gzip
39.4 kB
39.4 kB
✓

Overall change
211 kB
211 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.module.js
17.2 kB
17.2 kB
✓

main-HASH.module.js gzip
6.52 kB
6.52 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..42.module.js
45.6 kB
45.6 kB
✓

de003c3a9d30..dule.js gzip
16.5 kB
16.5 kB
✓

framework.5b..d3.module.js
125 kB
125 kB
✓

framework.5b..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
190 kB
190 kB
✓

Client Pages

zeit/next.js canary
zeit/next.js canary
Change

_app.js
1.81 kB
1.81 kB
✓

_app.js gzip
873 B
873 B
✓

_error.js
12 kB
12 kB
✓

_error.js gzip
4.73 kB
4.73 kB
✓

hooks.js
12.7 kB
12.7 kB
✓

hooks.js gzip
4.79 kB
4.79 kB
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
8.14 kB
8.14 kB
✓

link.js gzip
3.5 kB
3.5 kB
✓

routerDirect.js
408 B
408 B
✓

routerDirect.js gzip
281 B
281 B
✓

withRouter.js
419 B
419 B
✓

withRouter.js gzip
280 B
280 B
✓

Overall change
35.8 kB
35.8 kB
✓

Client Pages Modern

zeit/next.js canary
zeit/next.js canary
Change

_app.module.js
1.7 kB
1.7 kB
✓

_app.module.js gzip
832 B
832 B
✓

_error.module.js
23.3 kB
23.3 kB
✓

_error.module.js gzip
8.59 kB
8.59 kB
✓

hooks.module.js
1.52 kB
1.52 kB
✓

hooks.module.js gzip
793 B
793 B
✓

index.module.js
294 B
294 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js
8.53 kB
8.53 kB
✓

link.module.js gzip
3.68 kB
3.68 kB
✓

routerDirect.module.js
394 B
394 B
✓

routerDirect..dule.js gzip
281 B
281 B
✓

withRouter.module.js
404 B
404 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
36.1 kB
36.1 kB
✓

Client Build Manifests

zeit/next.js canary
zeit/next.js canary
Change

_buildManifest.js
81 B
81 B
✓

_buildManifest.js gzip
61 B
61 B
✓

_buildManifest.module.js
81 B
81 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
162 B
162 B
✓

Serverless bundles

zeit/next.js canary
zeit/next.js canary
Change

_error.js
253 kB
253 kB
✓

_error.js gzip
67.9 kB
67.9 kB
✓

hooks.html
3.75 kB
3.75 kB
✓

hooks.html gzip
979 B
979 B
✓

index.js
254 kB
254 kB
✓

index.js gzip
68.2 kB
68.2 kB
✓

link.js
261 kB
261 kB
✓

link.js gzip
70.3 kB
70.3 kB
✓

routerDirect.js
255 kB
255 kB
✓

routerDirect.js gzip
68.3 kB
68.3 kB
✓

withRouter.js
254 kB
254 kB
✓

withRouter.js gzip
68.4 kB
68.4 kB
✓

Overall change
1.28 MB
1.28 MB
✓

Commit: 3f1e19e64ad9dd2ec40a1842df6de1da8a80185a


Dynamic config doesn't apply browserslist

Neither file browserslist, nor env variable BROWSERSLIST.
browsers option in config works fine:
module.exports = ctx => {
  return [require('autoprefixer')({ browsers: ['last 50 versions'] })];
};

Looks like it happens when dynamic returns Array as described in README.
When object is returned, everything works as expected:
module.exports = ctx => ({
  plugins: [
    require('autoprefixer')
  ]
});

@prince In your first example, there is no plugins prop :) , {plugins: {} || [] } 👍☺

Yep, I've taken it from README.
So it is a README issue probably.

yep, was on mobile when replying, didn't check the repo tbh :), I will fix it

@princed thanks for report. I fixed a example: a3ea3ec
@michael-ciniawsky should we add more warnings in postcss-load-config about mistakes in config?

Great, thanks!

@ai Thx for update READEM.md hadn't found the time yet 👍

should we add more warnings in postcss-load-config about mistakes in config?

Yes, I have something in mind already and will ook at the latest issues whats needed else, a few days please 😛


Simplify the release artifact

It looks like the entire repository is part of the zip file:

I think that it would be easier from a "consumer" perspective to only download files the necessary file(s). There is nothing to prevent someone to try using lib/index.js instead of dist/standalone.js.
Would it make sense to have a Make/Gulp/Whatever target which job would be to build and package the SDK? I'm guessing that we only need:

standalone*.js
README.md
LICENCE?

Other suggestions:

Rename to something like mendeley-sdk.js
Include the version number in the file name


Spyder 2.0alpha1 - Error in IPython shell on startup

From koverholt on 2010-06-30T16:40:11Z
What version of the product are you using? On what operating system? Spyder 2.0alpha1
Mac OS X 10.6.4, Python 2.6.5
Please provide any additional information below
:
Spyder 1.1.2 works fine, this problem seems limited to the IPython shell. I can import IPython.Shell in a separate IPython process just fine.
What steps will reproduce the problem?

Start spyder normally or with --light option
IPython shell shows the following error:

'import site' failed; use -v for traceback
Traceback (most recent call last):
File "spyderlib/widgets/externalshell/startup.py", line 103, in <module>
import IPython.Shell
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/IPython/init.py", line 58, in <module>
import(name,glob,loc,[])
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/IPython/ipstruct.py", line 17, in <module>
from IPython.genutils import list2dict2
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/IPython/genutils.py", line 114, in <module>
import IPython.rlineimpl as readline
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/site-packages/IPython/rlineimpl.py", line 36, in <module>
(status, result) = commands.getstatusoutput( "otool -L %s | grep libedit" % _rl.file )
File "/opt/local/Library/Frameworks/Python.framework/Versions/2.6/lib/python2.6/commands.py", line 56, in getstatusoutput
text = pipe.read()
IOError: [Errno 4] Interrupted system call
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=248

From koverholt on 2010-07-10T22:11:26Z
Something in the recent commits has fixed this, it now works on OS X and IPython starts fine in Spyder. Thanks for the hard work!

From pierre.raybaut on 2010-07-12T01:24:29Z
Perfect!
I think this commit has fixed your problem (Matplotlib's patch was applied systematically): https://code.google.com/p/spyderlib/source/detail?r=5e61a29085ef378db1063cf130543f5cf2027d4c
Status: Fixed


Update chain.json

Add RPC & API endpoint

Please change the name of your PR to an accurate description of this PR.
Please do not add your end points to the middle of the list - please add them at the end.


feat: refactor for bun, viem, and other things

will it be required for people using this to have bun installed?

No, you can use other package managers :) But bun is pretty powerful

(I'll add a note in the readme)


Add an integration test for current error behavior:

Description
No new functionality.

Adds an integration test to capture our current output when a script fails

Testing Instructions
Run new integration test

Oh yeah, nevermind, don't need this then.


Possible to only load appropriate .scss files?

Is it possible to only load the appropriate .scss files? For some reason even though a react component isn't being used on a page the .scss file is still being included in my css.
I am currently using ExtractTextPlugin since I also want sourcemaps to work.

Are you require-ing the React component and not using it?

I don't think so. The component should only be pulled in when a certain page is hit.
So the question is. Is this normal or I am doing something wrong? Should the .scss only be loaded for the page you are on?

Can you post some of your code? Otherwise it can't be established if you're doing something wrong. Is the code in a public repository?

https://github.com/tkiethanom/splice/tree/sp2_front_end?files=1
Thanks for the help

It is a large repository. Which file should not be included and in which files is it referenced? What command should I run to test it?

In the /front_end directory there are some directions in the readme. Basically npm install and gulp serve.

So for example if I put require('../../styles/accounts/accounts.scss'); in /src/pages/AccountsViewPage.js, The .scss still get loaded even if I'm on the home page.

Webpack puts all required files into one big js file by default. If you want to load code (like styles) on demand, you need to create a code split point by using an async require (will be System.import in Webpack 2).
This issue is not a sass-loader thing, though.


Support for ng-disabled?

Is it me who's not understanding or have you not implemented ng-disabled support? Because there is a disabled class but there doesn't seem to be a way of actually using it.

No I have not, due to time scarcity. As I said it's best to fork off to implement the nice-to-haves. The core datepicker logic issues I will attend to.


Code Inspection: Tslint on atomist/a260p86nh/typescript-version/master

arrow-parens

app/components/codeSubmission/codeDisplay.tsx:27: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/codeDisplay.tsx:60: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/codeDisplay.tsx:105: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/highlightCode.ts:25: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/highlightCode.ts:34: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/highlightCode.ts:38: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/highlightCode.ts:42: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/ParserInput.tsx:40: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/codeSubmission/ParserInput.tsx:54: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/jsonDisplay/tree.tsx:21: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/jsonDisplay/TreeChoice.tsx:73: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/TreeParseGUI.tsx:41: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/TreeParseGUI.tsx:42: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/TreeParseGUI.tsx:68: (error) Parentheses are prohibited around the parameter in this single parameter arrow function
app/components/TreeParseGUI.tsx:73: (error) Parentheses are prohibited around the parameter in this single parameter arrow function

interface-over-type-literal

app/TreeParseGUIState.ts:4: (error) Use an interface instead of a type literal.

no-console

app/components/codeSubmission/codeDisplay.tsx:21: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/codeDisplay.tsx:75: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/codeDisplay.tsx:78: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/codeDisplay.tsx:82: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/codeDisplay.tsx:86: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/codeDisplay.tsx:91: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/highlightCode.ts:20: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/highlightCode.ts:51: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/highlightCode.ts:52: (warn) Calls to 'console.log' are not allowed.
app/components/codeSubmission/ParserInput.tsx:41: (warn) Calls to 'console.log' are not allowed.
app/components/jsonDisplay/tree.tsx:21: (warn) Calls to 'console.log' are not allowed.
app/components/TalkOutLoud.tsx:9: (warn) Calls to 'console.log' are not allowed.
app/components/TreeParseGUI.tsx:43: (warn) Calls to 'console.log' are not allowed.
app/components/TreeParseGUI.tsx:44: (warn) Calls to 'console.log' are not allowed.
app/components/TreeParseGUI.tsx:67: (warn) Calls to 'console.log' are not allowed.
app/components/TreeParseGUI.tsx:81: (warn) Calls to 'console.log' are not allowed.
app/components/TreeParseGUI.tsx:102: (warn) Calls to 'console.log' are not allowed.
server.ts:24: (warn) Calls to 'console.log' are not allowed.
server.ts:43: (warn) Calls to 'console.log' are not allowed.
server.ts:63: (warn) Calls to 'console.log' are not allowed.
server.ts:74: (warn) Calls to 'console.log' are not allowed.
server.ts:79: (warn) Calls to 'console.error' are not allowed.

no-floating-promises

app/components/codeSubmission/ParserInput.tsx:25: (error) Promises must be handled appropriately
app/components/codeSubmission/ParserInput.tsx:29: (error) Promises must be handled appropriately
app/components/TreeParseGUI.tsx:40: (error) Promises must be handled appropriately
app/components/TreeParseGUI.tsx:69: (error) Promises must be handled appropriately

no-implicit-dependencies

app/TreeParseGUIState.ts:1: (error) Module '@atomist/tree-path' is not listed as dependency in package.json
server.ts:9: (error) Module '@atomist/tree-path' is not listed as dependency in package.json
server.ts:11: (error) Module 'json-stringify-safe' is not listed as dependency in package.json

no-import-side-effect

app/components/codeSubmission/codeDisplay.tsx:2: (error) import with explicit side-effect
app/components/codeSubmission/codeDisplay.tsx:3: (error) import with explicit side-effect
app/components/codeSubmission/codeDisplay.tsx:4: (error) import with explicit side-effect
app/components/codeSubmission/codeDisplay.tsx:5: (error) import with explicit side-effect
app/components/codeSubmission/codeDisplay.tsx:6: (error) import with explicit side-effect

no-null-keyword

app/components/codeSubmission/codeDisplay.tsx:50: (warn) Use 'undefined' instead of 'null'
app/components/codeSubmission/codeDisplay.tsx:88: (warn) Use 'undefined' instead of 'null'
app/components/codeSubmission/codeDisplay.tsx:97: (warn) Use 'undefined' instead of 'null'
app/components/codeSubmission/codeDisplay.tsx:105: (warn) Use 'undefined' instead of 'null'
app/components/codeSubmission/highlightCode.ts:44: (warn) Use 'undefined' instead of 'null'

only-arrow-functions

server.ts:23: (error) non-arrow functions are forbidden

typedef

app/components/codeSubmission/codeDisplay.tsx:19: (warn) expected parameter: 'props' to have a typedef
app/components/codeSubmission/codeDisplay.tsx:27: (warn) expected member-variable-declaration: 'newCode' to have a typedef
app/components/codeSubmission/codeDisplay.tsx:32: (warn) expected call-signature: 'hasRange' to have a typedef
app/components/codeSubmission/codeDisplay.tsx:32: (warn) expected parameter: 'ranges' to have a typedef
app/components/codeSubmission/codeDisplay.tsx:38: (warn) expected call-signature: 'render' to have a typedef
app/components/codeSubmission/highlightCode.ts:15: (warn) expected call-signature: 'highlightFromAst' to have a typedef
app/components/codeSubmission/ParserInput.tsx:20: (warn) expected parameter: 'props' to have a typedef
app/components/codeSubmission/ParserInput.tsx:28: (warn) expected member-variable-declaration: 'event' to have a typedef
app/components/codeSubmission/ParserInput.tsx:28: (warn) expected member-variable-declaration: 'parserChoice' to have a typedef
app/components/codeSubmission/ParserInput.tsx:40: (warn) expected member-variable-declaration: 'event' to have a typedef
app/components/codeSubmission/ParserInput.tsx:45: (warn) expected call-signature: 'radioInputs' to have a typedef
app/components/codeSubmission/ParserInput.tsx:45: (warn) expected parameter: 'name' to have a typedef
app/components/codeSubmission/ParserInput.tsx:45: (warn) expected parameter: 'valueAndLabelses' to have a typedef
app/components/codeSubmission/ParserInput.tsx:57: (warn) expected call-signature: 'render' to have a typedef
app/components/ErrorDisplay.tsx:4: (warn) expected call-signature: 'ErrorDisplay' to have a typedef
app/components/jsonDisplay/tree.tsx:6: (warn) expected parameter: 'props' to have a typedef
app/components/jsonDisplay/tree.tsx:14: (warn) expected call-signature: 'render' to have a typedef
app/components/jsonDisplay/TreeChoice.tsx:12: (warn) expected call-signature: 'effectiveTreeChoice' to have a typedef
app/components/jsonDisplay/TreeChoice.tsx:47: (warn) expected call-signature: 'TreeChoice' to have a typedef
app/components/jsonDisplay/TreeChoice.tsx:69: (warn) expected call-signature: 'disableUnavailable' to have a typedef
app/components/jsonDisplay/TreeChoice.tsx:76: (warn) expected call-signature: 'radioInputs' to have a typedef
app/components/jsonDisplay/TreeChoice.tsx:76: (warn) expected parameter: 'name' to have a typedef
app/components/jsonDisplay/TreeChoice.tsx:76: (warn) expected parameter: 'valueAndLabelses' to have a typedef
app/components/PathExpressionInput.tsx:4: (warn) expected call-signature: 'PathExpressionInput' to have a typedef
app/components/TalkOutLoud.tsx:7: (warn) expected call-signature: 'TalkOutLoud' to have a typedef
app/components/TreeParseGUI.tsx:19: (warn) expected parameter: 'props' to have a typedef
app/components/TreeParseGUI.tsx:39: (warn) expected call-signature: 'componentDidMount' to have a typedef
app/components/TreeParseGUI.tsx:51: (warn) expected member-variable-declaration: 'updateTree' to have a typedef
app/components/TreeParseGUI.tsx:79: (warn) expected member-variable-declaration: 'words' to have a typedef
app/components/TreeParseGUI.tsx:79: (warn) expected member-variable-declaration: 'ranges' to have a typedef
app/components/TreeParseGUI.tsx:84: (warn) expected member-variable-declaration: 'styles' to have a typedef
app/components/TreeParseGUI.tsx:96: (warn) expected call-signature: 'render' to have a typedef
server.ts:23: (warn) expected call-signature to have a typedef
server.ts:23: (warn) expected parameter: 'exception' to have a typedef
server.ts:104: (warn) expected call-signature: 'condenseSingleChild' to have a typedef

[atomist:code-inspection:atomist/a260p86nh/typescript-version/master=@atomist/atomist-sdm]

Issue closed because branch atomist/a260p86nh/typescript-version/master was deleted.


[DBZ-646] io.debezium.text.ParsingException for TokuDB table

Current MySQLParser has problems with TokuDB compression parameter.
This PR solves this issue.

@maver1ck Thanks for contribution! Could you please add an example of CREATE TABLE (and ALTER if releavant) DDL statements into io.debezium.connector.mysql.MySqlDdlParserTest?

Done :)

@maver1ck Thanks!
@gunnarmorling LGTM

Checking build errors.

Rebased and applied. Thanks, @maver1ck!


Ms events

What does the code in this PR do / what does it improve?

This  code provides the sum of all cs2 in the drift length. With this you can evaluate the CES of MS events.
it gives peaks related to each event and correction for MS studies.

Can you briefly describe how it works?

Assumes that the main S1 is the only physical one in the event -peak level
Calculates all s2 drift length from that main s1-peak level
Calculate correction to get cs2 in the max drift length-peak level
Sum up the cs2.-event level

Can you give a minimal working example (or illustrate with a figure)?
In the wiki note https://xe1t-wiki.lngs.infn.it/doku.php?id=weiss:analysis:ms_plugin

Coverage decreased (-1.8%) to 91.426% when pulling eb63cb7efabd727e522f685646edaaec89e75bd7 on MSevents into 8689fb2d429320b5198e3ce4953cabccaec11415 on master.

Hi @michaweiss89 , when you are able to get back to this PR. Could you follow the new plugin structure from https://github.com/XENONnT/straxen/pull/1094

Thanks again Micha and Henning!


Remove an unnecessary null pointer check

An extra null pointer check is not needed in the destructor for the class “WebSocketData”.

It literally makes no difference either way. It's nice to see the intended behavior even if it's technically redundant (before optimization).

How do you think about corresponding software design options?

Adjusted class hierarchy (and fine-tuning of involved member variables)
Application of a smart pointer

If anything std::unique_ptr, but I'm not sure how deep that change would be. It's a pretty pointless thing to care for given the many bugs, issues and features with priority.


Add filtering on preset query param to user scratch list

Resolves #1299
I matched this to the way query params are handled on the ScratchViewSet class. Tested locally on mock data and works as expected!

Thanks for this! Looks good to me - just black failed due to the type of string quotes used, if you don't mind fixing that

@ethteck Done!


Inconsistency in documentation/implementation for OpenAiRequestHandler#apiResponse

Hi,
I'm currently working on adding support for Google's LLMs, but I came across an inconsistency between the implementation of OpenAiRequestHandler#apiResponse:
The Javadoc for this method has the following throws clauses:
/**
 * ...
 * @throws IOException              if an I/O error occurs, or if the response is not received within 60 seconds
 * ...
 * @throws TimeoutException         if waiting for the CompletableFuture times out
 */

The implementation leads me to believe that an IOException is thrown and a TimeoutException is actually never thrown in practice:
https://github.com/jonathan-m-phillips/ASHE_Automated-Software-Hardening-for-Entrypoints/blob/d7c703e1a20d5a7a3308b11195d211fc6693b04b/src/main/java/edu/njit/jerse/ashe/llm/openai/OpenAiRequestHandler.java#L125-L127
Is this intended? If not, should either the documentation or the implementation be updated? I am happy to make the change, if needed.

Hello James,
Great catch! This was an accident and should be changed. I think it is most reasonable to log the error message and then throw either a new TimeoutException with the same error message, or to throw the one caught.
Example:
String errorMessage = "your message here";
LOGGER.fatal(errorMessage);
throw new TimeoutException(errorMessage, e);
Additionally, the documentation should be changed.
Thanks,
Jonathan


cmake findpython alternation

Hi @igor-krechetov
There is no difference in function.
but cmake can't find python3 interpreter in our build system
(to be exact, Python_EXECUTABLE isn't specified and thus it uses host python3)
Platform information:

yocto: v3.1
cmake: v3.20.2

find_python is desirable, if not essential.
https://stackoverflow.com/questions/72693284/findpython-vs-find-packagepython
https://cmake.org/cmake/help/latest/module/FindPython.html
Also, can you expand a bit on what I commented about before and after?
Thanks!

Hello @yoowonsuk ,
You are right. include(FindPython3) was not the correct way to add python module and your proposed option is better.
Unfortunately I did some changed on the main branch which messed up this pull request's commits. Can you please rebase to master and update PR so that it contains only 1 commit? Or I can just cherry-pick and push your fix manually without a PR.