Need Inline Alert variation

It has been shown that the current Alert component does not look good when dropped into a page as an inline alert as the drop shadow causes it to appear floating above the content. The request is to create a new variant of the alert component with different styling.

@rachael-phillips @kybaker Here is the new issue I promised to request an Inline Alert variation. @andybraren could you add a screen shot of what you showed me yesterday as it does a good job highlighting the current problem.

We also have a similar issue for the inline alert style in Integreatly.

For the Integreatly team, we have a fairly immediate need to push through a solution for this as we fully convert Red Hat Solution Explorer to PF4. One proposed solution for this is from @bdellasc. The proposed inline style would be a modification of the existing style to:

Remove the shadow
Remove the background color for the side area and use that color for the icon instead.
Add that same color as a border around the element

Here is a screenshot:

Played around with another idea to throw in the mix:

@kybaker @mcarrano I built out a Sketch file to further show our proposal. Please let me know if this is enough information to get this reviewed and approved or if you need additional information. I also chatted with @maryshak1996 about how this proposal ties in to the notification drawer design ideas, so they match up. The Integreatly team should also be able to provide assistance with the dev side, when/if this is approved.
https://drive.google.com/file/d/1btGgm_pKchb4I5Pbe4BiW3hPHveFpIye/view?usp=sharing

Hi @tiffanynolan I've added this to our roadmap, and after tomorrow I can let you know timeline on this.

Hi @tiffanynolan we have this on the roadmap for our March 22 for our release! Thank you so much, and let me know if you have any questions!

@rachael-phillips Does this have a PF4 designer assigned to it yet? It would be great to have the chance to collaborate with them for any modifications.

It does. @mceledonia is assigned to this issue, and you can find that on the top right of any issue. I have a meeting tomorrow that will determine when we begin design work on this issue.

Hi @tiffanynolan I wanted to update you that after timeline discussions today this will be a variation that gets taken in during our May 5 milestone.

@rachael-phillips Thanks for the updates. Is there a way to reduce the timeline? The Integreatly team is willing to help usher this through the process with stakeholder checkpoints, etc. This is our final element to convert to be fully on PatterFly 4. Even if it's not fully approved, if the direction of the proposed designs is inline with what others are thinking, can we go ahead and use the proposal in our web app? The current inline alert style for PF4 will not work and will likely cause confusion with our users.

Hi @tiffanynolan , I spoke with @mcarrano and @mceledonia and we think it's a fantastic idea to go ahead and move forward with crafting the inline alert variation together. @mcarrano has put together a really helpful template for design proposals here: https://docs.google.com/document/d/1w6O_d6ZSEBoEBgsMMYNUtSMGw73LjEsV3w1pjHtRtVY/edit I'll put a meeting on the calendar to kick off the design conversations, and we can use this template to build it out.

FWIW, I was working with @priley86 on Kiali and they're attempting to use an inline alert on their login screen. I'm not sure if that's an acceptable use of the login component, but since the login component's error message maintains layout on the page even when it isn't shown, if someone drops an inline alert in that area, this is what the default login state looks like.

Hi @mcarrano @mceledonia @rachael-phillips @tiffanynolan. I completed the design doc, echoing mocks for toast notifications, and integrating new material where appropriate. Please let me know if you notice any gaps. Inline alerts design doc

Hi all - Wanted to throw one more use case into the mix here that @jknilans brought up.
This is the case where the alert/notification is inline, and required to be on a white background. The proposed design looks a little odd (since there is no definition around it). This is the proposal that Josh & I noodled around with:

@katierik can you try @bdellasc's proposal in your use case and see if it works for you?  If not this might be another 'variant' we need to consider.

Here is a not-pixel-perfect version where I tried Brian's in the existing openshift ui.

@ncameronbritt Thanks for sharing another use case. Do you feel like this pattern/style meets your needs?

@stacymcauliffe following up on our conversation today about "embedded help." Does the approach outlined here meet the needs you expressed?

@tiffanynolan, I think for inline alerts this pattern works fine for us. For the particular use case I'm working on now, it may not make sense to surface this information as an alert. @stacymcauliffe and I have discussed other possibilities.

@katierik following up here. Did @bdellasc's use case work for your needs?

@mcarrano @rachael-phillips: @srambach is going to go ahead and take this one and add a modifier to the current inline alert to address @tiffanynolan's needs. Right now Integrately only has one remaining component to convert from pf3 to pf4 and they would like to drop pf3 entirely this summer.

@mceledonia is currently assigned to this issue to review/finalize visuals. @srambach can you sync with Michael to make sure you are working with the correct visual designs? Thanks.

Finally got around to checking this out, I think the latest version is looking good. Wanted to check back in regarding the discussion earlier in this issue, were there any conclusions on the support of those use cases?

Small (hopefully quick) update here that I missed before... Icons should be 18px, looks like they're 16px here. I updated a few in the sketch file and everything still works with the current padding shown, just need to update the size of the icon itself!
@bdellasc @srambach

Given the changes to the icon size etc this week based on conversations here and with @mceledonia & @srambach,  I updated the source file InlineAlertsV3.sketch to reflect those changes.
@mcarrano I'd be happy to generate the inline graphics for the design page on the PF site, but I'd just need guidance on any naming conventions we have for those inline images.

:tada: This issue has been resolved in version 2.7.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

Thanks for the offer to update the graphics @bdellasc . But I've already put up a PR here: https://github.com/patternfly/patternfly-org/pull/1138 Do you think the 2 pixels will be noticeable to redo these? Does this change affect all alerts or only the new inline examples?

@mcarrano The spacing between the icon and color band is different and the icon is a bit larger than the ones in those v2 mocks. I'd prefer we update them with the most up-to-date graphics if possible. If you want to send me the images you generated, I can re-create them with my new source doc and post them this morning.

I was messaging with @mcarrano last week and I had posted the updated source file here: https://drive.google.com/open?id=1MZzqkM8wJITbdU1k80muE_ifiL1EPU2F

Thanks for working that out @bdellasc @mcarrano!


Fix wrong data hydration in AddressHydrator

1. Why is this change necessary?
Because $address->setAdditionalAddressLine1 will be used twice, once with the data from address_line1 and once with data from address_line2, the AddressGateway will retrieve invalid data. To put it in a nutshell the address_line1 data will be overridden by address_line2 so we need to use $address->setAdditionalAddressLine2
2. What does this change do, exactly?
Just replace the second usage of $address->setAdditionalAddressLine1() by $address->setAdditionalAddressLine2() in the AddressHydrator's hydrate method.
3. Describe each step to reproduce the issue or behaviour.
When trying to retrieve a customers address by the AddressGateway it will return wrong data in additionalAddressLine1. Instead of the correct value there mistakenly appears the value of additionalAddressLine2.
4. Please link to the relevant issues (if any).

5. Which documentation changes (if any) need to be made because of this PR?

6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[ ] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

thanks for your contribution @barbieswimcrew  +1 :tada: :blue_heart:


Adding unit tests for simple-table-row

Adding unit tests for simple-table-row
Additions

Adding unit tests for simple-table-row

Testing

Run  gulp test:unit:scripts.

Review

@anselmbradford

Checklist

[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated (including the "Unreleased" section of the CHANGELOG)

Looks like simpleTableRowLinks.init(); could go at the bottom of the beforeEach if you wanted to, but it doesn't need too. 👍

@jimmynotjim , can you take a look at this again?

All passing for me. Minor comments but otherwise 👍


Updating Meta learner parameters

It's mentioned in the original article that update's rule is : Phi <--- Phi - Eps * (W - Phi)
why didn't you use Eps and why you used (Phi-W)

The learning rate can be tuned through the optimizer, and the minus sign is
due to the fact that the optimizer goes in the opposite direction to the
gradient (therefore the sign is flipped)
On Sun, Jul 18, 2021 at 12:57 PM majid @.***> wrote:

It's mentioned in the original article that update's rule is : Phi <---
Phi - Eps * (W - Phi)
why didn't you use Eps and why you used (Phi-W)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/gabrielhuang/reptile-pytorch/issues/8, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB3P5RDH4MH27GG5PJZZPLDTYMBZJANCNFSM5ASJ3LIQ
.

Hi author,
I am curious about the "eps" parameter. To perform SGD for the meta step, why don't you use eps?


Web: City API

Add a City controller for API requests allow CRUD operations.

closed a bit too quickly ;)

allow only listing and display of a city; no real means to get any update as of now ... but it's comming ;)

We'll see later if some alteration to this are needed, as of now, it's of no use.


 The pull has to start on an area of the list that is not gray. There shouldn't be any dead zones—pulling down anywhere in the list should work.

This is probably a side effect of the gesture recognizers added to fix #1661.


How to show more shells

N pair shells:          29
shell:           1           1   0.0000000000000000
shell:           2           1   0.0000000000000000
shell:           3           3   0.0000000000000000
shell:           4          12   1.9479855477649999
shell:           5          24   2.7548675809560454
shell:           6          24   2.7548675809560454
shell:           7          16   3.3740099411388700
shell:           8          12   3.8959710955299998
shell:           9           6   3.8959710955299998
shell:          10           6   3.8959710955299998
shell:          11           6   3.8959710955299998
shell:          12          48   4.3558281039897038
shell:          13          48   4.7715706183402382
shell:          14          48   4.7715706183402382
shell:          15          12   5.5097351619120909
shell:          16          24   5.5097351619120909
shell:          17          12   5.5097351619120909
shell:          18          12   5.5097351619120909
shell:          19          48   5.8439566432949999
shell:          20          12   5.8439566432949999
... and 9 more shells
... determined singlet nullspace
... determined pair nullspace
... determined dielectric tensor nullspace
How to show more shells, i want to know the cutoff, thank you very much.
Best wishes
Donglin guo

The cutoff is written at the very top, e.g.,
 READ STRUCTURE AND SETUP CUTOFFS
 ... reading unitcell
 ... min cutoff:       3.14993
 ... max cutoff:       9.95139
 --> rc2 cutoff:      10.00000
 --> rc3 cutoff:      -1.00000
 --> rc4 cutoff:      -1.00000

To get all the pair shells, I recommend to use the script https://github.com/flokno/tools.tdep/blob/main/tdeptools/scripts/ase_get_distance_table.py from tdeptools.
When you run
ase_get_distance_table infile.ssposcar

you will get all pair shells including the elements in a csv file.
Does that solve the issue?

Read infile.ssposcar
... autodetect format vasp for infile.ssposcar
... material: Atoms(symbols='O192Sr64Ti64', pbc=True, cell=[15.58388438212, 15.58388438212, 15.58388438212])
... MIC:                         True
... density (atoms/AA3):      0.085
--> atom volume (AA3):       11.827
--> atom radius (AA):           1.413
--> atoms per  1A sphere:       0.354
--> atoms per  3A sphere:       9.563
--> atoms per  4A sphere:      22.667
--> atoms per  5A sphere:      44.271
--> atoms per 10A sphere:     354.170
... use 1 replicas to see more neighbors
... number of atoms: 320
... unique pairs: ['O-Ti' 'O-Sr' 'O-O' 'Sr-Ti' 'Sr-Sr' 'Ti-Ti']
... first 15 neighbors, first is nearest neighbor:
symbols  distances
0        O-Ti    1.94799
768      O-Sr    2.75487
3840    Sr-Ti    3.37401
4864    Sr-Sr    3.89597
6784     O-Ti    4.35583
9856      O-O    4.77157
16000   Sr-Sr    5.50974
19840    O-Ti    5.84396
23680    O-Sr    6.16007
29824   Sr-Ti    6.46074
32896     O-O    6.74802
35456    O-Ti    7.02356
38528    O-Sr    7.28869
50816     O-O    7.79194
51776    O-Ti    8.03175
... save to 'outfile.distances.csv'
... save unique distances to 'outfile.distances_unique.csv'
yes, it solves my problem, thank you very much.

Great, thank you and happy computing!


QueryParam of Option of scala primitive results in error

Been scratching my head at this one for a bit now after doing an upgrade from the old massrelevance version to the datasift maintained version.
Specifically the error I'm running into is whenever I try to add something like QueryParam("foo") foo: Option[Int] to a resource.
I've done some digging, and similar combinations of QueryParam("foo") foo: Option[java.lang.Integer] and QueryParam("foo") foo: Int work as expected.
This can be replicated by adding the following test/resource to ScalaApplicationSpecIT.scala
--- a/core/src/test/scala/com/datasift/dropwizard/scala/ScalaApplicationSpecIT.scala
+++ b/core/src/test/scala/com/datasift/dropwizard/scala/ScalaApplicationSpecIT.scala
@@ -37,6 +37,15 @@ case class ScalaTestConfiguration(
   def greetOrNotFound(@QueryParam("name") name: Option[String]): Option[List[String]] =
     name.map(greeting.format(_)).map(List(_))

+
+  @GET @Path("/opt-int-param")
+  def greetWithOptionInt(@QueryParam("i") i: Option[Int]): Option[Int] =
+    i
+
   @GET @Path("/option")
   def greetWithOption(@QueryParam("name") name: Option[String]): List[String] =
     name.map(greeting.format(_)).toList
@@ -313,6 +322,28 @@ class ScalaApplicationSpecIT extends FlatSpec with BeforeAndAfterAllMulti {
     assert(result === Success(expected))
   }

+
+  "GET /opt-int-param" should "yield results" in {
+    val fixture = Option(2)
+    val expected = Option(2)
+    val result = request("/opt-int-param").map {
+      _.queryParam("i", fixture.toString)
+        .request(MediaType.APPLICATION_JSON)
+        .get(classOf[Option[Int]])
+    }
+    assert(result === Success(expected))
+  }
+
   "GET /complex_scala" should "yield results" in {
     val fixture: Set[BigDecimal] = Set(BigDecimal(1), BigDecimal(2))
     val expected = 2

I think this has something to do with some weirdness with either type resolution or erasure as by introspecting ScalaParamConvertersProvider during test time the call to getConverter as the parameter type is being listed at type=class scala.Option and the generic type at runtime is scala.Option[java.lang.Object]
Actual error the container spits out
Caused by: org.glassfish.jersey.server.model.ModelValidationException: Validation of the application resource model has failed during application initialization.
[[FATAL] No injection source found for a parameter of type public scala.Option com.datasift.dropwizard.scala.ScalaTestResource.greetWithOptionInt(scala.Option) at index 0.; source='ResourceMethod{httpMethod=GET, consumedTypes=[application/json], producedTypes=[application/json], suspended=false, suspendTimeout=0, suspendTimeoutUnit=MILLISECONDS, invocable=Invocable{handler=ClassBasedMethodHandler{handlerClass=class com.datasift.dropwizard.scala.ScalaTestResource, handlerConstructors=[org.glassfish.jersey.server.model.HandlerConstructor@6097f225]}, definitionMethod=public scala.Option com.datasift.dropwizard.scala.ScalaTestResource.greetWithOptionInt(scala.Option), parameters=[Parameter [type=class scala.Option, source=i, defaultValue=null]], responseType=scala.Option<java.lang.Object>}, nameBindings=[]}']

Unsurprisingly the same behavior is noted with scala Longs and Booleans.

+1
Facing the same issue as well

Essentially, we need reflection compatibility between scala types and java types - there's an open ticket - https://issues.scala-lang.org/browse/SI-7317


Package request: abaddon

Project description
An alternative Discord client made with C++/gtkmm.
Metadata

homepage URL: https://github.com/uowuo/abaddon
source URL: https://github.com/uowuo/abaddon
license: gpl3
platforms: unix, linux, darwin, windows

#213735


[Bug]:  chromadb is missing in 0.4.8 released image

What happened?
When trying to set-up the recently added token authentication with chroma release 0.4.8 we need to make imports from the python chromadb package to set up authentication namely:

chromadb.auth.token.TokenConfigServerAuthCredentialsProvider
chromadb.auth.token.TokenAuthServerProvider
However I suspect the docker image is built without installing chromadb resulting in the module not found error. If provided some guidance I'd be happy to write the fix.

Versions
Using ghcr.io/chroma-core/chroma:0.4.8
Relevant log output
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.config Starting component System
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.config Starting component Posthog
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.config Starting component SqliteDB
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.config Starting component LocalSegmentManager
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.config Starting component SegmentAPI
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.fastapi Server Auth Provider: 'chromadb.auth.token.TokenAuthServerProvider'
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.registry Registering provider: basic
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.registry Registering provider: basic
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.registry Registering provider: htpasswd_file
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.registry Registering provider: token_config
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.registry Registering provider: token
chroma-test_server-1  | 2023-08-31 13:15:27 DEBUG    chromadb.auth.registry Registering provider: token
chroma-test_server-1  | Traceback (most recent call last):
chroma-test_server-1  |   File "/usr/local/bin/uvicorn", line 8, in <module>
chroma-test_server-1  |     sys.exit(main())
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
chroma-test_server-1  |     return self.main(*args, **kwargs)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1078, in main
chroma-test_server-1  |     rv = self.invoke(ctx)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
chroma-test_server-1  |     return ctx.invoke(self.callback, **ctx.params)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/click/core.py", line 783, in invoke
chroma-test_server-1  |     return __callback(*args, **kwargs)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/main.py", line 408, in main
chroma-test_server-1  |     run(
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/main.py", line 576, in run
chroma-test_server-1  |     server.run()
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/server.py", line 60, in run
chroma-test_server-1  |     return asyncio.run(self.serve(sockets=sockets))
chroma-test_server-1  |   File "/usr/local/lib/python3.10/asyncio/runners.py", line 44, in run
chroma-test_server-1  |     return loop.run_until_complete(main)
chroma-test_server-1  |   File "uvloop/loop.pyx", line 1517, in uvloop.loop.Loop.run_until_complete
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/server.py", line 67, in serve
chroma-test_server-1  |     config.load()
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/config.py", line 479, in load
chroma-test_server-1  |     self.loaded_app = import_from_string(self.app)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/importer.py", line 24, in import_from_string
chroma-test_server-1  |     raise exc from None
chroma-test_server-1  |   File "/usr/local/lib/python3.10/site-packages/uvicorn/importer.py", line 21, in import_from_string
chroma-test_server-1  |     module = importlib.import_module(module_str)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
chroma-test_server-1  |     return _bootstrap._gcd_import(name[level:], package, level)
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1006, in _find_and_load_unlocked
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 688, in _load_unlocked
chroma-test_server-1  |   File "<frozen importlib._bootstrap_external>", line 883, in exec_module
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
chroma-test_server-1  |   File "/chroma/./chromadb/app.py", line 6, in <module>
chroma-test_server-1  |     server = FastAPI(settings)
chroma-test_server-1  |   File "/chroma/./chromadb/server/fastapi/__init__.py", line 117, in __init__
chroma-test_server-1  |     self._auth_middleware = self._api.require(FastAPIChromaAuthMiddleware)
chroma-test_server-1  |   File "/chroma/./chromadb/config.py", line 188, in require
chroma-test_server-1  |     inst = self._system.instance(type)
chroma-test_server-1  |   File "/chroma/./chromadb/config.py", line 247, in instance
chroma-test_server-1  |     impl = type(self)
chroma-test_server-1  |   File "/chroma/./chromadb/auth/fastapi.py", line 70, in __init__
chroma-test_server-1  |     _cls = resolve_provider(
chroma-test_server-1  |   File "/chroma/./chromadb/auth/registry.py", line 107, in resolve_provider
chroma-test_server-1  |     return get_class(class_or_name, cls)  # type: ignore
chroma-test_server-1  |   File "/chroma/./chromadb/utils/__init__.py", line 10, in get_class
chroma-test_server-1  |     module = importlib.import_module(module_name)
chroma-test_server-1  |   File "/usr/local/lib/python3.10/importlib/__init__.py", line 126, in import_module
chroma-test_server-1  |     return _bootstrap._gcd_import(name[level:], package, level)
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 992, in _find_and_load_unlocked
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 992, in _find_and_load_unlocked
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 241, in _call_with_frames_removed
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1050, in _gcd_import
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1027, in _find_and_load
chroma-test_server-1  |   File "<frozen importlib._bootstrap>", line 1004, in _find_and_load_unlocked
chroma-test_server-1  | ModuleNotFoundError: No module named "'chromadb"
chroma-test_server-1 exited with code 1

@McDonnellJoseph, thank you so much for spotting this. Let me check the image.

@McDonnellJoseph, I see where the problem is.
In the error message you shared, I noticed the following:
ModuleNotFoundError: No module named "'chromadb"

There is an extra ' in front of chromadb, so I wonder if that could be something in your config that is causing it.

Hello @tazarov ,  I tried running docker compose --file docker-compose.test-auth.yml up --build in a fresh clone of the repo and I'm stuck on the same issue. I agree the issue may be linked to the ' in front of chromadb.

Ok so I found the two problems:
1- we don't need to add the single quotes for the environment variables when python convert the variables to strings it includes the singles quotes raising the module not found error
2- This may be a design choice but I'm not sure about using test-token as an example because the - is not a valid alpha-numeric ASCII symbol.

@McDonnellJoseph, yeah I also noticed 2). For 1) I'll update docs/examples to make it clear.

@tazarov Great! If you agree I'd be happy to make a PR with the changes to the documentation, and an extension to non alpha-numerical characters for the token choice.

@tazarov can we close this issue?

thanks!

In the docs, I don't think there should be any quotes at all for these environment strings in the docker-compose file.
The following gives me an error similar to the original post (I get '"chromadb' instead of "'chromadb"). And when I remove the quotes entirely from the two provider lines, I no longer get the module not found error.
environment:
            - CHROMA_SERVER_AUTH_CREDENTIALS="test-token"
            - CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER="chromadb.auth.token.TokenConfigServerAuthCredentialsProvider"
            - CHROMA_SERVER_AUTH_PROVIDER="chromadb.auth.token.TokenAuthServerProvider"

The same goes for "test-token". The double quotes are counted as part of the credentials, and so on the client the token value that works is actually "\"test-token\""
My working environment variables look as follows
environment:
            - CHROMA_SERVER_AUTH_CREDENTIALS=test-token
            - CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER=chromadb.auth.token.TokenConfigServerAuthCredentialsProvider
            - CHROMA_SERVER_AUTH_PROVIDER=chromadb.auth.token.TokenAuthServerProvider

@brock-cares in docker-compose we work with env vars like so:
    command: uvicorn chromadb.app:app --reload --workers 1 --host <IP_ADDRESS> --port 8000 --log-config chromadb/log_config.yml
    environment:
      - IS_PERSISTENT=TRUE
      - CHROMA_SERVER_AUTH_PROVIDER=${CHROMA_SERVER_AUTH_PROVIDER}
      - CHROMA_SERVER_AUTH_CREDENTIALS_FILE=${CHROMA_SERVER_AUTH_CREDENTIALS_FILE}
      - CHROMA_SERVER_AUTH_CREDENTIALS=${CHROMA_SERVER_AUTH_CREDENTIALS}
      - CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER=${CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER}

And then, we pass along .env file. See here - https://docs.trychroma.com/usage-guide#running-the-server

@tazarov im using the following dockerfile:
version: '3.9'

networks:
  net:
    driver: bridge

services:
  server:
    image: chromadb/chroma:latest
    volumes:
      - ./:/chroma
      # Be aware that indexed data are located in "/chroma/chroma/"
      # Default configuration for persist_directory in chromadb/config.py
    command: uvicorn chromadb.app:app --reload --workers 1 --host <IP_ADDRESS> --port 8000 --timeout-keep-alive 30
    environment:
      - IS_PERSISTENT=TRUE
      - ALLOW_RESET=TRUE
      - CHROMA_SERVER_AUTH_PROVIDER=${CHROMA_SERVER_AUTH_PROVIDER}
      - CHROMA_SERVER_AUTH_CREDENTIALS_FILE=${CHROMA_SERVER_AUTH_CREDENTIALS_FILE}
      - CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER=${CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER}
    ports:
      - 8000:8000
    networks:
      - net

with the following .env file:
CHROMA_SERVER_AUTH_CREDENTIALS_FILE="/chroma/server.htpasswd"
CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER="chromadb.auth.providers.HtpasswdFileServerAuthCredentialsProvider"
CHROMA_SERVER_AUTH_PROVIDER="chromadb.auth.basic.BasicAuthServerProvider"

and I still get the error:
ModuleNotFoundError: No module named 'chromadb'
It does not matter which quotes I use.

hey @lironrisk,
Can you try and remove the following:
volumes:
      - ./:/chroma

If you are not build image from source repo but rather using image: chromadb/chroma:latest then your volume mount will override anything in /chroma which is where chroma normally resides in containers.

@tazarov it worked, thanks!

This will work perfectly without giving authentication error! What is wrong?
chromadb:     image: chromadb/chroma:latest     ports:       - 8292:8000     environment:       - ANONYMIZED_TELEMETRY=False       - IS_PERSISTENT=TRUE       - PERSIST_DIRECTORY=/chroma/chroma       - CHROMA_CLIENT_AUTH_CREDENTIALS=teteokeoken       - CHROMA_SERVER_AUTH_CREDENTIALS_PROVIDER=chromadb.auth.token.TokenConfigServerAuthCredentialsProvider          - CHROMA_SERVER_AUTH_PROVIDER=chromadb.auth.token.TokenAuthServerProvider       - CHROMA_SERVER_AUTH_TOKEN_TRANSPORT_HEADER=X_CHROMA_TOKEN     volumes:       - chromadb_data:/chroma/chroma


Plot the evolution of the jobs running time and performance metrics

In GitLab by @gmontanepinto on Feb 3, 2023, 17:10
Currently we can see the running time and some performance metrics from the previous runs of a particular job in a table. Would it be possible to show also this information in a graph? I'm not sure if this should go in the historical runs view or inside the Performance metrics tab, but it would make it easier to see the evolution of the different metrics in time, particularly in the testing suite runs.
@ jberlin @mcastril

In GitLab by @gmontanepinto on Feb 7, 2023, 11:01
Only COMPLETED jobs should be taken into account.

In GitLab by @gmontanepinto on Feb 7, 2023, 10:24
You're right @mcastril, I completely forgot about the testing suite issue. Anyway, if you think it is feasible, it would be great to have it integrated in the GUI. It is not an urgent thing, so I think we can wait.

In GitLab by @ jberlin on Feb 7, 2023, 10:26
Hi @gmontanepinto , could please provide a sample graph of the data you want to display, maybe you can create a mockup in google spreadsheet with the desired layout, this will speed up the implementation a bit. thanks!

In GitLab by @mcastril on Feb 15, 2023, 16:51
We are still looking for the new GUI developer. New developments like this one will take time.

In GitLab by @gmontanepinto on Feb 7, 2023, 11:00
It would be something like that:

It shows the run time for every start date of a particular job. I took the data from the historical run view of the SIM job from experiment t06q.

In GitLab by @mcastril on Feb 3, 2023, 20:28
I agree it's interesting, it's a good idea, @gmontanepinto.
Note that, concerning the Testing Suite, I had already created this issue in the corresponding project:
https://earth.bsc.es/gitlab/es/testing_suite/-/issues/32
I think this is something that you, Eric, Alejandro or Genís could implement in the testing suite without much effort. In the GUI it could take some more time.


Support multiple context states for RequestsWrapper

Motivation
Necessary for use in OpenMetrics base class where there are different configurations for each endpoint
Additional Notes
https://github.com/DataDog/integrations-core/pull/5249#discussion_r359741180
https://github.com/DataDog/integrations-core/pull/5249#issuecomment-567597707

The use case is so niche that we'll do it where needed instead https://github.com/DataDog/integrations-core/pull/5414


[Backport 1.20] etcd subcommands

Proposed Changes

Backports the etcd subcommand functionality found in mastser to the release-.120 branch.
Types of Changes

Verification

Linked Issues

Further Comments

This is only relevant for 1.21 and newer.


rectified_src assert erroneously

I_source is at a low level. When configuring sourcecfg [0] from 0 to 1 (for example, configuring SM=EDGE0), there will be an error flip. How to handle this situation

It seems that the AIA-Spec pointed out this issue, but did not propose a solution

I @Reportcap! Thanks for reaching out! I am not sure I understand your question. Could you rephrase?
Is something related to this? https://lists.riscv.org/g/tech-aia/topic/rectified_input_value/106025837
Please check our solution in the new version of the RTL. If you have any question let me know!

The problem has been resolved

Great!


[1.9.1] Train 163

This train includes the following pull requests:
#1480 Use metronome 0.2.3
#1536 backport spartan bind ip blacklist and forward zones

Annoyed by flakiness of test_mesos.test_if_ucr_app_runs_in_new_pid_namespace (https://jira.mesosphere.com/browse/DCOS_OSS-862).

The upgrade test failure is supposedly as of a timeout issue, created https://jira.mesosphere.com/browse/DCOS_OSS-1114.

How come my commits show up in the history but the files changed don't reflect them at all?

How come my commits show up in the history but the files changed don't reflect them at all?

I have no idea. @adam-mesos have you seen that before? I used the trainadd alias from https://wiki.mesosphere.com/pages/viewpage.action?pageId=104169500&focusedCommentId=109609475#comment-109609475.

The upgrade test failed again: https://teamcity.mesosphere.io/viewLog.html?buildId=653908 (restarting).

Kicking off https://github.com/dcos/dcos/pull/1536 the train (had already landed, see that PR discussion for detail). What's left is just https://github.com/dcos/dcos/pull/1480. Closing this train PR now and going ahead with merging https://github.com/dcos/dcos/pull/1480 directly. It is confirmed to not break downstream.


update backend add user mutation

BACKEND PULL REQUEST
Related Issue

Part of #5945 - Adding two new parameters to addUser mutation

Changes Proposed

Add accessAllFacilities and facilities to the userInput object
Add userInput to the addUserToCurrentMutation

Additional Information

There will be 2 more PRs to resolve the rest of the work, Front end changes to use the new parameters and then a cleanup.

Testing

These changes should not impact existing functionality.  Deployed in Dev!

Creating new organization, adding an org admin, adding new user, and reprovisioning deleted user all works as expected.

Will the cleanup involve removing the part from your other PR where we use find users with the q parameter?

Will the cleanup involve removing the part from your other PR where we use find users with the q parameter?

Yes it will! It'll also clean up tests and improve test coverage 😄


nixos/klipper: Add Klipper firmware options

Description of changes
This adds firmware options to the klipper service. It is possible to only build the firmware for the microcontroller or even have NixOS flash it automatically. Also, two helper tools are added:

klipper-genconf: Generates the necessary firmware config. Internally it just calls make menuconfig
klipper-flash: Enables flashing of the built firmware to the microcontroller. For now, this only supports avr, stm32 and lpc176x boards. The other boards require additional tools which have to be built as well which fails as klipper.src is only readonly. Help would be here appreciated. The other firmwares should™ be supported with the enableFlashing option.

Unfortunately, I miss the required hardware to test all the firmwares.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@lovesegfault @zhaofengli

@lovesegfault @zhaofengli Anythig I should do, to get this merged? Should I remove all the scripts for now and only limit it to the klipper-firmware?

I had forgotten about this, thanks for working hard on it @vtuan10 :)


how to get complete disk-cache rather than the simple disk-cache

my code:
const browser = await puppeteer.launch({       args: ['--no-sandbox', '--disable-setuid-sandbox', '--disk-cache-dir=./dcache'],   });
const page = await browser.newPage();
await page.goto('https://google.com', {     waitUntil: 'load' });
I get disk-cache like this：

but I realy want something like this:

so how can I get the complete disk cache ?

Hey, it looks like this would be out of scope for Puppeteer and not something we support currently. Check out Chromium flags reference to see if some flags do what you need https://peter.sh/experiments/chromium-command-line-switches/


KV Stor prefix clash

3 Stores have kv store prefix clashing.

I think this issue is closed, I have linked the PR, please check and close.

I think this issue is closed, I have linked the PR, please check and close.


Add explicit classifications for supported python versions

Many tools such as caniusepython3 rely on classification to determine library support.

None taken - I did not verify each version. I referenced their documentation of supported versions:
github.com/python-intelhex/intelhex/blob/master/Readme.rst#supported-python-versions

That specific line was last changed before Python 3.7 was released :)
There's no reason to assume the package won't work with 3.7, just thought I'd ask...


[dev.icinga.com #10587] setup both release and snapshot repositories by default

This issue has been migrated from Redmine: https://dev.icinga.com/issues/10587
Created by vkhatri on 2015-11-10 06:22:57 +00:00
Assignee: vkhatri
Status: Assigned
Target Version: (none)
Last Update: 2015-11-10 06:22:57 +00:00 (in Redmine)

I am yet to start working on it, but i think it will be quite useful.
`release` repo will be enabled and `snapshot` repo will be disabled by default.
Each package (icinga2, classic ui, web2 ..) can have an attribute to use `release` or `snapshot` repo which will control --enablerepo & --disablerepo for `package` resource as an override to `node['icinga2']['build_type']`.
I am not entirely sure how it will be played out for `apt`, i am going to give it a day or two before releasing `v2.7.0`.

Not a requirement, leaving it for later.


How to add embeddings?

Sorry, I'm not that familiar with the technology, but I want to add some embeddings for my negative prompts through this: https://huggingface.co/Cordeliya/animefull-latest/tree/main
I am not exactly sure where the embeddings folder is, so that I can put these files there. Any help would be greatly appreciated.

My question is: I put the embeddings into the embeddings folder in Google Drive and restarted Stable Diffusion, but for some reason they are not loading. I also hit the refresh button. how do I add embeddings such as easy negative? I have multiple Colab acounts and for some reason only one embedding loaded. The other accounts do the same thing but do not load.

put them in the folder sd/stable-diffusion-webui/embeddings

I put the embeddings into the embeddings folder in Google Drive and restarted Stable Diffusion, but for some reason it is not loading. I also hit the refresh button.
Just put them in the Google Drive folder, just like the model, right?
I have multiple Colab accounts, but for some reason only one account loaded embeddings. The other accounts are doing the same thing but not loading.

When I set Model_Version: to 1.5, embedding loaded. v2.1-768px does not load.

The embedding must be compatible with the model

The models I have in my Drive folder are exactly the same except for the initial model. When the initial model was v2.1-768, embedding was not installed, when the initial model was 1.5, embedding was installed.


Separate identityDb by tenant

It is possible to separate the Identity in another database per tenant.
Thank you
ApplicationDbContext : MultiTenantIdentityDbContext

Yes, all you need to do is have each tenant have a connection string to it's own database then in your DbContext configuration have it use the connection from the tenant info. Technically you don't even need to use the "MultiTenant" db contexts here since they include functionality intended for shared-database (and hybrid) scenarios.
Take a look at this part of the docs about separate databases per-tenant.


Check if APIRule CRD is installed, otherwise stop reconciliation for EventMesh

Description
Changes proposed in this pull request:

Check if APIRule CRD is installed, otherwise stop reconciliation for EventMesh

Related issue(s)

https://github.com/kyma-project/eventing-manager/issues/95

/cla-recheck

/cla-recheck


getting error (0 , _immutable.isImmutable) is not a function

Trying to use this library to generate code blocks inline in StoryBook, however when I try to call jsxToString(component) i'm getting the error
(0 , _immutable.isImmutable) is not a function

I checked the immutable-js repo and there does seem to be a similar issue:
https://github.com/facebook/immutable-js/issues/1165
based on a suggestion there i was able to change the line in jsx-to-string/lib/index.js [69]
from if ((0, _immutable.isImmutable)(item)) { to if ((0, _immutable.Iterable.isIterable)(item)) { and it works...
is this an issue with this library? Or is it something with immutable 4.0-rc2? The _immutable object definitely doesn't have an isImmutable function as stated. Is there something better than this semi-hacky fix? Thoughts?

let me look into this. sorry for the delayed response.

could not reproduce this. I'm closing this bug. I've updated to latest immutable though. feel free to reopen if you are still facing this.
https://github.com/grommet/jsx-to-string/releases/tag/v1.4.0


Tests Refactoring

Changed code directory to backend so it wouldn't override the code standard import in tests and refactored the tests to run with the pytest command

This PR Addresses #34


Publish minor release

Hey @puranjayjain,
If you are happy with the changes I've made (package.json is updated automatically by apm, that's why I reverted it to 0.4) then I'll leave the first apm publish minor up to you. It will probably take some time for the PR on language-gfm to go through, but in the meantime you can focus on the remaining issues here.

resolved in latest release


Outputs only between 0 and 1

I'm trying to work out if this is intended behaviour, whatever data I train a network with, the output is always between 0 and 1, even if that does not match the training data.
Please see #1 as further explanation.
Have I misunderstood the scope of the networks?  Is this behaviour expected?  If I needed a network which was able to output a float of arbitrary size, is this possible with this package?
Many thanks

Hey, it's because this package at the moment uses the sigmoid function by default which is only capable of returning values in the range of 0 <= x <= 1. You can find more about the sigmoid function here.
I was thinking about adding more functions and make it optional which should be used, also a different could be set for each layer. Maybe it's the right time to add these features!

Hey @Fontinalis, thanks for the quick response.  Is this something you're looking to add in the near future?  I wish I could contribute, but I don't know enough about the NN methods involved!


U/jowilco/theme fix

Added support for detecting the docs.microsoft.com theme and cleaned up indentation

Docs Build status updates of commit b7e0f68:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

globalization/keyboards/kbda1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbda2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbda3.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdadlm.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdal.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarme.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmph.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmty.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmw.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdaze.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdazel.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdazst.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbash.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbe_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbe_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbene.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbgph.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbgph1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbhc.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdblr.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbr_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbr_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbu.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbug.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbulg.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdca.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcan.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcher.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcherp.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcr_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcr_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdda.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddiv1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddiv2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddv.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddzo.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdes.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdest.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfa.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfar.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfc.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi1_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi1_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfo.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfr.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfthrk.html
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b301eab:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

globalization/keyboards/kbda1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbda2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbda3.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdadlm.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdal.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarme.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmph.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmty.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmw.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdaze.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdazel.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdazst.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbash.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbe_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbe_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbene.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbgph.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbgph1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbhc.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdblr.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbr_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbr_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbu.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbug.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbulg.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdca.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcan.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcher.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcherp.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcr_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcr_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdda.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddiv1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddiv2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddv.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddzo.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdes.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdest.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfa.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfar.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfc.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi1_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi1_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfo.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfr.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfthrk.html
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit d71f179:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

globalization/keyboards/kbda1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbda2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbda3.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdadlm.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdal.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarme.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmph.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmty.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdarmw.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdaze.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdazel.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdazst.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbash.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbe_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbe_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbene.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbgph.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbgph1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbhc.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdblr.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbr_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbr_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbu.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbug.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdbulg.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdca.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcan.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcher.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcherp.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcr_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcr_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdcz2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdda.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddiv1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddiv2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddv.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbddzo.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdes.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdest.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfa.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfar.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfc.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi1_1.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfi1_2.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfo.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfr.html
:white_check_mark:Succeeded
View

globalization/keyboards/kbdfthrk.html
:white_check_mark:Succeeded
View

This comment lists only the first 50 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Fix: clear important beats after deleteMonitor

Closes #433
So uhhh... apparently foreign keys have not been turned on this whole time 😂
Might be why some people are seeing bigger database file than expected.

I believe foreign key is enabled by default.
If not, I may need to review all patch sql files. It may have a chance that it turned foreign key off and not turn it back on.

Did a quick search and the old patch files looks fine. I guess I'll check again later with a clean database to make sure I didn't somehow break the config before.

Okay tested FK delete cascade works on a clean database. I must have broke it during development. Do you think it's safer to just leave that line in anyway?

To minimize future problems, applications should set the foreign key enforcement flag as required by the application and not depend on the default setting.

https://www.sqlite.org/pragma.html#pragma_foreign_key_check
Just read the official doc, they actually suggest that it should not depend on the default setting, so it is good to keep.


Skillsme Hackathon invites you to be our judge with great developers worldwide

Hi there,
Skillsme has been running an Online Hackathon for the past 2 weeks and we are now at a stage where we need experienced judges to rate the codes quality. As a result, Skillsme would like to invite some of the most experienced and skillful developers from the community to share some of your thoughts and opinions to help us judge. You are invited because we believe you are in the best position to give critical reviews which will lead to a more accurate rating which will determine who the winner is. Skillsme believe having a wide range of experience developers judging our hackathon will more accurately reflect the portfolio and pick the correct winner.
If you are interested, you can sign up using the below link as a new user or sign in if you already have an account, add 'Hackathon Portfolio' to your topic list and give your reviews and ratings to our Hackathon Participants. The rating will start on 0:00 NZDT to the 21st of April.
https://beta.skillsme.co.nz/sessions/signin
Our hackathon participants comes from six different time zones and have spent 14 days on their projects. If you can share your opinions among other great developers all around the world to the participants' works, it would mean a lot to them and this Hackathon.
Looking for your participation, and see you soon!
If you have any question, contact us through our official Facebook page
https://www.facebook.com/skillsme.nz
or reply to this email directly. We will be happy to help you.
Sincerely,
Skillsme Team

Thanks for the invite but unfortunately I don’t have enough spare time currently.


Distribution function - must it be async?

I'm writing a bunch of unit tests and trying to do as much stuff that is not discord related as I don't have a good mocker for discord functionality. A good thing to test would be this distribution function and looking at it I don't see a good reason for it to be async as it does not call any discord stuff inside.
https://github.com/Stellar-Quest-Lumenauts/fantastic-goggles/blob/431e64404cb6e113e9e6e9e9a27b10e6b60b263f/helpers/discord.py#L40-L88
Can we make it synchronous so it's simpler to unit test? @Smephite, I think that was your code originally?

I agree with you. I don't see why this shouldn't be sync

I made it sync and refactored it just a little bit to make it easier to test in #25


UAT (latest master) color theme is missing

Describe the task
The color theme seems to be missing

Expected behavior

[x] The color theme should work fine

This issues is resolved and ready to test

This is complete.


restore-file can't restore deleted files in forks

I wasn't able to undo the deleted file, the console reported this 404:
https://github.com/sindresorhus/refined-github/new/linkify-code?filename=source/features/format-conversation-titles.tsx

Originally posted by @fregante in https://github.com/sindresorhus/refined-github/pull/3409#issuecomment-666318532

This is probably because that 404 URL should be this instead:
- https://github.com/sindresorhus/refined-github/new/linkify-code?filename=source/features/format-conversation-titles.tsx
+ https://github.com/kidonng/refined-github/new/linkify-code?filename=source/features/format-conversation-titles.tsx

Needs to be done like this
https://github.com/sindresorhus/refined-github/blob/81c11b9f1ac60a307591c88fb560bf56f725138c/source/features/enable-file-links-in-compare-view.tsx#L19
Make it its own function and export it?


Restructured train loop to minimize overhead by enabling "load_next_batch" to be overlapped

On a 1B model:

Original code: 13.9ms gap, ~594ms per step (https://xprof.corp.google.com/trace_viewer/rwitten-5603190285380189891)
New: 3.8ms gap, ~594ms per step (https://xprof.corp.google.com/trace_viewer/rwitten-7299847913837273264)

So we lower overhead by 72% (13.9-3.8)/13.9 but if you have a big step time (say 5 seconds) is impact overall is small (.2%).

Somehow it merged without closing this?


When the Estimate and Invoices dialog is reduced in width the input fields on the right disappears

When the Estimate and Invoices dialog is reduced in width the input fields at the right disappears at some point. We should let those widget go more in the left.

Source code where the error is located: https://github.com/BananaAccounting/InvoicesApp/blob/main/src/ui/WdgSettings.qml


Missing kuberenets module requirement

In GitLab by @arisilon on Oct 28, 2019, 16:44

In GitLab by @arisilon on Oct 28, 2019, 16:47
mentioned in commit 8f4de15954d768ea295b1261107e717410e290d1

In GitLab by @arisilon on Oct 28, 2019, 16:50
mentioned in commit 1187b8ec23dda7a3be5bdf96f2c19c7ac3947d8a

In GitLab by @arisilon on Oct 28, 2019, 16:59
closed


LCSC part numbers?

Hello,
Do you by chance have LCSC part numbers for this board? Some of them are easy to figure out, but I started trying to find an equivalent part for the Hirose FFC connector and I realized I should just ask first.
Thanks!

check https://github.com/will127534/OneInchEye/blob/main/bom/BOM_JLCSMT.csv#L11
They are mostly the same.
I haven't send it to JLCPCB yet so don't have any part numbers to share yet.

Actually I probably want to open this until I have the design send to JLCPCB

Okay thanks!

Ah interesting that the Hirose connector is marked as discontinued on LCSC with no stock indicated.
https://www.lcsc.com/product-detail/FFC-FPC-Connectors_HRS-Hirose-FH12A-22S-0-5SH-55_C3168813.html
https://jlcpcb.com/partdetail/Hirose-FH12A_22S_0_5SH_55/C3168813

I guess you can swap it to a bottom-contact type:
https://www.lcsc.com/product-detail/FFC-FPC-Connectors_HRS-Hirose-FH12-22S-0-5SH-55_C597981.html
But then you will need a FPC cable with one contact on the top and the other on the bottom of the FPC

Some thing like this

Okay great, thank you for finding a suitable part! I have seen cables like that around, shouldn't be too much trouble thanks.

Hi @will127534 ,
speaking of the BOM and the parts - how do you solder the image sensor?
Do you let PCBWAY, JLCPCB or other manufacturer take care of that or do you solder the IMX585 IC yourself?

@phodina I use low temperature paste and heat the board from the bottom with either heatgun or IR PCB pre-heater.

Closing the issue with the updated design files


Non-existing country code should give clearer error

When I use a wrong country code in the get function I get a cryptic 404 HTTP error and I think it would be helpful to give a more descriptive error, so that users know what they made wrong.
GADM.get("GER")

HTTP.Exceptions.StatusError(404, "GET", "/gadm/gadm4.1/gpkg/gadm41_GER.gpkg", HTTP.Messages.Response:
"""
HTTP/1.1 404 Not Found
Date: Thu, 01 Jun 2023 07:29:33 GMT
Server: Apache/2.4.52 (Ubuntu)
Content-Length: 282
Content-Type: text/html; charset=iso-8859-1

""")

Instead of this error I would have hoped for an error stating.
ArgumentError: Country code "GER" not found, please provide standard ISO 3 country codes.

Thank you for reporting the issue @felixcremer. Feel free to submit a PR if you have the time, otherwise we will try to address the issue by next month.


FMRadio stream doesn't work

🐛 Bug Report
Good day!
I'm trying to implement fm radio based on your library.
In the Play method, I pass the link to the radio station.
in this case, the State = Paused.
If call the PlayPause method, the State changes to Buffering, but is not reproduced (nothing is buffered)
This does not work, but what’s most interesting is on devices with iOS 12.x (tested on real devices and a simulator). On a device with pre-installed beta iPadOS (iOS 13), everything works fine.
Version: 0.8.4
Platform:

[ X] :iphone: iOS
[X ] :monkey: Xamarin.Forms

Can you add the steps to reproduce and a test url?


feat(fw): verkle t8n post state verification

🗒 Description
Creating a draft PR here for visibility and discussion.
This implements a method for checking the post state of the verkle tree after t8n execution.
Currently it calls an additonal subcommand: evm t8n verkle, responsible for generating the verkle tree keys for account addresses and storage slots. These can be used for each account to generate an expected verkle post state using our existing post alloc, and compared against the actual vkt from t8n execution.

For example, once we have the account address key:
evm t8n verkle 0x0000000000000000000000000000000000000100
> 0x31b6...6300   # address

We can create the account balance, nonce and code hash keys, by adding 0x01, 0x02 and 0x03 respectively to get their keys for the vkt:
> 0x31b6...6301  # balance
> 0x31b6...6302  # nonce
> 0x31b6...6303  # code hash

For account storage keys we simply add the storage slot to the sub-command:
evm t8n verkle 0x0000000000000000000000000000000000000100 0x01
> 0x31b6...6341   # storage slot 1

Using these keys we can create our own vkt representation, adding there appropriate values from the post alloc. Note the address value is Hash32(0). Numerical values are in little endian (balance/nonce). The code hash value is the keccak256 of the account code bytes.

Currently this method is not ideal - but it does work. As we call the subcommand around 260 times it takes around 120s to fill a single test. One proposed solution is update the subcommand, passing the entire post alloc to the subcommand - expecting an entire vkt conversion back. More comments are below.
🔗 Related Issues
N/A
✅ Checklist

[ ] All: Set appropriate labels for the changes.
[ ] All: Considered squashing commits to improve commit history.
[ ] All: Added an entry to CHANGELOG.md.
[ ] All: Considered updating the online docs in the ./docs/ directory.
[ ] Tests: All converted JSON/YML tests from ethereum/tests have been added to converted-ethereum-tests.txt.
[ ] Tests: Included the type and version of evm t8n tool used to locally execute test cases:  e.g., ref with commit hash or geth 1.13.1-stable-3f40e65.
[ ] Tests: Ran mkdocs serve locally and verified the auto-generated docs for new tests in the Test Case Reference are correctly formatted.

The question now that pops up - how do we best optimize this?

We update the evm t8n verkle subcommand to take in our post allocation as an input, where geth creates and returns our expected verkle tree instead of us creating it manually. This would solve the runtime issue. We'd only call the subcommand once.

We do 1), but entirely within t8n and not an additional subcommand. Essentially we'd provide additional optional flags --input.postAlloc and --output.postVkt. We'd provide the input post alloc on our last t8n call. T8n would do the same conversion above and provide it as an output.

Can t8n provide alloc alongside the vkt during each transition? If so, why don't we use the alloc here. Maybe it could be prone to errors?

If the long term plan is to use the pedersen hash in python within EEST, then the current implementation style would be the way forward. Although, 1) or 2) using the latter in EELS seems more optimal.

CIFO: #507
All relavent changes are included there. Most code is however removed, as we are going to verify the post state vkt slightly differently.


The file can't open

well, I have auto hotkey installed because the program was a script and wasn't compelled, so when I tried to open it to compile it into a .exe the file couldn't oppen

https://github.com/HiDe-Techno-Tips/Mouse2Gamepad_for_Yuzu/releases/latest/download/Mouse2Gamepad_for_Yuzu.zip
The above link will download the zip file that contains the precompiled exe file. Download it and then follow the steps found in the below link:
https://github.com/HiDe-Techno-Tips/Mouse2Gamepad_for_Yuzu#how-to-use


plugins/nvim-lsp: add java language server

Add java language server.
This throws an error in my config:
Error executing vim.schedule lua callback: ...rapped-0.9.1/share/nvim/runtime/lua/vim/lsp/handlers.lua:122: bad argument #1 to 'ipairs' (table expected, got nil)
stack traceback:
    [C]: in function 'ipairs'
    ...rapped-0.9.1/share/nvim/runtime/lua/vim/lsp/handlers.lua:122: in function 'handler'
    ...eovim-unwrapped-0.9.1/share/nvim/runtime/lua/vim/lsp.lua:1057: in function ''
    vim/_editor.lua: in funvtion <vim/_editor.lua:0>

But the language server still works and I don't think it's related to the PR.

I've updated my branches but GitHub is having problems syncing prs right now: https://github.com/orgs/community/discussions/16351#discussioncomment-6114418


transfer to couchdb broken

I added a flag -useCouchdb to MigrationApp which sets usecouchdb = true in MigrationHelpers.
Then I ran:
java -jar target/xmltoldmigration-0.1-jar-with-dependencies.jar -useCouchdb

which now breaks with:

SLF4J: Failed to load class "org.slf4j.impl.StaticLoggerBinder".
SLF4J: Defaulting to no-operation (NOP) logger implementation
SLF4J: See http://www.slf4j.org/codes.html#StaticLoggerBinder for further details.
creating directory: tbrc-jsonld/
creating directory: tbrc-jsonld/places
converting 55230 place files
Exception in thread "main" java.lang.ExceptionInInitializerError
at io.bdrc.xmltoldmigration.MigrationHelpers.modelToOutputStream(MigrationHelpers.java:254)
at io.bdrc.xmltoldmigration.MigrationHelpers.modelToFileName(MigrationHelpers.java:318)
at io.bdrc.xmltoldmigration.MigrationHelpers.convertOneFile(MigrationHelpers.java:409)
at io.bdrc.xmltoldmigration.MigrationApp.migrateOneFile(MigrationApp.java:126)
at io.bdrc.xmltoldmigration.MigrationApp.lambda$migrateType$0(MigrationApp.java:146)
at java.util.stream.ForEachOps$ForEachOp$OfRef.accept(ForEachOps.java:184)
at java.util.Spliterators$ArraySpliterator.forEachRemaining(Spliterators.java:948)
at java.util.stream.AbstractPipeline.copyInto(AbstractPipeline.java:481)
at java.util.stream.ForEachOps$ForEachTask.compute(ForEachOps.java:291)
at java.util.concurrent.CountedCompleter.exec(CountedCompleter.java:731)
at java.util.concurrent.ForkJoinTask.doExec(ForkJoinTask.java:289)
at java.util.concurrent.ForkJoinTask.doInvoke(ForkJoinTask.java:401)
at java.util.concurrent.ForkJoinTask.invoke(ForkJoinTask.java:734)
at java.util.stream.ForEachOps$ForEachOp.evaluateParallel(ForEachOps.java:160)
at java.util.stream.ForEachOps$ForEachOp$OfRef.evaluateParallel(ForEachOps.java:174)
at java.util.stream.AbstractPipeline.evaluate(AbstractPipeline.java:233)
at java.util.stream.ReferencePipeline.forEach(ReferencePipeline.java:418)
at java.util.stream.ReferencePipeline$Head.forEach(ReferencePipeline.java:583)
at io.bdrc.xmltoldmigration.MigrationApp.migrateType(MigrationApp.java:146)
at io.bdrc.xmltoldmigration.MigrationApp.main(MigrationApp.java:162)
Caused by: java.lang.NullPointerException
at org.apache.jena.query.ARQ.isTrue(ARQ.java:633)
at org.apache.jena.riot.system.RiotLib.(RiotLib.java:63)
... 20 more

It may be easier for you to debug this than for me. I didn't realize this area was being changed.
I thought that the usecouchdb was so you could do conversion testing without having to wait for couchdb to be populated -- it does run rather faster with populating couchdb.

I'm surprised the .jar file worked before, did it really? I've never managed to make the .jar file work, for reasons that seem to be linked with some black magic that needs to be done when using jena with maven... Anyway, I advise running mvn exec:java in the meantime. I'll try again to figure out how to build a .jar with jena, but it will require a few hours... I'll do that tomorrow

I can confirm that the .jar never worked for me, I tried by getting back to commit 4abf805 for instance and got the same error... can you tell me if you have it too?

Yes I can confirm that running the jar fails with the NPE at ARQ.java:633.
I'm lacking sufficient chops to know how to run:
mvn exec:java -Dexec.mainClass=io.bdrc.xmltoldmigration.MigrationApp

with the command line arg -useCouchdb.
I imagine there's a way to do that. I think having the option of running the migration with and without uploading to couchdb is sensible.
Also I need a walk-through to learn what:
mvn exec:java -Dexec.mainClass=io.bdrc.xmltoldmigration.MigrationApp

does. It runs java as follows so the myriad dependencies are being class loaded via some maven feature that I have no experience with:
/Library/Java/JavaVirtualMachines/jdk1.8.0_102.jdk/Contents/Home/bin/java -classpath /usr/local/apache-maven-3.2.3/boot/plexus-classworlds-2.5.1.jar -Dclassworlds.conf=/usr/local/apache-maven-3.2.3/bin/m2.conf -Dmaven.home=/usr/local/apache-maven-3.2.3 org.codehaus.plexus.classworlds.launcher.Launcher exec:java -Dexec.mainClass=io.bdrc.xmltoldmigration.MigrationApp

I'd guess that something(s) that's getting packaged in the xmltoldmigration-0.1-jar-with-dependencies.jar is a different version than what's referenced via the maven class loading.
The NPE is happening in MigrationHelpers when preparing the PrefixMap for the first Place document:
    DatasetGraph g = DatasetFactory.create(m).asDatasetGraph();
    PrefixMap pm = RiotLib.prefixMap(g);

So it really seems actually disturbing that code way inside a chain of calls from MigrationApp through MigrationHelpers is failing when invoked via main in the jar vs presumably the same sequence of calls from the mvn exec:java invocation.

Well, we're at the same point then, I'll spend a day or two understanding maven or maybe finding an alternative...


let's add the draw-dino guide that teaches people how to submit PRs

https://draw-dino.hackclub.com is a very valuable resource for beginners.
Right now there's no way to know about it unless someone shares it with you directly.
I recommend adding it to "START HERE"
call it a DRAW-DINO
Submit your first Pull Request to GitHub

done!


Problem: the demo script in README does not work

Solution: use the correct tx id with transfer step
Issues This PR Fixes
Fixes #449

What do you think about defining bdb_root_url = 'https://example.com:9984' via localhost? - people would be able to try the script out locally, without any modifications.

I see your point but not all of them use it locally. Some want to use it with the test network, so I think something generic that tells you to change it, is a good starting point.

What do you think about both using localhost and adding an additional note about it?

I can put a link to the docs


docs: update Github pages for V2.0 release

Feature or Bugfix

Feature

Detail
Updating documentation for V2.0 release

update deploy to AWS guide
update code walkthrough
new how to develop modules section

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

@maryamkhidir we need to update the existing frontend documentation to show the changes made with the modularization work. In particular the page that need changes is the one in pages/code. It needs to show the current code structure, but you can reuse some elements from the previous


Question about boundary conditions for ex3

Dear developers,
could you please comment how to specify real boundary conditions for ex3.
I don't understand what happened in this lines,
GridFunction x(fespace);
VectorFunctionCoefficient E(sdim, E_exact);
x.ProjectCoefficient(E);

thank you.

Hi @skarden86,
The last line takes the boundary conditions specified in the C-function E_exact (see https://github.com/mfem/mfem/blob/master/examples/ex3.cpp#L212-L226) and interpolates them in the finite element function x.
Since fespace is a Nedelec space, its degrees of freedom (entries in x) correspond to dot products with tangential vectors, so the above corresponds to imposing conditions on E.n.
Hope this helps,
Tzanio

Hi Tzanio,
thank you.
1)
I still don't understand, if I need to specify for example periodic or tangential conditions what shoul I do?
2)
Am I right that  x.ProjectCoefficient(E)   calculate E_exact on every point from x?
Denis


Polls: add "button" class to the button

Looks better than before

Pics for comparison?

Sure.
I'm not asking for a license because I don't think your change is big enough to be copyrightable; feel free to dispute blah blah blah.

u people just merged a PR of permalocked user

@Lord-Haji you aren't the first person to do that, sorry :(


Get class name with prefixed enclosing classes

Small improvement for formatting expected types. Instead of using Class.simpleName() method, we traverse enclosing classes to build class name.
Let's consider the following class structure:
class Outer {
    static class Inner {}
}

For e.g. type mismatch exception on Inner class we were reporting required type as "Inner". This improvement renders required type as "Outer.Inner" instead.

Codecov Report

Merging #104 into master will increase coverage by 0.06%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master     #104      +/-   ##
============================================
+ Coverage     93.51%   93.58%   +0.06%
- Complexity      294      296       +2
============================================
  Files            33       34       +1
  Lines           694      701       +7
  Branches         84       85       +1
============================================
+ Hits            649      656       +7
  Misses           25       25
  Partials         20       20

Impacted Files
Coverage Δ
Complexity Δ

...dlers/MissingRequestParametersWebErrorHandler.java
90.9% <100%> (ø)
9 <0> (ø)
:arrow_down:

...java/me/alidg/errors/handlers/ClassNameHelper.java
100% <100%> (ø)
2 <2> (?)

...g/errors/handlers/TypeMismatchWebErrorHandler.java
100% <100%> (ø)
8 <0> (ø)
:arrow_down:

...errors/handlers/ResponseStatusWebErrorHandler.java
95.77% <100%> (ø)
30 <0> (ø)
:arrow_down:

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 5ccf06e...2fded9d. Read the comment docs.

@zarebski-m Thank you 🙏. I've added a few lines of Javadoc.
Merging Now.


Sent buffer overflow

If the back-end is not responding or is responding very slow, the SENT_BUFFER can grow above the max buffer size limit. This can cause a situation when the restored buffer has more than MAX_BUFFER_SIZE elements.

:shipit:


Windows bootstrap fails if there are spaces in the path

Looks like its the .npmrc option that causes the issue.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use electron-prebuilt and electron-packager instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


Fix syntax error in conformance doc

When merging #326 a syntax error was introduced, which I have now corrected. @davidhassell would you mind cross-checking? Artefacts will be stored in the associated PR.

Thanks, @erget. I'm not sure what was introduced before, but adding the label looks good to me.

Hi @davidhassell yes, I should have described better what I was trying to fix. Without a label it wasn't being recognised as a header - one saw the === as text rather than as a modifier of the chapter heading. I've checked the new build artefacts and with the label it looks as I would expect it to. Would you like me to merge it?

Got it, thanks. Please merge!


Basic waning immunity

Assumes a constant rate of recovered becoming susceptible again
Closes https://github.com/SABS-R3-Epidemiology/epistrains/issues/41

It looks good to me!


WIP: shared pkg for Go plugins + plugin for EKS audit logs

Signed-off-by: Issif issif+github@gadz.org<!--  Thanks for sending a pull request!  Here are some tips for you:

If this is your first time, please read our contributor guidelines in the CONTRIBUTING.md file and learn how to compile Falco from source here.
Please label this pull request according to what type of issue you are addressing.
Please add a release note!
If the PR is unfinished while opening it specify a wip in the title before the actual title, for example, "wip: my awesome feature"
-->

What type of PR is this?

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

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

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

/area plugins

/area registry

/area build

/area documentation

What this PR does / why we need it:
This PR adds shared go pkg for dealing with AWS API + K8S audit logs + A plugin based on these shared libs for Audit logs from EKS
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

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

Needs approval from an approver in each of these files:

OWNERS

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

@Issif: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
cc8ce50704b81ec33123ff0475ab8e0d79846621
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@Issif: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
512dce582f183870b70a221ecf117f1d821a9490
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@Issif: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
3645772f9379fb53edd38d4c18ba9be9db60ee77
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@Issif: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
cd6d6abf926ff8fe498c94b7ee04465b6997c3bc
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@Issif: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
b5a1c663cbf9900ab16bf0a3e107a9f02c855746
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

@Issif: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

build-plugins-presubmit
e7fc8d0cebf9c1184557e0967cbe4eaa5a258144
link
true
/test build-plugins-presubmit

Full PR test history. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
If this issue is safe to close now please do so with /close.
Provide feedback via https://github.com/falcosecurity/community.
/lifecycle stale

I prefer to close this PR, I'm preparing new ones with the updates of the SDK


Swift signed urls must not end with \n

The refactoring PR #38 added a trailing \n to swift blobstore signed urls.
When using that in the director it fails with errors like:
Compiling package postgres-11: Fetching package postgres-11: Fetching package blob : Failed to download blob: Creating Get Request: parse "https://objectstore-3.abcd/v1/AUTH_1234/bosh1234/1234-5678?temp_url_sig=1234&temp_url_expires=1234\n": net/url: invalid control character in URL

It seems that \n was added since otherwise the url is postfixed with a % char in console.
https://objectstore-3.abcd/v1/AUTH_1234/bosh1234/1234-5678?temp_url_sig=1234&temp_url_expires=1234%
I'm not sure if this is a console issue only ....

Meanwhile I double checked that the signed urls of aws s3 blobstores are postfixed with the % char in the exact same way.
So the result is still the same: We must not and a linebreak (\n) to the signed urls of swift blobstores.


Better support for additional package.json attributes

Release Notes
Adds new rules to the package.json creation pipeline:
Adds merge_json rule to flatten multiple json files into one. This can be combined with the base_package_json attribute to create more dynamic package attributes.
Adds a create_contributors rule for generating the contributors section of a package.json from an .all-contributorsrc
Example:
load("@rules_player//javascript/package_json:index.bzl", "merge_json", "create_contributors")

create_contributors(
    name = "pkg_json_contrib",
    all_contributors = "//:.all-contributorsrc",
)

merge_json(
    name = "pkg_json_template",
    srcs = [
        "package-template.json",
        ":pkg_json_contrib",
    ]
)

:rocket: PR was released in v0.5.0 :rocket:


Refactor exporter config

Switch exporter over to standard Prometheus exporter flags and logging. This eliminates the need for a configuraion file.
Closes: https://github.com/prometheus-community/smartctl_exporter/issues/66
Closes: #30
Signed-off-by: SuperQ<EMAIL_ADDRESS>

Resolves #30

Seems this also doesn't support glob in device param
This is useful, when i want to exclude scsi and other devices, and use only nvme devices (and don't know how much devices will be present on host)
[root@host tmp]# ./smartctl_exporter --smartctl.interval=1h --log.level=debug --smartctl.device=/dev/nvme*
ts=2022-09-30T11:20:26.215Z caller=main.go:94 level=info msg="Starting systemd_exporter" version="(version=, branch=, revision=)"
ts=2022-09-30T11:20:26.215Z caller=main.go:95 level=info msg="Build context" build_context="(go=go1.17.2, user=, date=)"
ts=2022-09-30T11:20:26.215Z caller=main.go:57 level=error msg="Error collecting SMART data" err="Device /dev/nvme* unavialable"
panic: runtime error: index out of range [0] with length 0

goroutine 30 [running]:
main.(*SMARTctlInfo).mineVersion(0xc000185e08)
        /smartctl_exporter/smartctlinfo.go:59 +0xbaf
main.(*SMARTctlInfo).Collect(...)
        /smartctl_exporter/smartctlinfo.go:48
main.SMARTctlManagerCollector.Collect({{0x0, 0x0}, 0x0, {0xc00021c1d0, 0x1, 0x1}, {0xa0c9a0, 0xc000135b40}}, 0xc00010e1e0)
        /smartctl_exporter/main.go:60 +0xd2
github.com/prometheus/client_golang/prometheus.DescribeByCollect.func1()
        /go/pkg/mod/github.com/prometheus/client_golang@v1.13.0/prometheus/collector.go:90 +0x2b
created by github.com/prometheus/client_golang/prometheus.DescribeByCollect
        /go/pkg/mod/github.com/prometheus/client_golang@v1.13.0/prometheus/collector.go:89 +0xa5

We could do globs, but I would prefer to add that in a a separate feature change.

We could do globs, but I would prefer to add that in a a separate feature change.

Created issue #72 for this

Yes, there's always going to be some complaints, but there's also requests the other way, which is "Can we have this work with flags rather than a config file.
Flags are the standard across our ecosystem, and part of donating exporters to Prometheus Community is to bring them up to our standards.

sounds good to me. I forgot the project has been donated to prometheus. That's a good excuse to break thing hehe


Certbot cannot be installed.

The command docker-compose -f docker-compose-letsencrypt.yml up fails with the following error:
Skipping bootstrap because certbot-auto is deprecated on this system.
WARNING: couldn't find Python 2.7+ to check for updates.
Your system is not supported by certbot-auto anymore.
Certbot cannot be installed.
Please visit https://certbot.eff.org/ to check for other alternatives.
ERROR: Service 'nginx' failed to build : The command '/bin/sh -c ./certbot-auto --install-only -n' returned a non-zero code: 1

I think the latest certbot version is required, so the current instructions and configuration are broken.

I think we have two options:

Install certbot in the container and obtain a certificate each time which is not ideal. This can be done with a few modifications in Dockerfile (install certbot) and the start.sh file (use certbot instead of certbot-auto).
Get the certificates on the host and mount the necessary volumes to the container.
Step 1 - Obtain the certificates:
sudo docker run -it --rm --name certbot -v "/etc/letsencrypt:/etc/letsencrypt" -v "/var/lib/letsencrypt:/var/lib/letsencrypt" -p 80:80 certbot/certbot certonly
Your certificate, chain and key file will  be saved in /etc/letsencrypt/live/.
Step 2 - Modify the certbot-nginx/nginx.conf file to listen on 443 and use the new certificate and key.
Step 3 - Modify docker-compose-letsencrypt.yml for the nginx service to mount the necessary directories and files as read-only:

    volumes:
    - /etc/letsencrypt/:/etc/letsencrypt/:ro
    - /etc/ssl/ffdhe4096.pem:/etc/ssl/ffdhe4096.pem:ro
    - canarytokens-docker/certbot-nginx/nginx.conf:/etc/nginx/nginx.conf:ro

I had to do a few more changes in start.sh and Dockerfile to make that work.

Hi @ch40s,
Thanks for reporting this. We will take a look and get back to you. We do know about the "get new certificate each time" issue and we just havent got to optimising for it yet.

Hi @ch40s,
You mention that you have a working copy. We would love a PR if you have the time to submit one. We always appreciate folks contributing.

Confirming, I get the same error. Still a problem.

I just fought thru the errors --  but now there's a SSL error "SSL_ERROR_RX_RECORD_TOO_LONG" -- possibly not updated TLS. I'll submit an issue tomorrow when I get a chance -- also what changes I made to get it working (almost)

A potential solution
certbot's --keep-until-expiring should stop any excessive issuance/renewals

certbot/Dockerfile

FROM nginx
RUN apt-get update
RUN apt-get install -y python-certbot-nginx procps
COPY nginx.conf /etc/nginx/nginx.conf
COPY start.sh /
RUN chmod +x start.sh
CMD /start.sh

certbot/start.sh

(replacing example.com accordingly)
sed -i "s/___server_names___/example.com/g" /etc/nginx/nginx.conf
nginx
sleep 5
certbot --nginx --email<EMAIL_ADDRESS>-d example.com --agree-tos --redirect --no-eff-email --keep-until-expiring --non-interactive
nginx -s stop
sleep 3
nginx -g "daemon off;"

Hi folks,
Sorry for the delay in getting this sorted. I've updated the Dockerfile and some other stuff to fix this issue. Please let me know if you have more issues like this. Ill be closing the issue for now.


Very poor examples

Agreed with "rboy1". See my response to his issue here (in reply to MSFT's response): https://github.com/MicrosoftDocs/azure-docs/issues/23166#issuecomment-457185373

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

ID: ef9aa16f-9c7a-089a-8249-24a3902906e6
Version Independent ID: 886ef069-4001-3544-31ba-e4ef13fb62af
Content: Migrate to V3 - Translator Text API
Content Source: articles/cognitive-services/Translator/migrate-to-v3.md
Service: cognitive-services
GitHub Login: @Jann-Skotdal
Microsoft Alias: v-jansko

hi @lsmith999999,
I have responded on this thread: https://github.com/MicrosoftDocs/azure-docs/issues/23166#issuecomment-485564110
thanks

The issue here is being addressed in #23166.
#please-close


Add example for midi input (maybe output too?)

This adds an example for a stereo volume fader that can get controlled through a midi value (ignores status/note and always applies value byte).

[ ] is using a mspc::channel actually realtime safe? Didn't look further into it but i guess it could block if the the previous pushed value didn't get read?
[ ] currently the u8 (midi, from 0-127) to f32 conversion/mapping is hacky and sometimes has rounding errors not getting 1.0 or 0.0 as values
[ ] probably add vumeter again and send it through midi out? but how?

I've read the detail of MIDI support, but in case it helps, some documentation here:

https://faustdoc.grame.fr/manual/midi/
https://faustdoc.grame.fr/manual/architectures/