Invalid Brixton.SR2 pom deployed to https://repo.spring.io/release

See: https://repo.spring.io/release/org/springframework/cloud/spring-cloud-starter-parent/Brixton.SR2/spring-cloud-starter-parent-Brixton.SR2.pom it contains dependency to Brixton.BUILD-SNAPSHOT.
repo1 and repo2 at maven.org have valid poms. 4 days after deployment so probably it will not fix automatically during sync. Probably this commit https://github.com/spring-cloud/spring-cloud-starters/commit/5b3159a5f01491956007802c835d7d5bcf4a0a48 was accidentally deployed.

Fixed.


Gradle should treat the _JAVA_OPTIONS environment variable as an implicit task input

Current Behavior
Currently, gradle has a bunch of environment/system settings that it automatically considers to be task inputs. For example, the test task automatically includes the following (among many others):
Appending input value fingerprint for 'javaVersion' to build cache key: a40a171a9de3ed0d81e29d9af4cc27ef
Appending input value fingerprint for 'jvmArgs' to build cache key: 8222d82255460164427051d7537fa305

This is completely reasonable, as changing the JVM version or JVM arguments can impact how code is run, and affect the output of the tests.
However, gradle does not seem to treat the _JAVA_OPTIONS environment variable in the same way, but for consistency, it should - this environment variable is read by the JVM directly and can be used update the JVM settings. This can result in dramatically different behaviour during test (and maybe other) tasks, and should be treated as a task input.
Expected Behavior
Changing the value of the _JAVA_OPTIONS environment variable should cause test (and possibly other) tasks to re-run rather than re-using previously cached results.
Context (optional)
In our case, we changed our _JAVA_OPTIONS environment variable in CI to include a new java agent (via the -javaagent argument). Although this should have caused tests to fail, gradle re-used cached test output from a previous run and so the CI run passed. This later resulted in downstream breakage when the test was next re-run.
Steps to Reproduce
I can try to create a minimal example, but our original example has quite a bit of proprietary code so I haven't yet. If it would be useful (i.e. if this ticket isn't immediately closed as WONTFIX) I'm happy to put in the effort to create a reproducible example.
Gradle version
7.6.1
Build scan URL (optional)
No response
Your Environment (optional)
No response

JAVA_TOOL_OPTIONS is the public API equivalent: https://bugs.openjdk.org/browse/JDK-4971166
Another view of this is that Gradle should explicitly strip out this environment variable (and others like it) because it's a source for surprises.

JAVA_TOOL_OPTIONS is the public API equivalent: https://bugs.openjdk.org/browse/JDK-4971166

Fair enough, I'd be fine with that env var being treated as a task input instead of _JAVA_OPTIONS. I think fundamentally that doesn't alter the bug much.

Another view of this is that Gradle should explicitly strip out this environment variable (and others like it) because it's a source for surprises.

I'm not sure this is desirable. The env var exists for a reason and serves a useful function. And besides, Gradle stripping it out would be a much bigger breaking change.

Thank you for your interest in Gradle!
This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

Note: You can workaround this, by adding that env variable as an input manually, for example:
tasks.named<Test>("test") {
    inputs.property("javaOptionsEnvVariable", project.providers.environmentVariable("_JAVA_OPTIONS"))
}

Yes, it can be worked around, and we have done so. Still, I feel this should be fixed in Gradle itself.

@staktrace Instead of relying on _JAVA_OPTIONS to pass the java agent to tests, would it be possible for you to set it for just test tasks?
That would mean you would do something like:
test {
   inputs.files file("/path/to/javaagent.jar")
   jvmArgs "-javaagent:/path/to/javaagent.jar"
}

IIUC, the way you're using _JAVA_OPTIONS now will impact things other than tests: the Gradle daemon, Gradle workers (compilation, checkstyle, etc) and JavaExec.

IIUC, the way you're using _JAVA_OPTIONS now will impact things other than tests

This is the desired outcome. The java agent is an instrumentation agent and we want it to run in all cases, not just during test tasks. So to answer your question, no, just setting the agent on the test task wouldn't be appropriate for our use case.

This is a valid report.
The issue is in the backlog of the team, but this area of Gradle is currently not a focus one, so it might take a while before a fix is made.
The current workaround is to add the env variable as input to tasks manually.


ccAdd orders queue and associated configuration

This PR adds a new Azure Storage queue for processing orders, and updates the website configuration to include the storage account and queue information.

Should this be capaitalized


Change font

I want to change the font in pynvim.
Can I change it?
pynvim uses the hardcoded font and font size (monospace 13).

+1

+1


Prefill on HTTP (and not only HTTPS)

Feedback reported by a user on Chrome Webstore:
"Great extension ! Is it possible to make the prefill system work on http and not only https ? useful for local dev. Thank you !"

We have double-checked and the extension works fine on localhost:8080, for example when running any of the adyen-examples locally


Update deprecations

R17 has deprecated queue/0 as a type, in favor of queue:queue/0 or queue:queue/1.  This PR updates those types to silence compile-time warnings in R17.
Dialyzer did not like the spec contract on do_request/3 as handle_cast tried to pass in the 'undefined' atom as a pid().  Updated the spec to permit undefined as a value.

Sorry for taking forever to get to this PR. I'm closing this since #53 solves this in a backward compatible manner.


Errors on fresh install

On a fresh install throws error when trying to execute any command:
Traceback (most recent call last):   File "/home/oscrustacean/.local/bin/gext", line 8, in <module>     sys.exit(run())              ^^^^^   File "/home/oscrustacean/.local/lib/python3.11/site-packages/gnome_extensions_cli/cli.py", line 78, in run     subparsers.add_parser("update", aliases=["u"], help="update extensions")   File "/usr/lib64/python3.11/argparse.py", line 1188, in add_parser     raise ArgumentError(argparse.ArgumentError: argument {list,ls,install,i,uninstall,u,enable,disable,search,show}: conflicting subparser alias: u
I got this error to go away just by removing the "u" alias on line 78 of cli.py since it is conflicting with something else.
After fixing that, the program throws the error
File "/home/oscrustacean/.local/bin/gext", line 8, in <module>     sys.exit(run())              ^^^^^   File "/home/oscrustacean/.local/lib/python3.11/site-packages/gnome_extensions_cli/cli.py", line 78, in run     subparsers.add_parser("update", aliases=["u"], help="update extensions")   File "/usr/lib64/python3.11/argparse.py", line 1188, in add_parser     raise ArgumentError( argparse.ArgumentError: argument {list,ls,install,i,uninstall,u,enable,disable,search,show}: conflicting subparser alias: u [oscrustacean@oscrustacean-pc ~]$ gext list Traceback (most recent call last):   File "/home/oscrustacean/.local/bin/gext", line 8, in <module>     sys.exit(run())              ^^^^^   File "/home/oscrustacean/.local/lib/python3.11/site-packages/gnome_extensions_cli/cli.py", line 81, in run     subparsers.add_parser("disable", aliases=[], help="disable extensions")   File "/usr/lib64/python3.11/argparse.py", line 1185, in add_parser     raise ArgumentError(self, _('conflicting subparser: %s') % name) argparse.ArgumentError: argument {list,ls,install,i,uninstall,u,enable,disable,search,show,update}: conflicting subparser: disable
I fixed this simply by commenting out lines 80-83 of cli.py. Is there a reason there are two disable.configure entries?

Thanks for noticing that.
Very strange that I did not get any error ...
I did not use your PR as there were 2 problems,

'u' used twice
'disable' was also declared twice


feat: confirm checkbox for sending LP tokens

Add confirm checkbox when sending LP tokens.

Just adding one more validation for back buttons

Just adding one more validation for back buttons


closed #28

i have been working on all these changes all morning. PR not necessary .  maybe the script to move the photos could be a new seperate PR


Fixes

Just small things, no new features :

Simplify ValidationMixin to be all CP from attributeValidation
Fix translations

COME ON CIRCLECI 🔪


Dask Arrow DataFrame

Dask dataframe today supports a few different in-memory compute systems, primarily Pandas and RAPIDS/cudf, but also geopandas, spatialpandas, etc.. with subprojects.
The folks at Arrow are planning a compute backend as well (or there are already compute backends based on arrow memory) so we should probably consider how to support these in the future.
This issue is being pulled from https://github.com/dask/dask/issues/7933#issuecomment-902656163 from @wesm in another thread. I'll reproduce the content below for convenience
Wes' comment
Hopefully this isn't too OT, but I wanted to make Dask folks aware that we have an adjacent effort/discussion under way in Apache Arrow to develop a language-independent serialized expression format connecting user SDKs (e.g. things like Ibis or even dask.dataframe potentially) with Arrow-based/Arrow-compatible computing engines:
https://lists.apache.org/thread.html/r90c1e6ba1c7b27a960df3f27dc2c1aeb542f07bb7af72c17138667f0%40<dev.arrow.apache.org>
The idea is to provide a common ground consisting a standard lower-level operators rather than each engine having their own slightly idiosyncratic front end (e.g. using a certain SQL dialect, or something else) — there would be the presumption of using Arrow's schemas / type metadata to describe input/output types of operations.
In the same way that Dask uses pandas as a dataframe computing engine, it would be interesting to see if this High Level Expression effort could lead to a world of pluggable single-node engines for Dask to orchestrate (e.g. using one of the various Arrow-based engines — Rust, C++ — in development or even an small-footprint embeddable analytic SQL engine like DuckDB — which can now input/output Arrow easily). One might imagine that dask.dataframe in the future could not use pandas at all and permit use of alternative (or even multiple) backends to execute various tasks (and if useful, Arrow could be used as a serialization middleware). EDIT: I would also add that, given the existence of polars exists now, what would it take for Dask to be able to target it with dask.dataframe instead of only pandas?

Thanks for jumping in @wesm .  This seems on-topic to me.
We discussed this over video, but I thought I'd copy that conversation here as well for the general public.  Once there is a Python-accessible way to use those kernels (presumably through something like Ibis) then I think that having a dask.arrow module or dask-arrow project that looked a lot like dask.dataframe or dask_cudf would make a lot of sense.

One might imagine that dask.dataframe in the future could not use pandas at all and permit use of alternative (or even multiple) backends to execute various tasks

Yes, this is more or less our current state with Pandas, GeoPandas, RAPIDS.  The backstory here is that during the push on RAPIDS there was an effort in dask.dataframe to make it more backend agnostic.
However, many of the user-facing dask.dataframe functions target the pandas API.  For example, our merge or join operations heavily copy and rely on the semantics of pandas/cudf's merge/join.  However, all of the infrastructural operations like elemwise, reduction, window, and so on are agnostic to the thing on which they operate.  In general it is not hard for us to build new dask-foo projects.  It's mostly an application of API skin onto existing infrastructure.

EDIT: I would also add that, given the existence of polars exists now, what would it take for Dask to be able to target it with dask.dataframe instead of only pandas?

Ah, I wasn't aware of polars.  Yes, a dask-polars project seems in scope.  At this point I think this just raises questions of prioritization.

I suppose rather than dask-arrow I should probably say dask-ibis or some other thing-that-uses-arrow-memory, assuming that arrow itself doesn't want to grow the scope of maintaining a pandas-like compute layer.

Ah, I wasn't aware of polars. Yes, a dask-polars project seems in scope. At this point I think this just raises questions of prioritization.

I suppose rather than dask-arrow I should probably say dask-ibis or some other thing-that-uses-arrow-memory, assuming that arrow itself doesn't want to grow the scope of maintaining a pandas-like compute layer.

Polars is a query engine on top Apache Arrow, so that would kill two birds in one stone. :)
I don't know if polars expression could also be beneficial to the earlier discussion. I can imagine that query plans/ expressions trees can be transpiled.

One of the goals of the "Arrow IR" we are discussing in the project now is to provide for a language-independent middleware to reduce the need to build custom bridges between front ends (including Dask) and backends, e.g. schematically something like

(here keep in mind that Gandiva isn't actually a query engine, but it can compile array expressions with LLVM, so this shows that the IR can be used to interact with systems having only limited functionality)

As this is a rather high-breadth issue and has sat idle for several months, I'm going to close this as stale. Feel free to reopen or open a more focused issue if the discussion should continue.


How to change Server address

I have installed it on my server and it shows the log

Server address: http://<IP_ADDRESS>:4000/

But I want to change it to public address, Can you help me how i can do this.

Just publish it on GitHub using GitHub Pages: https://pages.github.com/

Yes, But I want to run it on my own server as we want our documents private. now on my server its ask to run on <IP_ADDRESS>

You'll need a host for that; maybe Netlify or similar.
It's more of a general Jekyll question though (maybe check https://talk.jekyllrb.com/ as well for hosting options).


Looking forward to get involved and contribute to the community 🎉

First Name
Rishabh
Last Name
Rathore
Discord Username (if applicable)
Rishabh #7588
Let us understand your motive.
I am interested in learning more with like-minded people and contributing to open source

Hey @rishabhrathore055 👋🏻
Thanks for requesting an invite! Welcome to SidHacks Community 🎉
Before going ahead, I would want you to complete the below To-Do list.
Your To-Do List ✔

Accept the invitation sent to you via mail.
Change the appearance of this organization to "Public" from the people list here.
Join our Discord Server here.

Accept the Rules from #📓〡rules channel.
Introduce yourself to our community in 👋〡introduction channel.

Feel free to share your excitement on socials with #SidHacksCommunity. You can also tag me @siddharth_hacks.

Close this issue once you complete all the above points.

Looking forward to interacting with you in our community! Welcome once again! 🤓


Substantially more parameters than OpenCLIP, SWAG and Timm's ViT models.

Hello,
Many thanks for sharing your interesting work. I noticed that the projection head of your models is substantially bigger than SWAG (Singh et al., CVPR 2022), OpenCLIP models and Timm's implementation of ViT that is used in recall@k surrogate (Patel et al., CVPR 2022). I ran a quick parameter counter for these models following the RS@k implementation, that is, with a layer norm and linear projection. Here are the counts:
ViT-B/32 Timm: 87850496
ViT-B/32 CLIP: 87849728
ViT-B/32 UNICOM: 117118464
ViT-B/16 Timm: 86193920
ViT-B/16 CLIP: 86193152
ViT-B/16 UNICOM: 202363136
ViT-B/16 SWAG: 86193920

It is clear that the UNICOM model has substantially higher number of parameters than the baselines used for the comparison. With this in mind, are the comparisons fair at all?

Thank you for the prompt reply. Looking forward to new results.

https://drive.google.com/drive/folders/1qjHwo2uYlVmJ6RXKaan5tymZkIRmBePR?usp=drive_link

https://drive.google.com/drive/folders/1qjHwo2uYlVmJ6RXKaan5tymZkIRmBePR?usp=drive_link

This is the performance of the model we trained using the same ViT architecture as CLIP.
Results

cub
car
sop
inshop
inat

unicom
83.7
95.9
70.0
72.8
64.6

new
83.4
95.5
71.0
75.0
64.9

Model
This is the model file:
https://drive.google.com/file/d/1dSrWAmoPqr8d9oB1wggnZfgHnBdre2wa/view?usp=drive_link
Usage
You can use it like this:
import clip
model, transform = clip.load("ViT-B/32", "cpu")
model = model.visual
state_dict = torch.load("ViT-B-32.pt", "cpu")
model.load_state_dict(state_dict, strict=True)

This is the performance of the model we trained using the same ViT architecture as CLIP.
Results
cub	car	sop	inshop	inat
unicom	83.7	95.9	70.0	72.8	64.6
new	83.4	95.5	71.0	75.0	64.9
Model
This is the model file: https://drive.google.com/file/d/1dSrWAmoPqr8d9oB1wggnZfgHnBdre2wa/view?usp=drive_link
Usage
You can use it like this:
import clip
model, transform = clip.load("ViT-B/32", "cpu")
model = model.visual
state_dict = torch.load("ViT-B-32.pt", "cpu")
model.load_state_dict(state_dict, strict=True)

HI, the model file has no permission to download, can you open the permission? Thank you very much.

This is the performance of the model we trained using the same ViT architecture as CLIP.
Results
cub	car	sop	inshop	inat
unicom	83.7	95.9	70.0	72.8	64.6
new	83.4	95.5	71.0	75.0	64.9
Model
This is the model file: https://drive.google.com/file/d/1dSrWAmoPqr8d9oB1wggnZfgHnBdre2wa/view?usp=drive_link
Usage
You can use it like this:
import clip
model, transform = clip.load("ViT-B/32", "cpu")
model = model.visual
state_dict = torch.load("ViT-B-32.pt", "cpu")
model.load_state_dict(state_dict, strict=True)

HI, the model file has no permission to download, can you open the permission? Thank you very much.

we have updated it


unittest.main() doesn't work

Background:
A typical python unit test code file looks like
import unittest

class MyTest(unittest.TestCase):
  def test_xyz(self):
    ...

if __name__ == '__main__':
  unittest.main()

unittest.main by default runs all the test cases in module __main__.
pex executes the entry point via runpy.run_module(module_name, run_name='__main__'): https://github.com/pantsbuild/pex/blob/a253efd4a4d9f33f5ac7f6f397902f62fb1e517f/pex/pex.py#L421
This sets __name__ to be __main__ in the entry point's execution context, and therefore the if check in the example code above passes. However, when unittest.main() tries to load the __main__ module, what it loads is the __main__.py file generated by pex, not the entry point.
A simple fix is to specify alter_sys=True when invoking runpy.run_module, which will set sys.modules[__name__] to the entry point code.

The same root cause (wrong sys.modules entry) prevents pkg_resources.resource_* from working in the entry point when using __name__ as the argument.

This was fixed some time ago and now works:
:; cat test.py
import unittest

class MyTest(unittest.TestCase):
  def test_xyz(self):
    assert False, "Proving test ran (and failed)."

if __name__ == '__main__':
  unittest.main()

:; pex -V
2.16.0
:; pex --exe test.py -otest.pex
:; ./test.pex
F
======================================================================
FAIL: test_xyz (__main__.MyTest.test_xyz)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/jsirois/.pex/unzipped_pexes/a029f272ccacc2894c95f032ab2e58b930897223/__pex_executable__.py", line 5, in test_xyz
    assert False, "Proving test ran (and failed)."
           ^^^^^
AssertionError: Proving test ran (and failed).

----------------------------------------------------------------------
Ran 1 test in 0.000s

FAILED (failures=1)


General Issue: derive_param_tte appears to be missing a set up for AVALU

Background Information
derive_param_tte appears to be missing a setup for AVALU, which can be different depending on the domain data.
Definition of Done
No response

Could you elaborate a bit more @oreillb1? derive_param_tte() returns the time to event in days. Are you looking for functionality to output the result in other units, e.g. "weeks"? Or is this just about setting the AVALU variable? In that case you can use the set_values_to parameter, e.g. set_values_to = vars(AVALU = "DAYS").

derive_param_tte() derives ADT or ADTM only. AVAL (and AVALU) is derived in a separate step for all parameters together:
adtte <- derive_vars_duration(
  adtte,
  new_var = AVAL,
  new_var_unit = AVALU,
  start_date = STARTDT,
  end_date = ADT
)

You can specify the new_var_unit argument to add a variable for the unit.

AVALU is in our ADaM specifications for ADTTE so it will always be missing from the dataset unless deliberately included in derive_vars_duration. Could AVALU be created null by default in ADTTE and then it would be up to the programmer to define?

AVALU is a Roche specific variable. Thus I would not add it to the general admiral vignette. If we provide a template script for ADTTE in admiralroche, it will create AVALU.

Many thanks for the clarification


feat: add Oracle contracts

Codecov Report

Merging #281 (e902103) into develop (ef970de) will increase coverage by 17.79%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##           develop     #281       +/-   ##
============================================
+ Coverage    71.73%   89.52%   +17.79%
============================================
  Files           68       33       -35
  Lines         2257     1079     -1178
  Branches       335      150      -185
============================================
- Hits          1619      966      -653
+ Misses         638      113      -525

Flag
Coverage Δ

batch-submitter
?

contracts
89.52% <ø> (ø)

core-utils
?

data-transport-layer
?

message-relayer
?

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

Impacted Files
Coverage Δ

packages/data-transport-layer/src/utils/common.ts

packages/core-utils/src/l2context.ts

packages/batch-submitter/src/index.ts

packages/core-utils/src/common/test-utils.ts

packages/core-utils/src/coders/index.ts

...kages/data-transport-layer/src/utils/validation.ts

...ubmitter/src/batch-submitter/tx-batch-submitter.ts

.../batch-submitter/src/transaction-chain-contract.ts

packages/core-utils/src/alias.ts

packages/core-utils/src/watcher.ts

... and 25 more

Continue to review full report at Codecov.

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

changes to FluxAggregators logic level-

timedOut logic - changed to only timeout a round if the answer wasn't reached because of lower number of submissions ( L948 checks if round answer wasn't reached)
payment not compulsion for data submissions when paymentAmount is set - a var voluntarySubmissionsAllowed added to allow/block this
trigger updateAvailableFunds to some methods, since erc20 boba transfer to aggregator might not trigger updateAvailableFunds right away


Refactoring intermittent for Python projects in VS2022

This issue has been moved from a ticket on Developer Community.

Refactoring command (. Refactor.Rename Ctrl+R+R) in Python project is intermittent, sometimes it works properly and sometimes it invokes and immediately exits by saying that it is not available - without allowing to enter new name for the variable of class. I tried same on VS2019 using same code, there it works properly.

Original Comments
Feedback Bot on 11/15/2021, 00:17 AM:
We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.

Original Solutions
(no solutions)

Can you please provide a code snippet that fails to refactor for you?

Closing old issue. If this is still a problem, please reopen with the information requested. thanks


init application view

Description:
init application view
Issues:

Issue #<TICKET_ID>

UI changes
<Please, provide Screenshots or Figma links>
Checklist:

[ ] the pull request name complies with Conventional Commits
[ ] the pull request name starts with fix(<scope>):, feat(<scope>):, feature(<scope>):, chore(<scope>):, hotfix(<scope>): or e2e(<scope>):. If contains breaking changes then the pull request name must start with fix(<scope>)!:, feat(<scope>)!:, feature(<scope>)!:, chore(<scope>)!:, hotfix(<scope>)!: or e2e(<scope>)!: where <scope> is name of affected project: chat, chat-e2e, overlay, shared, sandbox-overlay, etc.
[ ] the pull request name ends with (Issue #<TICKET_ID>) (comma-separated list of issues)
[ ] I confirm that do not share any confidential information like API keys or any other secrets and private URLs

Hey there and thank you for opening this pull request! 👋🏼
We require pull request titles to follow the Conventional Commits specification and it looks like your proposed title needs to be adjusted.
Details:
No release type found in pull request title "init application view". Add a prefix to indicate what kind of release this pull request corresponds to. For reference, see https://www.conventionalcommits.org/

Available types:
 - fix
 - hotfix
 - feat
 - feature
 - chore


Customizable Fonts Not Working

Got multiple custom fonts and it doesn't seem to be working. I've tried all the different types of names too.

https://github.com/l2-/template-plugin/issues/32
Do my comments in this thread help you? I think it is the same issue.


Allow zwitterion to be installed and used at the top level

Right now zwitterion needs to have plugin-typescript in the server context that it creates because of the way systemjs-builder is configured and gets a reference to the plugin. Figure out how to change that so it doesn't matter where the node_modules folder is that contains plugin-typescript

Right now it's looking like zwitterion needs to be installed at the root directory that you want it to run at, because it expects typescript and plugin-typescript to be located in the node_modules directory where it is running. I'm not sure it is worth fixing this at the moment.


TableHeader: prop type colGroups is invalid

Hi :),
I am getting a warning:
Warning: Failed prop type: TableHeader: prop type colGroups is invalid; it must be a function, usually from React.PropTypes.
in TableHeader (created by BootstrapTable)
with even the simple code as:
render() {
    return (
        <BootstrapTable data={[{id:1}]} >
            <TableHeaderColumn isKey={true} dataField='id'>ID</TableHeaderColumn>
        </BootstrapTable>
    )
}

Using 15.4.1 react and latest version of react boostrap table

I'm seeing this same behavior with React 15.3.2

thanks for issue report, I think I made a little mistake on v2.8.0, I'll fix it soon.

A changelog would be nice for these latest versions as well. Thanks for all your hard work @AllenFang!

@jflayhart, I'll add the changelog today, I'll figure out what happen to this warning. BTW, this warning  was happened before?

I am not certain of @Trudko issue, but seems that this only happened when I updated to your plugin to 2.8.0

@jflayhart, prop type `colGroups` is invalid is a known issue, but I dont see the warning you mentioned above, could you please show me your code?

Great component! But we are having the same error of "TableHeader: prop type colGroups is invalid". We are using React 15.4.1 with react-bootstrap-table 2.8.0
Thank you

I'm using v2.7.1, and it Warning: Failed prop type: TableHeader: prop type colGroups is invalid; it must be a function, usually from React.PropTypes.
in TableHeader (created by BootstrapTable)

with even the simple code in tutorial.

hi all, this issue fixed on v2.8.1, let me know if this problem still remain.

@AllenFang, whatever fix you applied in 2.8.1 seemed to fix the additional error about "key" prop I was seeing. Thanks!

@AllenFang i updated version but warning not disappear. this is my code:
<BootstrapTable             data={[{ id: 1 }]}             striped             hover             headerStyle={{ marginBottom: '-20px' }}             search             searchPlaceholder="Search ..."             pagination             options={options}           >             <TableHeaderColumn dataField="id" key={_.uniqueId()} isKey dataAlign="center">               No             </TableHeaderColumn>           </BootstrapTable>

the warning disappeared but it seemed to have messed up the Sort ability on the table.

the warning disappeared but it seemed to have messed up the Sort ability on the table.

have more detail?

@nguyenchanhnghia, make sure you have already upgraded to v2.8.1, BTW, as your this mentioned, you never get this warning on v2.7.1 because v2.8.0 start to support header column group, so make sure the version you used first.

i upgraded to 2.8.1 because if I go back to 2.8.0 then the sort function works but the error exists. When i use v2.8.1 there is no error but the sort does not work. the caret arrows don't even appear.

Sorry, that's my mistake, I've patch it on v2.8.2, please upgrade it. Let me know if problem still there.

Looks great ! thank you for the quick fix.

I got warning prop invalid for tdStyle and trStyle.
Warning: Failed prop type: TableHeaderColumn: prop type `tdStyle` is invalid; it must be a function, usually from React.PropTypes.
Warning: Failed prop type: TableHeaderColumn: prop type `tdStyle` is invalid; it must be a function, usually from React.PropTypes.

I didn't customize those things though. Any clue?

@ferrwanz, what's the version you are using?

@AllenFang I'm using v2.11.1

upgrade to v2.11.2 will fix this issue


Panic while scrolling passed tests

This happened while testing the gba_save library. When scrolling down to the end of the displayed tests on the "passed" page, attempting to scroll to the tests below the bottom of the page causes this panic. I'm guessing there is some problem with an unaligned pointer.

This happened again when just scrolling down the "All" page. It didn't happen immediately though; I'm guessing some test is causing it repeatedly.
Here is a dump of EWRAM at time of panic, for further investigation:
ewram.txt

This happens specifically when trying to load info for the test at byte 0x0200_0049, which is a "passed" test.

This should now be fixed with this commit: https://github.com/Anders429/gba_test/commit/fc50b34fcf2e226f84de735b8e396b43db3bcd69


Template set overview

As a user, I want to get an overview of what template sets are installed including which increments are originating from which of the template sets so that I have an overview of the installed templates including increments for comparison and controlling.

Notes about this problem in regards to the CLI:

New command to show installed template sets/increments/templates

add parameters to the command (show everything (tree view), show all template sets/increments of a template set/templates of an increment)
be able to filter through template sets/increments/templates based on specific keywords (entity related, TO related etc) (maybe reliant on #1463 to add extra data)

Notes about this problem in regard to the Eclipse integration:

Do not show installed template sets from the generate context menu. The interface already exists in a way that would show those well but is too dependent on the input file and could confuse the user (don't generate to show what is installed)
Maybe use UI from the generation window with template sets top level, followed by increments and then templates. See as picture below but add templates as sub-choices for increments and instead of resources to be generated give descriptions for the selected template set/increment/template

Notes about this problem in regard to the CLI:

New command to show installed template sets/increments/templates

add parameters to the command (show everything (tree view), show all template sets/increments of a template set/templates of an increment)
be able to filter through template sets/increments/templates based on specific keywords (entity related, TO related etc) (maybe reliant on #1463 to add extra data)

I feel we could skip templates in a non verbose mode as normally people should focus on increments as lowest level. Nonetheless, it might be worth to see everything in a verbose mode

Notes about this problem in regard to the Eclipse integration:

Do not show installed template sets from the generate context menu. The interface already exists in a way that would show those well but is too dependent on the input file and could confuse the user (don't generate to show what is installed)
Maybe use UI from the generation window with template sets top level, followed by increments and then templates. See as picture below but add templates as sub-choices for increments and instead of resources to be generated give descriptions for the selected template set/increment/template

Also here, Level of templates might be too low and less helpful for the user. I fully agree with the fact that this should be a separate dialog as it's not related to the generate dialog.
Could you try some mockup tool to share some ideas like  https://gomockingbird.com/home?

I can propose to use: https://gitlab.com/barfuin/text-tree for the tree output in CLI.
I've already played around with it a bit and prepared a simple test. The formatting options are really useful.

Here are some very rudimentary mockups.
The first one is simply the templates and increments shown on the right with the option to select one and see its description on the right. On top there could be some description of what's going on in addition to an optional way to see the templates per increment as well

Next one is basically the same but with the "verbose" option chosen so the templates are shown as well. Descriptions for those are probably not necessary so they can't be selected.

This final one is not specifically the template overview but could be a way to download templates from a similar window. I do not think it is necessary since there is probably no proper way to show descriptions of multiple template sets and downloading them individually could be tedious for the user if they need multiple template sets (and confusion if you can download them in different ways in multiple locations)

Continued in #1454


UI/mood picker screen

Mood Picker Screen

Mood Picker Screen Completed.
Colors will be implemented after this issue #311 .
I use the Mood Tile that I created in this issue #326 , this PR is not merged yet so I simply copy this Mood Tile and Paste it into the Mood Picker screen to make some progress in this issue, so when issue #326 is merged, I will remove the Mood Tile that I copy paste in Setting Screen and use this one issue #326

For an AppBar, I will make a separate issue.


Add Supernova vs. Truth Table tutorial Notebook.

Develop a specific example of comparing a simulated supernova in the DM DIA outputs to the truth table.
While this will be developed for SN, it should be clear how to apply to AGN instead.

Closed by #106


pmacctd_integration

This research project focuses on integrating the pmacctd tool into the FABRIC testbed and includes the development of a comprehensive tutorial featuring various experiments.

@pilfg - Could you please sign the commits? Please see the instructions above.

@pilfg - Looks like your old commit is still unsigned. Could you please sign that as well?
If it's easier, just create a new branch and add your changes and use signed commits.
Also, another suggestion is to clear output of the cells in the notebook.
In addition, where you are using node.execute() which installs packages. I'd suggest to either pass in the log file to capture the output or run it as quietly as below:
Quiet Execution:
stdout, stderr = node.execute("command ", quiet=False, output_file=f"{node.get_name()}.log");

Redirect output to Logs:
stdout, stderr = node.execute("command ", quiet=True);

Dear Komal Thareja,
I have created a new branch and made a signed commit with my changes.
Additionally, I have updated the use of node.execute() to run package
installations in quiet mode.
Before I proceed with creating the pull request (PR), are there any other
improvements or modifications needed for the notebook?
Thank you for your guidance.
Best regards,
Pilar Fernandez
El jue, 18 jul 2024 a las 15:22, Komal Thareja @.***>)
escribió:

@pilfg https://github.com/pilfg - Looks like your old commit is still
unsigned. Could you please sign that as well?
If it's easier, just create a new branch and add your changes and use
signed commits.
Also, another suggestion is to clear output of the cells in the notebook.
In addition, where you are using node.execute() which installs packages.
I'd suggest to either pass in the log file to capture the output or run it
as quietly as below:
Quiet Execution:
stdout, stderr = node.execute("command ", quiet=False, output_file=f"{node.get_name()}.log");
Redirect output to Logs:
stdout, stderr = node.execute("command ", quiet=True);
—
Reply to this email directly, view it on GitHub
https://github.com/fabric-testbed/jupyter-examples/pull/294#issuecomment-2236513511,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUAU5PQ5SECJYDVMUDTSQUTZM66SPAVCNFSM6AAAAABK5CERNCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZWGUYTGNJRGE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@pilfg - I think everything else looks good. Please also remember to clear the output of the cells in the notebook.
Another suggestion - (not a mandatory change) is to use variables for parameters such as IP address which users may want to change on the top, so it's easier to customize your notebook.


voltaire can't find servers that users belong to, possibly due to sharding

Further info from skipper:
"So I was messing around with it to see if it works, it seems to work fine when it is said directly in the server but doesn't work when DM'ing the bot"

Looks like this was fixed by https://github.com/nminchow/Voltaire/commit/a35cc2f50a5bea43413a5579bae3514e738495a4. Closing for now


Cannot fetch DateTime lists

Steps to reproduce:

Create a new Blank project with SQLite
Use this schema:

generator photon {
  provider = "photonjs"
}

datasource db {
  provider = "sqlite"
  url      = "file:dev.db"
}

model User {
  id           String     @default(cuid()) @id
  datetime     DateTime
  datetimelist DateTime[]
}

Use this script:

const { Photon } = require("@generated/photon");
const photon = new Photon();

async function main() {
  await photon.users.create({
    data: {
      datetime: "2019-10-01T13:18:19.617Z",
      datetimelist: {
        set: [
          "2019-10-01T13:18:19.617Z",
          "2019-10-01T13:18:19.617Z",
          "2019-10-01T13:18:19.617Z"
        ]
      }
    }
  });
  console.log(await photon.users.findMany());
}

main()
  .catch(e => console.error(e))
  .finally(async () => {
    await photon.disconnect();
  });

This throws no errors, but the datetimelist field's value is not correctly returned from the findMany call. Note that a simple DateTime works as intended. Photon complains about an Invalid Date, even though the same date is used in both datetime and datetimelist fields.
Looking into the SQLite file, it seems the right data is created in the DB. This might very well be a photon issue, please relocate if that's the case!

Thanks for the detailed reproduction!
I can confirm this bug.

This might help in solving the issue:
https://github.com/prisma/prisma2/issues/809#issuecomment-547432541
I think that when a list (of any data type) is empty, the query on that data should return an empty array.

Looks like it is a pure photonjs issue as the engine is returning the correct data.


"Jasonette has stopped" crash when using tab navigation

Hello! I installed Android Studio 3.0.1 with Gradle 4.1 and opened the JASONETTE-Android-master project file. I have been trying the Twitter-UI-example and after I click on the tab navigation links a number of times, I am getting a "Jasonette has stopped" notification and the app crashes. Please assist in helping find out what is wrong with my setup. Below is a screenshot and an error log.

6472-6472/com.jasonette E/AndroidRuntime: FATAL EXCEPTION: main Process: com.jasonette, PID: 6472 java.lang.NullPointerException: Attempt to invoke virtual method 'void android.widget.ImageView.setSelected(boolean)' on a null object reference  at com.aurelhubert.ahbottomnavigation.AHBottomNavigation.updateItems(AHBottomNavigation.java:680)  at com.aurelhubert.ahbottomnavigation.AHBottomNavigation.access$000(AHBottomNavigation.java:52)  at com.aurelhubert.ahbottomnavigation.AHBottomNavigation$2.onClick(AHBottomNavigation.java:436)  at android.view.View.performClick(View.java:5637)  at android.view.View$PerformClick.run(View.java:22429)  at android.os.Handler.handleCallback(Handler.java:751)  at android.os.Handler.dispatchMessage(Handler.java:95)  at android.os.Looper.loop(Looper.java:154)  at android.app.ActivityThread.main(ActivityThread.java:6119)  at java.lang.reflect.Method.invoke(Native Method)  at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:886)  at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:776)

Can you share the exact JSON markup you're trying?

Hi! I am using the JSON markup here: https://raw.githubusercontent.com/Jasonette/Twitter/master/home.json
I am now suspecting it's something to do with the current Jasonette build, I experimented by loading the above url in Jason, the JSON browser installed from Play Store and I am getting the same error after clicking tab links a couple of times. I also tested with an older build of Jasonette and this problem is not there.

Screenshots:

JSON Browser
Twitter UI Example

I think this was related to a recent upgrade to the library we're using for the tab bar.
I've looked into the issue and think I've fixed it. https://github.com/Jasonette/JASONETTE-Android/commit/98885d0b14ddab39e0378faea4c59e7c84891b76
Please try pulling from the latest develop and retry and let me know if it works. Thanks!

Hi! I tried the latest develop, everything seems to work fine, but there is one scenario that seems to be still bringing up the same error. Was trying to put my finger on it and I think it happens when you have html items in the view url that you open.

Hi! I tested the latest master branch and this issue is no longer there, it works well. Closing this issue now. Thanks!


x-select to support attributes similar to ember select

x-select to support attributes similar to ember select
e.g.
{{x-select value=selections multiple=false action="selectionsChanged" content=model.books optionValuePath="content.id" optionLabelPath="content.title" prompt="Please select a name ember x-select"}}
i.e. in similar lines to
{{view "select"
content=model.books
optionValuePath="content.id"
optionLabelPath="content.title"
prompt="Please select a name ember select"
value=2}}

Hi @nagkumar!
We specifically don't support that style of select. I think Ted select is what you're looking for :)

There is also https://github.com/thefrontside/emberx-select-blockless, but as @Robdel12 said, the philosophy behind emberx-select is to map as closely to real HTML as possible and not take on the task of generating elements for you. We believe this explicit approach makes it more flexible and readable in the long run, but understandably it does require a few more lines of code.


Fix example test failure: rename ScheduledJob to CronJob

Fix the Travis CI build failure on example tests (i.e. this is blocking all other PRs)
cc @erictune @soltysh

This change is

LGTM

Merging to unblock other PRs


fix(router): Planner routing pattern fixed

Closing as we need to change this library not the calling application


Add file handling

Need to add the file handling concepts using Ruby

Hello! Could you please assign this to me? New to contributing, and I think I could add something beneficial for this issue.

Hey @jpierce-coder,
Assigned.

Is the issue resolved and is this applicable to hacktoberfest this year?

Is the issue resolved and is this applicable to hacktoberfest this year?

Hey,
This will be applicable to this year's hacktoberfest as well.


IBotContext information lost upon thread switches

Hi,
Last few days I've been trying out a few things with the new botbuilder SDK. I'm using Akka.NET to implement my dialog flow. I really like Akka.NET because I can easily implement an actor based on the finite state machine pattern to model different stages of the conversation that my bot is in.
I noticed however that when I pass the IBotContext as a message to my Akka actor information is lost and the call ReplyToActivity on IBotContext doesn't result in a message to the user of my bot.
I'm curious what happens with the IBotContext object when I pass it to another thread. Could it be that information is lost when I do this?

DISCLAIMER: I'm familiar with a couple Actor systems and the Actor model in general, but not steeped in Akka.NET specifically.
First, to make sure I'm understanding you correctly, you're trying to pass the IBotContext through to your actor via a message, correct? If so, I'm relatively certain that's not going to work. Actor messages are meant to essentially be POCOs that get serialized, sent to a mailbox (in Akka.NET's case) and then delivered to an actor "in time". While IBotContext is technically thread safe, it is not able to be serialized and "remoted" in this this way. Besides, it would be violating the rule of passing a mutable object to an actor which is frowned upon.
You also wouldn't be able to inject it via Akka.NET "props" because the props are only resolved when an actor instance is created and if that actor "lives" throughout many activity messages from the bot framework perspective, it would need to be working with the proper IBotContext for each of those messages.
I do actually think actor systems are potentially a really good match for implementing bots, I just don't think the current abstractions of the v4 SDK as it stands right now are going to "fit" that kind of system naturally due to the major architectural differences actor systems present from a traditional application architectures. It would not be a stretch to imagine a more native SDK for Akka.NET (or other actor systems) at some point in the future, but, full disclosure, I'm not on the product team so I'm not promising anything. 😄
Anyway, let's think... how could you do this right now? 🤔 I assume right now you are using some sort of API gateway leveraging ASP.NET, resolving an ActorRef and that's when you tried to send it over the IBotContext via a Tell based message... maybe? Spitballing here: what if, instead of sending over the IBotContext itself, you sent over only the Activity and maybe even your state, but you do so with an Ask and then your API gateway awaits that, takes the result of the Ask, which would be a respone message with maybe List<Activity> and your state again, and marshals those back onto the IBotContext???

I think passing a message (the activity) to the actors is indeed a better method of working. In almost all cases I will be sending a reply to the user so that looks good too.
Let me give it a try and see what happens :-)

Here's the code that I wrote: https://github.com/wmeints/bot-actors-sample

This is nice!

@wmeints, the email address listed in your GitHub profile bounces. Are you in Redmond for the MVP Summit? If so, please join us for our Bot Round Table tomorrow morning. 9:30 AM in the Building 35 Lobby.

I'm at the MVP summit, so I can join you for the round table. See you in building 35!

@wmeints I'm going to close this issue now that we've sorted it out.


Change single option value type to any if the source is internal stories

Fix for issue https://github.com/dohomi/storyblok-generate-ts/issues/20

@schaschjan shouldn't any be avoided if possible? As the internal stories name might be available, it would be better if the type of that story will be linked instead of any?

@dohomi Yes I agree that any should be avoided if possible. I chose to implement it this ways as the type is then equivalent to the current type of the options field.
As both the option and options field allow for various sources, the type should respect the source. I can have a look at how to make this work for both fields and would create a separate pull request as soon as finished.

I am also converting this package to TypeScript I hope I finish the rewrite soon

I am also converting this package to TypeScript I hope I finish the rewrite soon

Ok, I will wait for the rewrite then!

@schaschjan the release is out and the project is converted to TypeScript


Different color for the same thing in Monokai Dimmed

From @usernamehw on December 8, 2017 1:59

The first one has applied TM selector variable.other.property
The second - variable.other
What is it?

Both should be pink
Both should be blue
As designed

Copied from original issue: Microsoft/vscode#39905

The JavaScript grammar seems to give the following scopes,
variable.other.property.js
variable.other.object.property.js
Not clear why not both times other.object.property.
Moving to to https://github.com/Microsoft/TypeScript-tmlanguage

This is exactly how atom/language-javascript scopes these. Look at like https://github.com/atom/language-javascript/blob/master/grammars/javascript.cson#L1833 and https://github.com/atom/language-javascript/blob/master/grammars/javascript.cson#L1851
Note that in this.$el we dont know if $el is object hence just variable.other.property while in this.$el.style we know $el is object hence the scope variable.other.object.property

Okay. All other themes paint these 2 properties in the same color. What was meant specifically in Monokai Dimmed?

Both should be pink
Both should be blue
As designed


Discuss further actions for icon component

### Tasks
- [ ] Setup font awesome icon set in core theme
- [ ] setup

Diafram for icons structure


JavaScript (Node.js) Wrapper API

Because JavaScript is Awesome

+1!

+1 ! :+1:

+1

:+1:

+1

Just what I was searching for. :+1:
As quoted from the offical website http://www.tensorflow.org/

we’re hoping to entice you to contribute SWIG interfaces to your favorite language -- be it Go, Java, Lua, Javascript, or R.

I am new to this whole SWIG thing but searched around and found this. http://www.swig.org/Doc3.0/Javascript.html
Not really sure how this works. Do we need to write swig interface file specifically for Javascript or is it auto-generated when running some commands or is somebody already working on this (this would be awesome) ?

+1 :+1:

+1

@jagandecapri i am also not an expert on wrapping things with javascript, but i am willing to contribute!  (but might take some time)

+1

+1

+1

👍

:+1:

+1!
Just starting out on one, but new to writing a nodejs addon. Checking out the swig interface files to see if they're going to be helpful, or if I should just use the c++ API.

+1

+1

+1

+1

+1

This is something the core TensorFlow team is unlikely to tackle in the near future, so if you want to contribute it, please go ahead! I would recommend circulating a proposed implementation on the discuss mailing list early on, so that a consensus about where such API might live (in repo / off repo / in 'contrib' directory) can be reached ahead of time.

Anyone up to code a NodeJSlibrary? :+1:

:+1:

@Foorack I am willing to contribute it if some people are interested as well. Is it possible to move the discussion to a slack channel ? (see #31)

@tngan The slack channel is private, however is was able to join with the herokuapp link. :+1:

We hope more developers to discuss and contribute. Now we have a slack channel named as nodejs (see #31), and a Github repository node-tensorflow is reserved. Thanks @Foorack !

I am willing to contribute. Thanks for the initiative guys!

@miguelalche Glad to see you're interested! Please join the slack channel and someone will add you to the repository. ^^

I look forward for contributing ( specially along with #132 ) !!

+1

Hooray for node! Let's do this.

+1

+1

Here's a writeup on how to load and execute TensorFlow graphs using the C API: https://medium.com/jim-fleming/loading-tensorflow-graphs-via-host-languages-be10fd81876f (source code included)

The proposal will be released in the next week. Keep tracking on https://github.com/node-tensorflow/node-tensorflow.

+1

I have published my starting point -- https://github.com/nikhilk/node-tensorflow that will be published to npm later.
@jimfleming - like your approach (we're both using ffi ... I did it to get started quickly). Are you going to take on building higher level framework-style APIs to replicate the python experience? Thats my next step.

@nikhilk Thanks. Something like new tf.Tensor() instead of tf.NewTensor() might be a nice addition but I'm not planning on expanding it at the moment. I'm only interested in loading graphs created in python and I think I like the minimalism.

+1

The proposal is released here with current progress.
https://github.com/node-tensorflow/node-tensorflow/tree/1.0.0
There is an open issue for the discussion.
https://github.com/node-tensorflow/node-tensorflow/issues/2

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1
It'd be great to be able to easily run tensorflow networks in node.js based servers.

+1

+1

+1

+1

+1

+1

I am very willing to contribute. @Foorack please add me to what ever you can! I have a real life use case for this so it will be great to develop and test it at the same time!!

@pushtheworldllc I'm glad you are interested. :)
The repository and the proposal can be found here: https://github.com/node-tensorflow/node-tensorflow/
You can use this link to join our slack channel: https://tensor-flow-talk-invite.herokuapp.com/

+1

+1

+1

+1 :+1:

+1 :+1:

I have a working prototype using SWIG here: https://github.com/node-tensorflow/node-tensorflow/pull/13
The next steps would be to define the areas that the bindings would initially cover (must be within the C++ API ) and start implementing the SWIG interface files for these.
If anyone has experience with SWIG, I'd love to collaborate, as it seems like a huge amount of the python SWIG interfaces are custom overrides etc. and I'm keen not to reproduce their work. Additionally, would be great to get some clarity from the tensorflow team on what API's would be good to initially cover as I'm sure their roadmap has many changes on the way, and I wouldn't want to conflict. (cc @martinwicke ? )

+1

+1 :+1:

+1

+1

+1

+1

+1

please try use reactions button --> http://www.geekwire.com/2016/github-adds-reactions-keep-comments-track/ no more +1 comments xD

+1

:+1:

+1

+1

+1

@peterbraden sorry for the prolonged silence. We are building out the C++ API, and it will grow over time. I expect the most useful bits to be the parts that are needed to run an existing graph. The C++ graph building API is being redone right now, so it's not particularly useful to spend much time on it.
I'd love it if you prepared a PR to put these bindings into contrib/nodejs.

@martinwicke thanks for the encouragement. I made an initial stab at it here: https://github.com/tensorflow/tensorflow/pull/2206 - this is just a proof of concept that gets the version string into nodejs. I'll start work on adding the swig interfaces for the graph running stuff.

+10000

+1

+1

+1

+1

+1

+1

This would be interesting for pure front-end graph exportation for direct usage on web clients. Even if the desired inputs/outputs asked from the graph would be hard-coded in the exported JS "sess.run" equivalent function.

+1

:+1:

+1

+1

+1

+1

Found this while looking into wether or not bindings existed already.  Going to learn some tensor flow via the current python API before researching more, but I have built nodejs bindings for C++ libs before and can tell you from experience that swig is the wrong way.
If you simply use the swig bindings then you will have synchronous blocking code in an async environment.  The swig bindings do not run things on IO threads, they execute on the main event loop from what I understand/experienced.
Once I have some basic tensor flow experience under my belt I'll likely be interested in building out proper bindings.  So if anyone is serious about that and/or wants more details on working with v8 modules, let me know.

Is there any link related to node-gyp binding for tensor flow API ??

@dmcmorris I am seriously interested in lending a hand! What resources do you recommend for working with v8 modules? We can assemble a team here and start diving into materials asap as this project is way overdue :)

+1

+1

+1

+1s

Is there any update ??
On 31-Oct-2016 12:06 pm, "willshion"<EMAIL_ADDRESS>wrote:

+1s
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/37#issuecomment-257222936,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANrvwrbmShC9c0_wsNpTudKSCb0-8qt8ks5q5Yx3gaJpZM4Ge5NV
.

Happy Anniversary TensorFlow !
https://research.googleblog.com/2016/11/celebrating-tensorflows-first-year.html
I notice TensorFlow is now accessible from Go, Rust and Haskell. Why ignore JavaScript ?
Really waiting for a machine library in JavaScript.

+1

+1

💯 👍

+1

+1.0000000000000000000000001

+1

+1

+1

+1

I am looking forward to see a official Node.js API.But I think there are some problems.

JavaScript have only 1 thread ,trainning  can block the whole process unless using callbacks or  other tricks.
lack of other science labs, like numpy
JavaScript only support 53bit precision.

anyway, JavaScript is awesome!

Is anybody working on this?

Looks very difficult.

+1

very need it!

@stackOverMind. Did a little search on these bullet points. I've not tried any of these and they might not be efficient to use / run but it looks like there are things that exist to potentially solve those issues.

taking advantage of multi processor environments in node js
node-lapack
numjs
Long.js
mljs

+1

+1

+1 pweeettyyy pwease!!!

+1

+1

Looking forward to it. 👍

+1

Looking forward to it. :+1:

👍

+1

+1. I have some experience in Node, and will take a  look at this.

+1

+1 Can't wait, Python is great, Node and JS is great too

+1

+1 just for the sake of it

+1!

+1

+1 👍

+1

+1 would be cool af

+1 <3

👍

👍

+100

+1

+1

:+1:

+2

+1 ;)

mark

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

:+1:

+1

+1

+1

👍
Please !

+1

+1

I think I might be getting the hint that nothing will be happening regarding with this issue. The OP's date was from 2015, its now 2017 and it's not been picked up by anyone on the project. Does anyone know if there has been any healthy discussion regarding tensorflow and node anywhere, as these +1's don't seem to be doing much :(

+1

#+1

👍

+1

+1

:+1:

it's been 2 years and still no luck?

Good. Fuck Javascript.

+1.0/0.0

Use synaptic https://github.com/cazala/synaptic

Inspired from deep_recommend_system, I am now trying another way to access the model with Node.js through tensorflow serving, still in progress.
https://github.com/tngan/tensornode

this could be useful keras-js

+1

@sarkistlt Unfortunately no, we are NOT talking of doing a javascript implementation of Tensorflow, which keras.js does, but we are talking having a nodejs wrapper around the C++ api of Tensorflow, so it requires understanding how to write native add-ons for NodeJs.
Other useful source.
Unfortunately my day job is not coding and it requires proficiency in C++, which I personally don't have.
By the way keras.js does only inference, no training, so no backpropagation.
Google developers implemented a small portion of Tensorflow in Javascript in their playground, the neural network implementation is here and does include back propagation.

There is I started work on native nodejs Tensorflow implementation, would be great if anybody joins
https://github.com/nodejs-tensorflow/nodejs-tensorflow

+1

+1

+1

+1

I'm so happy to hear you're giving this a shot @JIoJIaJIu. The potential for impact in solving this issue is huge. It's our most upvoted issue.
At cursory glance, so far you seem to be doing the right thing. You created this in a separate project and are using the TensorFlow C API, as @martinwicke recommended earlier.
A good way to attract contributors to your project would be by sharing a design doc with the TensorFlow mailing list, as Vincent recommended a few years back. That way we can build consensus around your vision and help it be the best vision possible.
The TensorFlow team wants the NodeJS community to benefit from TensorFlow. So we're absolutely interested in helping the individual devoted to making that happen be successful.

If someone out there is listening,  this seems to be the most requested feature for Tensorflow:
https://github.com/tensorflow/tensorflow/issues?utf8=✓&q=is%3Aissue is%3Aopen sort%3Areactions-%2B1-desc

+1

Hi all, I created a Node.js bridging library for Tensorflow at: https://github.com/yorkie/tensorflow-nodejs without SWIG, it has supported "predefined graph running" and very simple "graph construction", I'm also planing to support more client features in the future :)
But I would glad to make this be merged by Tensorflow official group, that would be a zero-cost PR to me :)

@yorkie It looks interesting, I will try it out! However we cannot merge GPL code into TensorFlow.

@yorkie it looks awesome, would you like to join to the project and join forces?

@ry sure I can change the license surely :)
@JIoJIaJIu I dunno what's the best place to move this repo for now, if this repo is not suitable for moving tensorflow org, I think nodejs-tensorflow is the good place :)

However we cannot merge GPL code into TensorFlow.

@ry Updated the license to MIT.

+1

+1

+1

+1

+1

JavaScript APIs for TensorFlow were announced earlier this month. See details on the deeplearn.js homepage.
I'll close this (broad) bug now. Feel free to open other more specific FRs.

deeplearn.js is for browser with webgl, not a sdk for node.js

Fair enough. I see now that the bug title references Node.js directly.

@vincentvanhoucke it's not even about node.js in the title. Talking about "deeplearn.js" and "Tensorflow API for Javascript" is like talking about apples & pears.
First one is a library that only mirrors to some extent "the style of TensorFlow API" and operates purely in the browser and the other would be a direct API to whole Tensorflow goodness. deeplearn.js is not even remotely close be called an alternative to Tensorflow... maybe for hobbists but not for commercial use, where one would need clusters of machines to aim the computing process.

+1

+999

Jesus christ, stop sending people useless notifications, there's a reason GitHub introduced 👍 and 👎 reactions.
+1 and +999 just annoys people and adds no value whatsoever.

+1000

:+1:

+1

+1

ATTENTION
😄 Guys please before commenting +1 or +whatever - Please take a look at @k1sul1 's comment

Jesus christ, stop sending people useless notifications, there's a reason GitHub introduced 👍 and 👎 reactions. +1 and +999 just annoys people and adds no value whatsoever.

@shahen94 we all saw that but still... we are js dev.

+1

@BruceHem not really sure how being a js dev correlates with blindly pushing unnecessary spam to the feed... 😄
You all are aware that "+1" just makes this topic unreadable? I understand that we all have the desire to support this case but can only deduct that on github closest thing to "vote" functionality is implemented with "reactions" not with a count of comments in the thread... or am I missing something? ;-P

Lol :P this thread died years ago.
.
+1 Googolplex!

+1

Agreed with @thefill "+1" just makes this topic unreadable, and actually we had community implementations then if anyone wants to use TensorFlow with Node.js or JavaScript, just have a try with the above one or two, I think this might be a good start than comment votes here.
As for me, I was working on https://github.com/yorkie/tensorflow-nodejs to make it enough functional like Python possible, and it still have such long time to go, but it basically has full implementation for official language_bindings API. That means you could still use Python to build graph, but load models and run it within a Node.js runtime. Other languages except for Python also can do this currently.
I was also asking for the help from @ry to make my personal repository to be supported officially, there are few things we have to do like building some example models especially RNN cases, but unfortunately I'm got to work on other fields and have no time for these few months, if someone is interested in making this be happened, email to me, I'd love to guide you how to start. Let's the do something useful for community in best wishes :)

In regards to the current projects that have been started, and specifically the challenges of working with the C API, I have a suggestion on implementation that has worked well for me.
Since python is still the most robust, developer-friendly, and full featured wrapper around the Tensorflow API, rather than trying to "re-create" the python API for js, why not create bindings directly TO the python API? This would still require first creating a node C++ add-on, but rather than binding to the C API directly, you can employ "embedded" python to run python methods directly from C++.
This is unlike other JS => Python solutions out there that suggest simply spawning a python script...a solution not viable for any reasonable size learning problems because of the extensive data transfer cost (time) between the processes. With embedded python however, memory accessed by your python script / numpy arrays directly point to your js Float32Array buffers.
This solution is working very well for me (though admittedly getting the initial js => C++ => python flow working was kind of a pain). Since I have specific needs, I have not gone through the task of binding to each individual python TensorFlow method, and instead just pass my data and hyper parameters to a few methods that build most of the graph. The full individual binding wouldnt be too bad from my current starting point.
I welcome any thoughts or suggestions on the approach outlined above. Thanks.

@djimoh5 Awesome thoughts on JavaScript to Python full-featured APIs! The other hand, we also could put an implementation of a RPC server for TensorFlow Python APIs with introspection feature, so that JavaScript and other language clients could access the real-time Python. (I will do this when I'm available, aha)
But here is something about why re-creating some Python features for JavaScript, because they are written in JavaScript, they are more friend to JavaScript developers, and it's easy for that developers to modify the source code to check if something different is possible, not just the get feeds from upstream :)

+1

I'm also interested in nodejs tensorflow API   to be able to use it in node-red flows would chain tensorflows graphs and may be other kinds of data analysis nodes. I still don't know much about tensorflow. It May not be thé right place to ask but I'd like to know why others developers look for a nodejs api/add-on for tensorflow ? What would be your use cases ?

@khelkun answer is rather simple: providing mature JavaScript package that allows easy interaction with Tensorflow opens myriad new possibilities. JavaScript operates on every mobile platform, all major desktop Operating systems & in all the browsers so possibilities are endless.
Biggest benefits would come for sure from server-side applications that operate on node.js that could directly interact with Tensorflow, but also node-webkit (desktop applications) could potentially spawn dozens of interesting projects.

Are the community organizers /admin of this thread not able to simply delete the posts of the those people that intensionally trolling with all the "+1's” maybe even ban them? Lol

Has anyone working on this integration considering using WebAssembly (wasm)? It is potentially the most elegant solution to this problem, side-stepping all of the talk of JS talking to Python talking to C++, you know. I really don't know much about the internals of TensorFlow, but I believe the C++ parts of TensorFlow could be compiled to wasm (check the MVP features supported, but Unreal Engine 4 was compiled to wasm's predecessor and ran successfully in FireFox). Once the C/C++ API is compiled to wasm, you just need to ensure the necessary API is exposed. wasm will run in Node.js, all major browsers, and even outside of any of those, since it is meant to be an extremely portable bytecode. This seems like the best path forward to me.

+1... we no longer live in the medieval portion of the information age. Please support node.js.

Why would anyone need another Javascript library? Why would anybody use a JS library to train NNs? Javascropt is a bad desigbed language.

@AyalaSaenzJorge lol (since you're trolling why dont I have at it) ... How about we LOVE "badly" designed languages? Javascript happens to be to most prevalent language currently in existance.. more code (on earth) is written in javascript than ANY other high level language.. And that's a FACT and it's never going away sorry lol
For those of you more serious than this troll Checkout the https://deeplearnjs.org ... It is influenced by tensorflow and backed by Google ... Maybe rather than starting from scratch we may consider porting that to Node.js instead

@somombo yes, it looks really interesting.  RE: tensorflow + deeplearnjs, see esp:

https://deeplearnjs.org/demos/mnist/mnist.html
https://github.com/PAIR-code/deeplearnjs/issues/238
https://github.com/PAIR-code/deeplearnjs/issues/407
etc

@AyalaSaenzJorge this is a place for informative comments, not an opinionated-firestarters.
@somombo please see my comment from 26 Aug where I explain why deeplearnjs is irrelevant to this debate.

@thefill I saw your comment, but respectfully I disagree I think there are good lessons that were learned on the deeplearn.js project that would be certainly be relevant to creating node.js ML library that can import tensorflow graphs, and save checkpoints etc without the need to directly invoke tensorflow (py or c code) itself. I think it would be nice and very useful to see an isomorphic version of deeplearn.js that works in the browser as well as on the server (nodejs) .. and is optimized to use webgl in browser and uses something N-API(or webassembly)+gpu on the server. How great would it be if you didn't have to configure it... If it just knew what environment it's in and just worked! ... However, I will concede that perhaps my points are better discussed as an issue on the deeplearn.js repo rather than here.

Ok sorry for the comment.
El dic. 12, 2017 6:46 PM, "Filip Dabrowski"<EMAIL_ADDRESS>escribió:

@AyalaSaenzJorge https://github.com/ayalasaenzjorge this is a place for
informative comments, not an opinionated-firestarters.
@somombo https://github.com/somombo please see my comment from 26 Aug
where I explain why deeplearnjs is irrelevant to this debate.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/37#issuecomment-351232483,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeZvKtru1EQjtRnoz6ZR36Kh-DTfVNozks5s_xBVgaJpZM4Ge5NV
.

+1

@cpple Remember not to add +1s, they cause noise and have been replaced by reactions. Try giving the first comment a thumbs up

Just want to share an update -- revamped https://github.com/nikhilk/node-tensorflow with plan to have that support using TensorFlow graphs (and later, saved models) for prediction/inference in node.js. Thought I'd share since a number of folks have expressed interest on this issue.

+1

propelml.org - Looks promising not tried it but its GPU enabled and runs in both the browser and on node

@7ammer propelml.org looks rather promising. Thanks for sharing this with us ;-)

Because NodeJS it's fast! ;D

If an ambitious member of the community wants the glory of solving this problem, and having it merged into the TensorFlow contrib codebase, here are some tips on how I would do it. Please note I'm not going to do this.
You can add Node to workspace.bzl just like TensorBoard did in js.bzl.
Please note TensorFlow can not depend on rules_nodejs.
load("@io_bazel_rules_closure//closure:defs.bzl", "filegroup_external")

filegroup_external(
    name = "org_nodejs",
    # MIT with portions licensed:
    # - MIT
    # - Old MIT
    # - 2-Clause-BSD
    # - 3-Clause-BSD
    # - ISC
    # - Unicode
    # - zlib
    # - Artistic 2.0
    licenses = ["notice"],
    sha256_urls_extract_macos = {
        "910395e1e98fb351c62b5702a9deef22aaecf05d6df1d7edc283337542207f3f": [
            "https://mirror.bazel.build/nodejs.org/dist/v6.9.1/node-v6.9.1-darwin-x64.tar.xz",
            "http://nodejs.org/dist/v6.9.1/node-v6.9.1-darwin-x64.tar.xz",
        ],
    },
    sha256_urls_windows = {
        "1914bfb950be8d576ce9e49c8a0e51c9f2402560fe3c19093e69bc1306a56e9e": [
            "https://mirror.bazel.build/raw.githubusercontent.com/nodejs/node/v6.9.1/LICENSE",
            "https://raw.githubusercontent.com/nodejs/node/v6.9.1/LICENSE",
        ],
        "513923b0490ebb7466a56483a62595814ed9d036d6f35476debb0cd606bec526": [
            "https://mirror.bazel.build/nodejs.org/dist/v6.9.1/win-x64/node.exe",
            "http://nodejs.org/dist/v6.9.1/win-x64/node.exe",
        ],
        "3951aefa4afd6fb836ab06468b1fc2a69fa75bd66ec2f5a0e08c4e32547681e3": [
            "https://mirror.bazel.build/nodejs.org/dist/v6.9.1/win-x64/node.lib",
            "http://nodejs.org/dist/v6.9.1/win-x64/node.lib",
        ],
    },
    sha256_urls_extract = {
        "d4eb161e4715e11bbef816a6c577974271e2bddae9cf008744627676ff00036a": [
            "https://mirror.bazel.build/nodejs.org/dist/v6.9.1/node-v6.9.1-linux-x64.tar.xz",
            "http://nodejs.org/dist/v6.9.1/node-v6.9.1-linux-x64.tar.xz",
        ],
    },
    strip_prefix = {
        "node-v6.9.1-darwin-x64.tar.xz": "node-v6.9.1-darwin-x64",
        "node-v6.9.1-linux-x64.tar.xz": "node-v6.9.1-linux-x64",
    },
    executable = [
        "node",
        "node.exe",
    ],
    default_visibility = ["//tensorflow/contrib/node:__subpackages__"],
)

Now let's say you want you have a Node program, e.g. tsc.js, which you want to turn into something you can bazel run //tensorflow/contrib/node:generate. One quick way you could do this in Bazel is by defining a macro in tensorflow/contrib/node/defs.bzl:
def node_binary(name, srcs, data=None, visibility=None, testonly=None, **kwargs):
  native.sh_binary(
      name = name,
      srcs = [name + ".sh"],
      data = srcs + data + ["@org_nodejs"],
      testonly = testonly,
      visibility = visibility,
      **kwargs
  )

  native.genrule(
      name = name + "_sh",
      srcs = [srcs[0]],
      outs = [name + ".sh"],
      cmd = "cat >$@ <<'EOF'\n" +
            "#!/bin/bash\n" +
            "NODE=external/org_nodejs/bin/node\n" +
            "if [[ -e external/org_nodejs/node.exe ]]; then\n" +
            "  NODE=external/org_nodejs/node.exe\n" +
            "fi\n" +
            "exec $${NODE} $(location " + srcs[0] + ") \"$$@\"\n" +
            "EOF",
      executable = True,
      testonly = testonly,
      visibility = ["//visibility:private"],
  )

Now for the fun part. I would write a single .js file (even if it had to be 30,000 lines long like tex.web) with zero dependencies other than the Node standard library. The inputs for this program would be ops.pbtxt and all the other pbtxt files in api_def/base_api. The output to this program would be exactly one gigantic C++ file that talks to TensorFlow C API and Node C++ Addon API based on this example.
load("//tensorflow/contrib/node:defs.bzl", "node_binary")
load("@domain_registry//java/google/registry/builddefs:zip_file.bzl", "zip_file")

node_binary(
    name = "generate",
    srcs = ["generate.js"],
    data = [
        "//tensorflow/core:ops/ops.pbtxt",
        "//tensorflow/core/api_def:base_api_def",
    ],
)

genrule(
    name = "api",
    srcs = [
        "//tensorflow/core:ops/ops.pbtxt",
        "//tensorflow/core/api_def:base_api_def",
    ],
    cmd = "$(location :generate) $(location api.cc) $(SRCS)",
    outs = ["api.cc"],
    tools = [":generate"],
)

zip_file(
    name = "tfnode",
    srcs = [
        "package.json",
        "README.md",
        "api.cc",
        "binding.gyp",
        "tfnode.js",
    ],
    mappings = {"tensorflow/contrib/node": "package"},
)

Then you bazel build //tensorflow/contrib/node:tfnode.zip and bam you've got your NodeJS project all bundled and ready for distribution to places like NPM.
If I wrote this (which I won't) it would be a barebones direct mapping of the TensorFlow API definitions. Then I would encourage our friends in the community to veneer the library. There's a diversity of visions out there on friendly modern high-level idiomatic JS and ML APIs, each catering to different use cases. However they could all share this binding in common.
Please note there are examples of where we already generate language bindings. See tensorflow/go/genop/main.go and tensorflow/go/op/generate.go for inspiration.

Looks like the TensorFlow team is making this a top priority now: https://js.tensorflow.org/faq/

As update to this issue - we have open-sourced the Node.js binding for TFJS: https://github.com/tensorflow/tfjs-node
We are working hard at getting a proper NPM build and will release it soon!

I will close this issue. Please track tensorflow/tfjs and tensorflow/tfjs-node for further updates.

Related and possibly of interest: I managed to get TF running in the browser via Webassembly. See https://humantoanimal.com for a demo; I will be providing more details in the future.

@nuchi, so did you compile the necessary TensorFlow code from the C API to WebAssembly? Or are you using TensorFlow.js?

@lastmjs I explain in more detail in the link I provided. Short version: I added Webassembly as an XLA compilation target. I did not use Tensorflow.js in any way.

@nuchi Great work! and I know another WebAssemble work on TensorFlow at here:
https://medium.com/@tomasreimers/compiling-tensorflow-for-the-browser-f3387b8e1e1c

Glad to see that there's official progress on this. I'd love to have fast, parallel GPU compute power at my fingertips with the ease and composability of JS.
I started working on a NodeJS binding for TensorFlow a while ago, but a haven't had much free time to devote to it lately.
The concept is similar to @jart's suggested approach.
I had three goals in mind for the project:
1. Don't require building or installing tensorflow
Instead, it should download and use the pre-built, multi-platform python binaries and download any needed source files on the fly.
2. Don't require a complete C++ or JS reproduction or abstraction of the API
Instead, it should provide a complete 1-to-1 interface with the C API, providing convenient JS abstractions as much as possible.
3. Don't maintain the C API bindings by hand
Instead, it should use a swig script to map the core data structures between Tensorflow/stdc++/V8/node and the rest will follow.

I got pretty far along with this, but last I remember a was having issues with TF_Session related segfaults.
Right now it's just collecting dust, so if someone wants to jump in and help with this I'd gladly accept PRs.

Closing as this is resolved


Fix title to align

Align title

Deploy preview for calico ready!
Built with commit dc7f9f93d941f47f390a5e6a4fe9386153f12565
https://deploy-preview-3000--calico.netlify.com


Add more fields to the device plugin spec

Cherry-pick from upstream https://github.com/qbarrand/oot-operator/commit/31e2fe7c5133b5334642b52e41ca0df662e018c4.
/cc @yevgeny-shnaidman @fabiendupont @ybettan

/lgtm


Upgrade to SHDP 2.4.0.M1 release

As a developer, I'd like to upgrade to SHDP 2.4.0.M1 release, so I can take advantage of the latest improvements in hdfs and gpfdist sinks.

Moved to: spring-cloud/spring-cloud-stream-app-starters#15


Fixing bullet points and quotes on comment review

Fixes eregs/notice-and-comment#307

Good sleuthing! Does it work well for nested bullets/numbered lists, too?
I think ideally we'd pull out comment-content and reduce some duplication rules applying to ProseMirror.
Heads up: merge conflict.

It does seem to work with nested bullets/lists however I can't figure out how those would actually be created with the tool itself. I had to create something in google docs and copy/paste it over.
I'll work on cleaning up the merge in a bit.

Travis errors are due to linting; will be resolved later.


MobiusLoopTest: add tearDown and fix a comment

ah I forgot that I added that when I reset the commit :D Thanks for doing it!


Broken i2c on Raspberry Pi 5

A customer is running into the issue described here (Zendesk 3607): https://github.com/raspberrypi/linux/issues/6043
The kernel on the balena device is:
Linux 59f3c40 6.6.22-v8 #1 SMP PREEMPT Tue Mar 19 17:41:59 UTC 2024 aarch64 aarch64 aarch64 GNU/Linux

Kernel logs:
[81900.707649] i2c_designware 1f00078000.i2c: i2c_dw_handle_tx_abort: lost arbitration
[81901.714440] i2c_designware 1f00078000.i2c: controller timed out
[81902.834436] i2c_designware 1f00078000.i2c: controller timed out
[81903.954453] i2c_designware 1f00078000.i2c: controller timed out
[81905.074427] i2c_designware 1f00078000.i2c: controller timed out
[81906.194447] i2c_designware 1f00078000.i2c: controller timed out
[81909.842410] i2c_designware 1f00078000.i2c: controller timed out
[81910.866405] i2c_designware 1f00078000.i2c: controller timed out

The PR that fixes the issue is: https://github.com/raspberrypi/linux/pull/6050

Hey @majorz, do you guys have any update on this?

hi @YinonLensor did you try a balenaOS release above v5.3.21+rev4? It contains a v6.6.22 kernel that has already been patched for the problem above.

btw @YinonLensor we don't have a policy of monitoring github issues, so it's better if you contact us through our support channels.


Tags link fix

Tags link fix for when there are no (AWS EC2) tags shown in a table row
https://issues.redhat.com/browse/COST-4855

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

Project coverage is 65.71%. Comparing base (d694aec) to head (3fd1ed1).

Additional details and impacted files
@@           Coverage Diff            @@
##             main    #3860    +/-   ##
========================================
  Coverage   65.71%   65.71%
========================================
  Files         515      515
  Lines        9999     9999
  Branches     2357     2357
========================================
  Hits         6571     6571
- Misses       3180     3424   +244
+ Partials      248        4   -244

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


Feature: adding more css features to about page

Feature description
Please assign me this task
👀 Have you spent some time to check if this issue has been raised before?

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

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Hii
Please assign me this task

I want to work on this issue as a contributor.
Pleasure Assign so that I can show my skills under GSSoC'23.

Hey @SauravMukherjee44 , I would like to add more css features to about page .I can resolve this bug. I'm a contributor to GSSOC'23 please assign this issue to me as a part of GSSOC'23

please assign me this task. i want to work on this

Folks, Post the image of your changes on the About page here.

For any help, you can reach out to me here: https://sauravmukherjee.bio.link/

I am interested to work on this issue please assign me this task under GSSOC.

I would like to change the ui of the about us page to make iit more attractive .
I would like to add some images and would change the whole layout of the page.
so,please assign this to me under GSSOC'23.


Doc update to support standard AWS credential loading.

Docs changes from machine PR https://github.com/docker/machine/pull/3799
Signed-off-by: Gordon Shankman<EMAIL_ADDRESS>

@nathanleclaire @mrburrito LGTM! merging

@mrburrito @nathanleclaire these AWS docs changes are live now: https://docs.docker.com/machine/drivers/aws/
(Let me know if they should not be! i.e., if they aren't valid yet for currently available binaries .. we need to figure out a process for this .. hopefully it was ok to publish these particular changes)

@londoncalling the PRs on the machine project haven't been merged yet. Might be better to back these out until those are closed. I think the AWS credentials are closer to being merged than the userdata update.

Thanks! Sorry about that .  We talked about  creating a v-next milestone on
the docs side for these situations . I'll work it out with Nathan and John
today .
On Wednesday, October 5, 2016, Gordon Shankman<EMAIL_ADDRESS>wrote:

@londoncalling https://github.com/londoncalling the PRs on the machine
project haven't been merged yet. Might be better to back these out until
those are closed. I think the AWS credentials are closer to being merged
than the userdata update.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/pull/36#issuecomment-251677352,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALHuA3mtlUy0dVt_X1mhGnD0VyueNDdbks5qw6izgaJpZM4KOJ2G
.

@londoncalling They are for new features which won't be included until 0.9.0 :( They should not be live

I think it needs to be opened as PR to vnext-machine branch


Removed [fn].name override. Causes TypeError in strict mode

See: https://github.com/Netflix/falcor/issues/586#issuecomment-150840423
function.name is spec'd as read-only, and setting it, with "use strict" throws a TypeError in browser in which it's supported. In the browsers which support it, it's already "set", so we don't need to reset it.
IE seems to be the only outlier (haven't tested Edge): https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Function/name#Browser_compatibility
If we do need to set it for some reason, we probably need to try/catch or feature test before setting it, but not sure if we really need it set on the constructor function.

Closing this, and opening a PR against 0.x which is a branch I just pushed, off of the last 0.x publish from master. We can use the 0.x branch for minor/patch fixes since master is effectively 1.x now (it has the back-incompat deref change).


CI: Dont check for dev0 in maint branches

Helps with #11002
This will still make the one commit to main that bumps to non dev0 fail, though. @drammock I could easily add a [azp ignore dev] commit tag awareness or something, is this worth it?

to me this is only worth it if the changes actually reduce cognitive overhead

If we say in the Wiki "include in your commit to remove the dev0 label [azp ignore dev]", then all stays green. Would this have reduced cognitive load or no? It's only a couple of lines of code in the CIs.
But actually there are maybe better ways to check that the imported mne is the correct one. That's probably an easier route, I'll try that...

Okay @drammock I think this is cleaner


Add example page for Next app router and DaisyUI

This PR, inspired by https://github.com/wslyvh/nexth/issues/4.
Two examples pages are added using Next.js app router and DaisyUI with tailwind :
Send Ether transaction
Send ERC20 transaction
react-toastify is added

Hi @Maxtho8 this is great! Thanks you for contributing.
I've left some comments on some of the files. Hope it makes sense.
Also keep in mind that I've upgrading wagmi/viem and Web3Modal to their next major version.
This might result in some merge conflicts in your PR.
Not sure if it's feasible to merge, or maybe just submit a new one.
Happy to chat if you need anything

Hi @wslyvh! Thank you for your feedback.
Yes, your comments make sense. I understand the utility of not embedding react-toastify in every file but rather in a provider. I hope my fix is better. However, I didn't fully understand the part about the format of balances.
I successfully merged wagmi V2 without any issues, my PR is up to date. I also fixed the example pages to align with the recommendations of wagmi V2.

Great to hear wagmi v2 merged successfully and thanks for the updates!
The changes on the toast provider are great!
Only one minor issue with balance formatting. Let me know if you need more context

Hi,
Here is the fix to round the balance :)

Hi,
Here is the fix to round the balance :)

Awesome! Thanks again for the PR, nice work 🙏


Create a wascc:logging capability provider

In order to give different environments more options when it comes to handling the logs emitted by the actors (not to be confused with the trace/debug emissions from wascc-host), we should have a wascc:logging provider that is invoked whenever an actor attempts to log.
This will:
a) Break any existing compiled modules that don't have a wascc:logging capability
b) Require updating the wapc-host-rust crate so that waSCC can provide a callback for logging
c) Provide an update to wascap so that wascc:logging is one of the well-known standard capability IDs

The wascc-host should expose a default logging provider (much the same way it does for the wascc:extras provider. The default would be to have no logging provider (actors can't emit logs), but hosts could also add the default with code something like this:
host::add_native_capability(NativeCapability::from_instance(DefaultLoggingProvider::new()))?;

This change will go hand in hand with the change to the actor SDK


Different disk layout per machine

Ultimately, this pull request allows us to specify disk layouts to use on a per-machine basis, by specifying Hieradata in hieradata/ named after the FQDN of the machine itself.
When adding a new off-site backup target in Skyscape, we realised that we had eight disks. Disks are added as a result of trying to increase space on existing backup machines. The problem with eight disks is that, given the SCSI Controller addresses the first disk as disk 0, the eighth disk becomes disk 7. This means that we run in to https://github.com/gds-operations/vcloud-launcher/issues/104 when we try to deploy machines with seven or more disks.
To work around this, and in order to make more efficient use of disks on hosts, we should squash disks together. The real resolution will hopefully be a fix to the above issue, but this is a short-term fix to get things working. We're also adding additional space to some volume groups, such as the graphite one since they were getting low on space. You'll also see that some volume groups are stretched across physical volumes - this is because the recommended maximum disk size per LUN is 2tb, in order to ensure that the disk isn't stretched across LUNs which reduces performance.

It would be good to say in 7003a0 why we are adding a Skyscape off-site backup machine.

What do the 'conflicts' in the commit message of 1890648a refer to? Is there a good reason to keep them in the commit message?

@mattbostock Amended https://github.com/alphagov/govuk_offsitebackups-puppet/commit/cdaf2fa29e694f8dab031009e40ec15fd39cad41 to better the commit message and explain why we're unpacking.

@ajlanghorn: It looks like the issue being worked-around has been fixed: https://tickets.puppetlabs.com/browse/MODULES-5

@mattbostock I'll look further at that, but regardless of that issue, this PR is still valid because the disk layout changes per machine.

@mattbostock We can fast-forward straight to puppetlabs/lvm, which would work around the LVM issue. That's one school of thought. Leaving this open further.

Discussed with @rjw1, and agreed that I'm going to leave this without fast-forwarding puppetlabs/lvm because there are other stories to be picked up, this PR works, and the fast-forwarding can be considered again at a point in future.

That sounds sensible. Can we add a FIXME to the places where we're unpacking lvm::volume to state what the fix is?


feat: LAKE_PKG_URL_MAP

Initial prototype. Overrides are of the form: LAKE_PKG_URL_MAP={"pkg-name": "git-url", ...}.

@semorrison Is the mathlib CI broken on Lean master?  All I did was rebase the PR onto master and it switched from builds-mathlib to breaks-mathlib.

Sorry, combined Mathlib/Lean CI is really struggling at the moment, due to the number of simultaneous breaking changes we have going.
Since we previously got a green tick, let's decide to ignore subsequent failures.


Package path not exported

On the latest version of substreams/manifest, when trying to
import {
  readPackage
} from '@substreams/manifest';

There's an error
node:internal/errors:496
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './Bigint' is not defined by "exports" in node_modules/effect/package.json imported from<EMAIL_ADDRESS>    at new NodeError (node:internal/errors:405:5)
    at exportsNotFound (node:internal/modules/esm/resolve:359:10)
    at packageExportsResolve (node:internal/modules/esm/resolve:695:9)
    at packageResolve (node:internal/modules/esm/resolve:870:14)
    at moduleResolve (node:internal/modules/esm/resolve:936:20)
    at defaultResolve (node:internal/modules/esm/resolve:1129:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:835:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18)
    at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:77:40) {
  code: 'ERR_PACKAGE_PATH_NOT_EXPORTED'
}

Node.js v18.17.1

Can you check if the latest release fixes that?

Still a problem with yarn but problem don't seem visible using pnpm

I'm trying to test with yarn version 3+ now, seems it could be a problem only with yarn v1, it seems it the older yarn has problem with the new exports section of package.json.

After more investigation, it appears it's just a problem with yarn v1 (and maybe older npm version). Package manage pnpm, yarn v3 and npm 10 all works properly.


Calculator - Does not accept underscores in number formats

I apologize for not following the suggested issue format, but I don't think this is an external extension. I couldn't find any other place to report bugs on the base application.

Describe the feature and the current behavior/state.
Currently, the base calculator in Raycast does not support underscores in number formats: (Ex: 5_000_000).

Who will benefit from this feature?
Programmers - This format is very popular in programming languages and sometimes I find myself having to manually replace the underscores with commas when trying to copy/paste values from my code to Raycast.
Any Other info.
I believe this request is pretty self-explanatory, but I'd be happy to reply to any questions! I'm in love with Raycast

Hey @imthath-m! Could you please have a look at the issue? 😉

Hi @psikoi, Sorry for the late response.
We do not have plans to support this now. We'll consider your request for the future.


Memory Leak?

I am not aware of a memory leak, but it has come to my attention that I am not deleting any buffers or unallocating anything.
Everything seems to work for now, but once there are more objects and such, I am willing to bet there will be a memory leak.
Look into it!

This could very well still be a problem. However, I changed how buffers are created, so the likelihood of this happening has decreased.


Does not include processes for applications like 'file explorer', 'cmd','control panel'

I was trying to get a list of all active applications window using this module, but it doesn't show me processes for windows like control panel, command prompt, power shell
OS : Windows 10

Seeing as how this project isn't being maintained anymore, we decided to maintain a fork of it over here. If you want, you can open a issue over there.


Enable a custom builder for WaveFormBar instances when using AnimatedWaveList

Fix for https://github.com/agenthesh/waveform/issues/5

Hey Chris, that's a really helpful PR, thanks for the work!

Thanks, @agenthesh. ETA on the updated package on pub.dev?

Should be up now!

It is. Thanks!


Update local storage capacity isolation feature to GA

update feature to GA

We need to update the following section as well:
https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#local-ephemeral-storage

/assign

@jingxu97 @xing-yang , the Docs Ready for Review deadline for the 1.25 release is eod tomorrow, August 9th 2022
When this PR is ready, please change the state from Draft to Ready for Review

Here's another place that needs an update: https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features

Here's another place that needs an update: https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features

@jingxu97 any update of this reference for the dev-1.25 release?

Here's another place that needs an update: https://kubernetes.io/docs/reference/command-line-tools-reference/feature-gates/#feature-gates-for-alpha-or-beta-features

not sure whether we should update this or not. I don't see any GA features for 1.25 or even 1.24, 1.23 got updated in this page.

this is replaced by new PR https://github.com/kubernetes/website/pull/35989

/remove-area blog release-eng
/remove-language de fr id it ja ko pt uk zh
/remove-sig release