text:
How to generate Java classes from the model definition

In an attempt to introduce my company to automated code generation from service definitions, I am looking to get started with defining my APIs with Smithy and use the Gradle plugin to generate the Java code. I followed the complete example as described in https://awslabs.github.io/smithy/2.0/quickstart.html#complete-example
After running gradle build, it did generate the Jar but it does not contain any Java classes.
jar -tvf build/libs/smithy-example.jar
     0 Mon Sep 05 12:46:56 PDT 2022 META-INF/
    40 Mon Sep 05 12:44:26 PDT 2022 META-INF/MANIFEST.MF
     0 Mon Sep 05 12:46:56 PDT 2022 META-INF/smithy/
    15 Mon Sep 05 12:46:56 PDT 2022 META-INF/smithy/manifest
  2577 Mon Sep 05 12:46:56 PDT 2022 META-INF/smithy/weather.smithy

The contents of my project files are exactly as shown in the complete example section. After running gradle build I expected it to generate the model classes and a client SDK for the service but that does not seem to be the case. Let me know what I am missing or  if I completely misunderstood this project.

Ping

Per Michaels comment in https://github.com/awslabs/smithy/issues/1390

We don't currently have any Java code generation for Smithy. It's something we're working on soon. You can see the list of known implementations here: https://awslabs.github.io/smithy/2.0/implementations.html

I do not have any ETA I can share with you, but you might be interested in the documentation on making your own code generator here: https://smithy.io/2.0/guides/building-codegen/index.html

I do not see Java as supported language yet. Do you have any update for us? I am curious to know why is Java support still not added. Are there any challenges that we should be aware of if we go with own code generator option mentioned above?

authors: Askmecoding gredditor hpmellema

repo: smithy-lang/smithy-gradle-plugin


text:
Fixes #1407

Fixes #1407
Omit setting cache setting on request init when using default value

@kuhe do you see any issues with this?

source: gharchive/pull-request

repo: smithy-lang/smithy-typescript

license_type: permissive

license_source: github-api


text:
Add add_outlives method to Poller

resolves #161
The previous implementation only implemented unsafe methods for registering file descriptors with Poller. This implements an add_outlives method that can guarantee safety by accepting a reference to an AsSource which outlives the Poller. Since file descriptors are guaranteed to be valid through the lifetime of the Poller, there is no need to ever delete to maintain soundness.
Please advise if I should change anything.

I tried this initially, but I don't think it will work if the source lifetime is not somehow tied to the Poller struct. The borrow checker will just shorten the poller lifetime inside add_outlives.
With the above example this compiles:
let poller = Poller::new().unwrap();

{
    let file = File::open("./file.txt").unwrap();
    let _ = poller.add_outlives(&file, Event::all(7));
    drop(file);
}
println!("{:?}", poller);

That's disappointing. I was under the impression that the borrow checker would catch this.
Still, thanks for checking!

authors: BrankoKrstic notgull

repo: smol-rs/polling


text:
Chatview inside a tabbar

Hi,
I'm trying to add Smooch inside a react-native component so a user can open Smooch through a tabbar menu instead of the default popup / modal screen.
I created an RCTViewManager class (based on https://facebook.github.io/react-native/docs/native-components-ios.html) that uses [Smooch newConversationViewController].view as its UIView.
The problem is that all chat messages are hidden.
Just the camera icon and send button are visible, although they do not work.
Any ideas how I can get this to work?

Hi @Thymo,
From what I know about React Native, and from a cursory scan of the doc you linked, I'm pretty sure Smooch isn't able to work in this way (i.e. embedded in a tab bar controller) in a react-native app. The reason is simple: there are no UIViewController lifecycle hooks.
The doc you linked is specifically tailored to adding pre-built UIView objects, not UIViewController views. Our conversation controller is strongly coupled to the UIViewController lifecycle methods (e.g. viewWillAppear, viewDidDisappear`, etc...). Without those lifecycle methods being called at the correct time, the conversation view controller will not render or handle user interaction correctly.
If there's a way to render a native UITabBarController in a react-native application, then you should be able to add Smooch correctly as a child of that controller. If that's not possible, I don't think you'll be able to accomplish what you're trying to do unfortunately.

source: gharchive/issue

authors: Thymo mspensieri

repo: smooch/react-native-smooch

license: mit

license_source: bigquery


text:
TypeError: Cannot read property 'bind' of undefined

I am maintaining a react library. In this library i have one entry file from which i am exporting my two main component. If i am importing them in regular way then it is working but my bundle size is going above required bundle size.
So i tried importing dynamically that two component which i am exporting from main entry file and i can see that chunks are being created for bundle but after publishing my library to npm and installing it in another project i am getting TypeError: Cannot read property 'bind' of undefined. I have gone through the docs and have configured the projects properly with respect to code splitting but still getting error every time.

Just double check browser console. This error should have an exact location and an exact reason.
PS: Please don't use any sort of code-splitting inside a library, delegate it to the user code base. You can not ship untranspiled import, required for code splitting, among es5 compatible library code.

@theKashey  in console i am getting above specified error. for error location, since i am using it in another project which is using minified version of my code and that is why i am not able to track it.
And yes i am doing it in my code base. may be you didn't get my use correctly. So i have one react project which is basically a react library in which i am doing code splitting but when i am installing this library after publishing in to another project then in that project i am getting above error.
Hope you got my issue now

Yep, I've got your issue. No code splitting is possible on the library side. The another project should handle it.
Anyway - there a magic button in Chrome DevTools - pretty print, it should help you figure out what is the problem.
Nobody except you could do it. Nobody.

Yes @theKashey  i have tried tracking the issue in formatted by printing it in pretty print  but still it is not depicting exact location of this error that is why i am not able to track it.
And can you please explain me why i can not achieve this at library side. As i can see chunks are being created for all dynamic imported components so i think we can do code splitting for library type project. CMIIMW @theKashey

@theKashey  can you please better suggest me how can i achieve this ?  It will be helpful if you can tell me an example if there exist.
What about this your library https://github.com/theKashey/react-imported-component ?  Can i achieve library level code splitting using this library?

One more time - code splitting code should not be on a "library side".
It could, but you have to configure .babelrc to skip modules transformation (modules:false) and ask not to transform dynamic import, using only syntax plugin.
In any other case you will get or code transpiled for node (would not run in a browser), or a syntax error import is not defined.
Probably you run into the first case. But there is too many unknowns - starting from how you compile your library and ending how you use it.
Yet again - unless you provide an example, you are the only one who could answer these questions.

@theKashey  Can you please more elaborate how and what to configure in .babelrc?
And for providing example, i have to publish a new project on npm with same use case  and then only you can check but i can't give current project.

I encourage you to learn more about the thing you are using, or stop using it without proper domain knowledge. As I said - code splitting code should not be on a "library side", and the problems you are facing is something you shall face.
Try to solve this puzzle without cheating from my side. Only one tip for you - import shall still be import in the final library sources, you are publishing to the npm.

Thanks @theKashey  for encouraging and i am going in deep as much as i can. I think it is fine in my case to do code splitting as only there are two export statements not like many exports for many components.

authors: Nasirilahi theKashey

repo: smooth-code/loadable-components

license: MIT


text:
TES Executor error

Snakemake version
6.10.0
Describe the bug
Trying to run the example hello-world TES workflow in Snakemake version 6.10.0 does not work due to a WorkflowError. Reverting Snakemake to 6.6.1 starts the execution of the workflow correctly. Could be related to https://github.com/snakemake/snakemake/issues/1260
Logs

(/tmp/conda/snakemake) XXXXX@88665a0ab8a1 hello-world % snakemake
--tes $TES_URL
--use-conda
--envvars CONDA_PKGS_DIRS
--conda-prefix $CONDA_ENVS_PATH
all -j 10 -F --rerun-incomplete
Building DAG of jobs...
[TES] Job execution on TES: http://localhost:8000
Using shell: /bin/bash
Singularity containers: ignored
Job stats:
job                  count    min threads    max threads

all                      1              1              1
convert_to_pdf           3              1              1
download_data            1              1              1
plot_histogram           3              1              1
select_by_country        3              1              1
total                   11              1              1
Select jobs to execute...
[Wed Nov 17 16:23:20 2021]
rule download_data:
output: data/worldcitiespop.csv
jobid: 4
resources: tmpdir=/var/folders/xb/ygj1lpcj1bb6hgvyxw3cdfp80000gs/T
WorkflowError:
expected str, bytes or os.PathLike object, not LocalSourceFile

Minimal example
Terminal 1;
Install Funnel on your local system: https://ohsu-comp-bio.github.io/funnel/download/
Run the server: funnel server run
NB: It should output the following text (change the http port in Terminal 2 for tes if it is different)
server               Server listening httpPort             8000 rpcAddress           :9090 time                 2021-11-17T16:19:56-08:00
Terminal 2;
Download the Snakemake git directory and change the directory to the hello-world example
Setup a Snakemake environment via Mamba: mamba create -c conda-forge -c bioconda -n snakemake snakemake
Activate Snakemake: conda activate snakemake
Run the following commands:

pip install py-tes
export TES_URL=http://localhost:8000
export CONDA_PKGS_DIRS=/tmp/conda
export CONDA_ENVS_PATH=/tmp/conda

Run the workflow via Snakemake:

snakemake
--tes $TES_URL
--use-conda
--envvars CONDA_PKGS_DIRS
--conda-prefix $CONDA_ENVS_PATH
all -j 10 -F --rerun-incomplete

Additional context
TES Server used: Funnel

What is the hello-world workflow? Can you provide a link to it? Would like to test with it.

I was using the workflow defined here: https://github.com/snakemake/snakemake/tree/main/examples/hello-world

Just tested with the above workflow, and could not reproduce this on version 6.12.1.

authors: cademirch elliot-smith

repo: snakemake/snakemake


text:
remove --cluster from v8.x

Is your feature request related to a problem? Please describe.
I am trying to troubleshoot a problem that I was having in snakemake 7 where, when I used --cluster "command string here", snakemake would not recognize when target files were present and rules had successfully completed. The same snakemake worked fine when ran without --cluster. I think it is related to https://github.com/snakemake/snakemake/issues/2739 or https://github.com/snakemake/snakemake/issues/2496 . It might be some file latency problem with my SLURM cluster, too.
I switched to snakemake 8 to test my code, and I ran the same command with --cluster. It ran, and I encountered the same issue. I then looked at the documentation for snakemake 8 and realized that --cluster has been replaced with the --executor flag, and the --cluster is no longer supported.
Describe the solution you'd like
I think snakemake 8 should throw an error when --cluster is called and the user should be pointed to the now-supported --executor pattern. If it is deprecated code, maybe that code should also be removed.
Describe alternatives you've considered
The alternative is not doing anything and allowing snakemake to run with the old --cluster instruction. Old scripts may still work, but bug fixes for it would not be supported.

The cli documentation contains several references to --cluster, even though it doesn't exist anymore in 8.25.3.
$ snakemake --version
8.25.3
$ snakemake --cluster
usage: snakemake [-h] [--dry-run] [--profile PROFILE] [--workflow-profile WORKFLOW_PROFILE] [--cache [RULE ...]] [--snakefile FILE] [--cores N] [--jobs N] [--local-cores N]
...
snakemake: error: unrecognized arguments: --cluster

authors: conchoecia guyer


text:
[saddle-finance] Snapshot Strategy Logic Fix

Changes proposed in this pull request:

Change logic away from taking into consideration total vest amount to unclaimed and vested amount.
Closes https://github.com/saddle-finance/tickets/issues/244

Hi @ug02fast This can potentially change voting power in existing proposals (including the one that is still active) so better to create a new -v2 strategy

Hi @ug02fast This can potentially change voting power in existing proposals (including the one that is still active) so better to create a new -v2 strategy

Good idea. Thanks.

repo: snapshot-labs/snapshot-strategies


text:
New settings validation

Work in progress... but you can look at the PR build if you want.

I think if the schema has a maxlength it should also set the maxlength on the input field. Like we do with strategies

There is some issue with the text color on select inputs, they should be text-skin-link color.

I think if the schema has a maxlength it should also set the maxlength on the input field. Like we do with strategies

I think we should take care of this when refactoring the settings page and reuse the new input component.

authors: mktcode samuveth

repo: snapshot-labs/snapshot


text:
I wish this was opt out!

I wish I could just have one account on the fediverse, and from that follow all the people I know on Bluesky, and have everyone be able to reply to my posts. But this doesn't work out because the people I want to follow and the people who would reply to my posts are probably not opted into the bridge!
I'm sure this was done for a reason, but it severely limits the utility of the service. I also couldn't find an explanation of the reasoning on the FAQ page.

I found it! https://github.com/snarfed/bridgy-fed/issues/835
Maybe there's something to be said about default allowing bridging onto the fediverse, but not off of it...

Yeah this was a pretty big controversy. Lots of people felt strongly, on both sides but especially on the opt in side, and they told me so pretty colorfully.
Also see #1471 and https://snarfed.org/2024-01-21_moderate-people-not-code#Metcalfe , where I discussed the same point:

Having said all that, for services like bridges that live and die by network effects, opt-out seems like the only way to be broadly useful. If a Bluesky/fediverse bridge is opt in, and Alice opts into bridging her Bluesky account, people in the fediverse will see her and her posts, but she won’t see their replies or other interactions unless they’ve also opted in. More importantly, people in the fediverse won’t see anyone else on Bluesky either.

Yes, dupe of #1471 tbh

authors: snarfed tbodt

repo: snarfed/bridgy-fed


text:
Webmentions aren't being received for some replies

It appears that some replies are being rejected by webmention.io with no_link_found
Some investigation:
https://chat.indieweb.org/dev/2023-03-09/1678348830552900
https://chat.indieweb.org/dev/2023-03-09/1678349222769000
https://chat.indieweb.org/dev/2023-03-09/1678349490081300

Odd. Details from this example:

source: https://fed.brid.gy/render?id=https%3A%2F%2Fhachyderm.io%2Fusers%2Fbyjp%2Fstatuses%2F109990940244547039%2Factivity

...which 301 redirects to https://fed.brid.gy/render?id=https%3A%2F%2Fhachyderm.io%2Fusers%2Fbyjp%2Fstatuses%2F109990940244547039

target: https://www.jvt.me/mf2/2023/03/shs0i/
webmention.io status page: https://webmention.io/www.jvt.me/webmention/zbdmZxxGx1sI4n6djhx6
BF log: https://fed.brid.gy/log?start_time=1678328560&key=https://hachyderm.io/users/byjp/statuses/109990940244547039/activity&module=

As mentioned in chat, the final source page has this link to the target URL.

@aaronpk my only guess is the redirect, but that should be pretty common, I'm sure wm.io supports source URL redirects, right?

Interestingly there are replies in the thread in 👆🏼 that I'm receiving perfectly fine

Moving to https://github.com/aaronpk/webmention.io/issues/187

Tentatively closing in favor of https://github.com/aaronpk/webmention.io/issues/187. Feel free to reopen if it turns out to be on this end after all!

authors: jamietanna snarfed


text:
how do you handle changing usernames on bluesky?

a vast majority of fedi software doesn't support changing usernames (mostly because all the other ones don't), but bluesky does. how do you handle that? the usernames are the actual username on bluesky, not the did, which never changes.

Not the developer, but I suspect they do this by using the DID identifier which is unique to a user rather than their bluesky handle for their activepub handle.

Not the developer, but I suspect they do this by using the DID identifier which is unique to a user rather than their bluesky handle for their activepub handle.

Right! https://fed.brid.gy/docs#translate

authors: AshWeststar TheAwesome98-Real snarfed


text:
Download stuck after certain percentage

As title says.
https://user-images.githubusercontent.com/28742605/81871177-93b54a00-9577-11ea-84eb-78e308028fe9.png

Ok made it work with dev build, it was probably a token problem as mentioned in other threads... I would rather have a working version of a program with open headless browser in the background then fancy looking none functional build. Could even download one hour long video with new version.

repo: snobu/destreamer


text:
[Query] Compatibility with PyTorch >=v1.2.0a0

Installing snorkel requires torch>=1.1.0,<1.2.0. Are there non-trivial issues that restrict PyTorch version? Is this something that can be helped?

Hi @chaturv3di — At the moment, a few internal implementations rely on those versions of torch. Closing this issue as a duplicate of #1558 ~ please see the following comment for more details!
https://github.com/snorkel-team/snorkel/issues/1558#issuecomment-602116595

repo: snorkel-team/snorkel


text:
the timeline is null

when i use , the timeline is show nothing. and others working well

This is the default behavior.
https://github.com/snowair/phalcon-debugbar#send-custom-messages-to-debugbar

authors: snowair xkos

repo: snowair/phalcon-debugbar


text:
Merge Installation page with Quick Start page?

There is a lot of overlapping content from both pages, I believe we could merge them both in a way that we can have the "quick start" followed by the rest of the "installation" content.
I believe this should be done after these two PR's are completed so that no content is missed or we have double work.

https://github.com/snowpackjs/astro-docs/pull/32
https://github.com/snowpackjs/astro-docs/pull/16

@FredKSchott @itskitto @aFuzzyBear @jgil-r

The only difference is that the installation page briefly mentions node.js as a dependency. I can just add that to the top of quick-start page and completely get rid of installation page. Currently we have very similar information in /, /installation, and /quick-start pages. I mentioned in #32 that we can avoid repetitive information by making the sidebar headings just be headings or links that route to the first link of that specific group. For example, instead of Basic Concepts having its own page, it should just link to Project Structure.

@jgil-r I agree with the sidebar, but for the installation page, I believe it would be better to check PR #16, since @aFuzzyBear changed a lot of the page content.

Yeah, I'm not sure if we need a distinction between Installation and Quick Start, they seem to be one in the same. I think we can merge them in a way that's concise and to the point and then break out @aFuzzyBear's extended information into a "Deep Dives" section and link it in the Quick Start/Installation merge

Hey guys thats me made the changes to the install and in the index page, If we can merge them, idk what the best way for that would be, whatever you guys think is best, Once they are merged there is a few link adding that I need to do just to link them to other doc pages for reference,
thanks for your support team =)

Docs improved in https://github.com/snowpackjs/astro-docs/commit/d2027d928ee04d2af38bab39878c38f0681f422c to make this separation more clear

authors: FredKSchott Hanawa02 aFuzzyBear itskitto jgil-r

repo: snowpackjs/astro-docs


text:
[BUG] devOptions.hmr doesn't disable HMR

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager npm
[x] I run Snowpack on OS Mac
[x] I run Snowpack on Node.js v12+

Describe the bug
Setting devOptions.hmr: false doesn't disable HMR
To Reproduce
We can't fix bugs that we can't see for ourselves. Issues often need to be closed if this section is skipped.

npx create-snowpack-app testing-hmr --template @snowpack/app-template-react
cd testing-hmr
Set devOptions.hmr: falsein snowpack.config.js
npm start
Edit App.jsx with any content you want
You will notice HMR is still enabled

Expected behavior
HMR should be disabled
Anything else?
Nope 😄 thank you!

I spotted this the other day, currently the option is haedcoded to true here: https://github.com/snowpackjs/snowpack/blob/af1680e8fd6fcdf0a683cb0a06f87bfeea882a44/snowpack/src/commands/dev.ts#L966
I'm happy to create a PR to default it to true but respect the option set in config.

Thank you!!!

repo: snowpackjs/snowpack


text:
Protect against Integer overflow

SchemaVer.parse("1-1-111111111111114") results in runtime exception.

Test demonstrating the issue: https://github.com/snowplow-incubator/iglu-scala-core/blob/int-overflow/src/test/scala/com/snowplowanalytics/iglu/core/SchemaKeySpec.scala#L47-L57

authors: chuwy dilyand

repo: snowplow-incubator/iglu-scala-core


text:
Iglu CLI: add iglu lint command

Migrated from https://github.com/snowplow/schema-guru/issues/85

See also: https://github.com/snowplow/iglu-central/blob/master/ci/lint.bash
I'd like this linter to get to the point where the Iglu Central linter can be removed.

repo: snowplow/iglu


text:
Reset firstId even if app is in the foreground

firstId are only reset if the app is in the background:
https://github.com/snowplow/snowplow-android-tracker/blob/b702375c004dad67da84ffd9961c486e3435aaa0/snowplow-tracker/src/main/java/com/snowplowanalytics/snowplow/tracker/Session.java#L140-L147
which causes subsequent foreground sessions to have the same firstId

c.f. #192

Ouch good catch, thanks for scheduling

and c.f. https://snowplow.zendesk.com/agent/tickets/8211

authors: BenFradet alexanderdean

repo: snowplow/snowplow-android-tracker


text:
Emitter.addToBuffer can lead to network on UI thread if set to immediately flush

Raised by @hamidp

All network communications have been reimplemented within RxJava and a background Scheduler.
Relevant Issue: https://github.com/snowplow/snowplow-android-tracker/issues/49
As such this is no longer an issue.

Closing this has been done/

authors: alexanderdean jbeemster


text:
Scala Common Enrich: bump Akka Streams to 2.0.4

[info] Total for specification MapTransformerSpec
[info] Finished in 1 ms
[info] 2 examples, 0 failure, 0 error
localhost - - [26/May/2016 09:43:00] "GET /guest/api/lookup-test/snowplower?format=json HTTP/1.1" 200 -
localhost - - [26/May/2016 09:43:00] "POST /api/lookup+test/snowplower/j-ZKIY4CKQRX72/32.1?date=2014-11-10T08%3A38%3A30.000Z HTTP/1.1" 200 -
[ERROR] [05/26/2016 09:43:00.956] [api-request-system-akka.actor.default-dispatcher-5] [ActorSystem(api-request-system)] Outgoing request stream error
java.lang.IllegalArgumentException: requirement failed: Cannot pull closed port
    at scala.Predef$.require(Predef.scala:233)
    at akka.stream.stage.GraphStageLogic.pull(GraphStage.scala:419)
    at akka.http.impl.engine.client.OutgoingConnectionBlueprint$ResponseParsingMerge$$anon$3$$anonfun$1.apply$mcV$sp(OutgoingConnectionBlueprint.scala:207)
    at akka.stream.stage.GraphStageLogic$Emitting.followUp(GraphStage.scala:830)
    at akka.stream.stage.GraphStageLogic$EmittingSingle.onPull(GraphStage.scala:879)
    at akka.stream.impl.fusing.GraphInterpreter.processEvent(GraphInterpreter.scala:593)
    at akka.stream.impl.fusing.GraphInterpreter.execute(GraphInterpreter.scala:533)
    at akka.stream.impl.fusing.GraphInterpreterShell.runBatch(ActorGraphInterpreter.scala:445)
    at akka.stream.impl.fusing.GraphInterpreterShell.receive(ActorGraphInterpreter.scala:400)
    at akka.stream.impl.fusing.ActorGraphInterpreter$$anonfun$receive$1.applyOrElse(ActorGraphInterpreter.scala:549)
    at akka.actor.Actor$class.aroundReceive(Actor.scala:467)
    at akka.stream.impl.fusing.ActorGraphInterpreter.aroundReceive(ActorGraphInterpreter.scala:495)
    at akka.actor.ActorCell.receiveMessage(ActorCell.scala:516)
    at akka.actor.ActorCell.invoke(ActorCell.scala:487)
    at akka.dispatch.Mailbox.processMailbox(Mailbox.scala:238)
    at akka.dispatch.Mailbox.run(Mailbox.scala:220)
    at akka.dispatch.ForkJoinExecutorConfigurator$AkkaForkJoinTask.exec(AbstractDispatcher.scala:397)
    at scala.concurrent.forkjoin.ForkJoinTask.doExec(ForkJoinTask.java:262)
    at scala.concurrent.forkjoin.ForkJoinPool$WorkQueue.runTask(ForkJoinPool.java:975)
    at scala.concurrent.forkjoin.ForkJoinPool.runWorker(ForkJoinPool.java:1478)
    at scala.concurrent.forkjoin.ForkJoinWorkerThread.run(ForkJoinWorkerThread.java:104)
[info] ApiRequestEnrichmentIntegrationTest
[info]
[info] This is a integration test for the ApiRequestEnrichment
[info] + Basic Case
[info] x POST, Auth, JSON inputs, cache, several outputs
[error]    'Failure(NonEmptyList(java.lang.IllegalArgumentException: requirement failed: Cannot pull closed portjava.lang.IllegalArgumentException: requirement failed: Cannot pull closed port))' is not Success (ApiRequestEnrichmentIntegrationTest.scala:289)
[info]
[info]
[info] Total for specification ApiRequestEnrichmentIntegrationTest
[info] Finished in 0 ms
[info] 2 examples, 1 failure, 0 error

In e.g. this Travis build: https://travis-ci.org/snowplow/snowplow/builds/133065328

Seems like this bug. But from what I can see in their history - it is fixed in 2.0.2 which is used in API Enrichment. I'll try to reproduce.

Looks like it has been really fixed in 2.0.3 http://akka.io/news/2016/01/26/akka-streams-2.0.3-released.html. Should we create separate ticket to bump?

I have renamed this ticket!

Thanks. But I guess, it will be better to bump straight to 2.0.4.

Good point.

moved away from akka-streams, closing

authors: BenFradet chuwy fblundun

repo: snowplow/snowplow


text:
Too large memory use when submitting queries that generate punctuated watermark

When submitting many stream queries that generate punctuated watermarks, MIST uses too large memory. We should fix it.

That was the problem of my query submission code. I will close this issue.

It occurred again. I will reopen this issue

repo: snuspl/mist


text:
[Snyk] Security upgrade @angular/cli from 10.2.4 to 14.2.12

Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

frontend/package.json
frontend/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity
Reachability

265/1000  Why? Confidentiality impact: None, Integrity impact: None, Availability impact: High, Scope: Unchanged, Exploit Maturity: Proof of Concept, User Interaction (UI): None, Privileges Required (PR): None, Attack Complexity: Low, Attack Vector: Network, EPSS: 0.0016, Social Trends: No, Days since published: 487, Reachable: Yes, Transitive dependency: Yes, Is Malicious: No, Business Criticality: High, Provider Urgency: High, Package Popularity Score: 99, Impact: 5.99, Likelihood: 4.41, Score Version: V5
Regular Expression Denial of Service (ReDoS) SNYK-JS-SEMVER-3247795
Yes
Proof of Concept
Reachable

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

🎉 Snyk hasn't found any issues so far.
✅ security/snyk check is completed. No issues were found. (View Details)
✅ license/snyk check is completed. No issues were found. (View Details)

repo: snyk-kevin/juice-shop


text:
Should enrichment modify or add to the tools noted in the SBOM

Good question from @rnjudge https://twitter.com/rosejudge5/status/1666879138739916800

how is SBOM creation metadata handled when the SBOM is changed? Is the document creation metadata changed to reflect the new creator?

Warrants investigation. Parlay is adding to, rather than recreating, the original content. You ideally still want to know what tool generated the list of packages, but (separately) knowing that some of the information came from Parlay would be useful.

Both CycloneDX and SPDX should support extending an already available list of creation tools, and add Parlay as an additional entry while maintaining any other tools that might have come before it.

https://cyclonedx.org/docs/1.4/json/#metadata_tools
https://spdx.github.io/spdx-spec/v2.3/document-creation-information/#68-creator-field

The trouble with adding a creator instance to the original SPDX document is that the timestamp of when Parlay enriches the SBOM and when the SBOM is actually created will be different (in 2.3 at least) and simply adding a creator would imply that those timestamps were the same. The original SBOM should not be modified.
You think could also use an amends relationship from the original document to point to another version of the SBOM that has been enriched. I think you could also enhance the SBOM using annotations of some sort?.  to Adding @goneall here because he will have a better idea.
Note that in 3.0 this will be much easier because of the profiles being added.  In SPDX 3, you can put enhancement information into a new file which could reference the original one.

Agree with @rnjudge comments above - making amendments to the original SBOM would be the preferred approach.  That would allow clear separation of the creation information.
There are a couple of ways you could do this in SPDX:

create a complete copy of the SBOM + the amended information then have a single amends relationship back to the original document
create a skinny non-SBOM with just the changed elements and have an amends relationship back to each modified element

I personally like the first approach - seems simpler and in the spirit of this utility.
You can also use Annotations - however, they are unstructured and may not be easily machine understood by the receiver.

authors: garethr goneall mcombuechen rnjudge

repo: snyk/parlay


text:
[Snyk] Security upgrade @angular/cli from 1.0.0 to 6.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

infrastructure/oss/testdata/package.json
infrastructure/oss/testdata/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

696/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.5
Denial of Service (DoS) SNYK-JS-DECODEURICOMPONENT-3149970
Yes
Proof of Concept

641/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 6.4
Prototype Pollution SNYK-JS-JSON5-3182856
Yes
Proof of Concept

479/1000  Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-LOADERUTILS-3042992
Yes
No Known Exploit

589/1000  Why? Has a fix available, CVSS 7.5
Prototype Pollution SNYK-JS-LOADERUTILS-3043105
Yes
No Known Exploit

479/1000  Why? Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-LOADERUTILS-3105943
Yes
No Known Exploit

586/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-1018905
Yes
Proof of Concept

681/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.2
Command Injection SNYK-JS-LODASH-1040724
Yes
Proof of Concept

686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution SNYK-JS-LODASH-450202
Yes
Proof of Concept

731/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 8.2
Prototype Pollution SNYK-JS-LODASH-567746
Yes
Proof of Concept

686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution SNYK-JS-LODASH-608086
Yes
Proof of Concept

686/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 7.3
Prototype Pollution SNYK-JS-LODASH-73638
Yes
Proof of Concept

541/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 4.4
Regular Expression Denial of Service (ReDoS) SNYK-JS-LODASH-73639
Yes
Proof of Concept

636/1000  Why? Proof of Concept exploit, Has a fix available, CVSS 6.3
Prototype Pollution npm:lodash:20180130
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)
🦉 Prototype Pollution
🦉 Command Injection

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

authors: CLAassistant pecodez

repo: snyk/snyk-ls


text:
fix: golangci config, linter errors

Description
Activated linters and fixed issues.
Checklist

[ ] Tests added and all succeed
[x] Linted
[ ] README.md updated, if user-facing
[ ] License file updated, if new 3rd-party dependency is introduced

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: bastiandoetsch:x: Team-HammerheadYou have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant bastiandoetsch


text:
Use pod_target_xcconfig instead of xcconfig in the podspec

Basically the same as https://github.com/CocoaLumberjack/CocoaLumberjack/issues/814, and @benasher44 did a great job of explaining this change.
The current podspec modifies the xcconfig for the entire Pods project, when it really only needs to be applied to this pod's project. This change keeps this pod's changes restricted to its project,t and leaves the user's settings to drive the rest of the pods.

Great @mrh-is, thank you for your work, I appreciate it!

authors: mrh-is soberman

repo: soberman/ARSLineProgress


text:
Windows環境でのインストール

Windows環境でのインストールが比較的スムーズにいきましたので、情報提供です。
環境：Windows 10 pro
Windows環境においてはそのままインストールするとインストール中にUnicodeDecodeErrorが発生してしまいインストールできず、windowsブランチはインストール可能なものの初回使用時にダウンロードされる辞書をShift-JISコードに変換するなどの作業が必要で、入力ファイルもShift-JIS形式を用いる必要がありました。
https://qiita.com/Nidhog-tm/items/c7e9d759ce1a0f5c85c6
に沿って、
コントロールパネル＞地域＞管理＞システムロケールの変更＞ベータ：ワールドワイド言語サポートでUnicode UTF-8を使用(U)
というオプションをオンにしておくと、
pip install git+https://github.com/sociocom/MedNER-J.git
のみでインストールが可能で、インストール後もUTF-8形式のテキストファイルを入力ファイルとして使用することができました。ただ、ベータ版の機能のようで、こちらをオンにするとMecabのWindows版インストーラーが文字化けしてしまったので、要注意かもしれません。

有益な情報ありがとうございます！対応が大変遅れまして申し訳ありません．
是非REAMEに追記させていただきたいと思います．

repo: sociocom/MedNER-J


text:
Support for T8/T15 modes

Hi, would it be possible to add support for the T8/T15 modes often used when keeping a basic temperature in a summer home etc. when you want to save on energy costs.
If I set e.g. T8 with the Comfort Cloud, the add-in now shows Heat and 8C, but when trying to adjust this in HA, I cannot go below 16C. So I can see that it is in T8 mode in HA, but I cannot activate T8 in HA.

Duplicate of issue #20

There is a preset for 8/15 mode

authors: dsmnetdesign mstendah sockless-coding


text:
Use same code on docker-compose and kubernetes

What type of PR is this?
Fixes the following.

Build Latest images for multi-cloud .
Use correct path for initdb.sh
Use same code on both Kubernetes and Docker-Compose.

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind new feature
kind bug fix
/kind cleanup
/kind revert change
/kind design
/kind documentation
/kind enhancement

What this PR does / why we need it:
Fixes the following.

Build Latest images for multi-cloud .
Use correct path for initdb.sh

Which issue(s) this PR fixes:

Fixes #
#1215
#1223
Test Report Added?:

Uncomment only one  /kind <> line, hit enter to put that in a new line, and remove leading whitespace from that line:
/kind TESTED

Test Report:
on docker-compose :

On Kubernetes

Special notes for your reviewer:

LGTM

LGTM

Opened issue #434 to track these suggestions and naming convention changes.

These conditional service naming is ok for now. Please open issue and track it to fix properly going ahead

Opened #435 to track the conditional naming

authors: PravinRanjan10 kumarashit rajat-soda sushanthakumar

repo: sodafoundation/multi-cloud


text:
Create Unit test to assert mixin is mixed in

@notmessenger this issue will be addressed in #809 since that issue is creating the unit test file for sl-alert.

authors: erangeles notmessenger

repo: softlayer/sl-ember-components


text:
🛑 Subs EU is down

In 3a6c834, Subs EU (https://subscene.eu.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Subs EU is back up in 1bb1fb0 after 12 minutes.

repo: softsub/uptime


text:
Update sbt to 1.10.6

About this PR
📦 Updates org.scala-sbt:sbt from 1.10.1 to 1.10.6
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #157.

repo: softwaremill/odelay


text:
How to user wheelnav.js to create sub menu?

Hello,everyone,
I want to create sub-menu,is there hava some examples or API document?
Thank a lot.

Hi @deadliving
Basically the sub-menu is two wheelnav on each other.
You can find more information here: http://wheelnavjs.softwaretailoring.net/documentation/core.html#divMultipleWheel

authors: deadliving softwaretailoring

repo: softwaretailoring/wheelnav


text:
WIP: Add tests on Fedora linux

Related to https://github.com/sogou/workflow/issues/1187

Still failed...

Yes, error is due to get_filename_component on newer versions of CMake https://github.com/sogou/workflow/actions/runs/4251285902/jobs/7393433380

OK, we will fix it. Thanks

Please reverse this commit: https://github.com/sogou/workflow/pull/1189/commits/182576079c26fa938f288b6e472c169258fbc541

Could you reopen a pull request? Create a new branch from sogou/workflow master branch and update ci.yml only.

Because I submitted a wrong commit and mess everything up. Sorry, my fault.

I think it should be:
get_filename_component(GTEST_PATH ${GTEST_LIBRARY} DIRECTORY ABSOLUTE )

Passed. By please reopen a PR. We will update CMake.

Ok, checking Ubuntu as well. Will open a new PR once done. Hopefully, 30 minutes at most.

Probably order ABSOLUTE DIRECTORY vs DIRECTORY ABSOLUTE is not important https://cmake.org/cmake/help/latest/command/get_filename_component.html

Thank you so much!

Replaced with https://github.com/sogou/workflow/pull/1193

authors: Barenboim bkmgit

repo: sogou/workflow


text:
can not pull docker images

docker run --rm -p 3000:3000 -v ./log:/var/log/traq soheilpro/traq /var/log/traq/traq.log
Unable to find image 'soheilpro/traq:latest' locally
docker: Error response from daemon: pull access denied for soheilpro/traq, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

The images have been removed from the Docker hub. You can build them yourself by running:
docker build -t traq .

authors: changchichung soheilpro

repo: soheilpro/traq


text:
Polyfill Node APIs for compatibility with Webpack 5 and Create React App 5 (second try)

The new version of Webpack – and by extension the new version of Create React App – no longer includes polyfills for Node APIs by default. This means that if your browser-based app requires modules like assert and stream, Webpack will fail to find them and fail to build.
In this PR, we alias the modules that the wallet adapter depends upon to their related browser polyfills.
I've also followed up with each repository to let them know that they might like to eliminate or polyfill these modules in their own browser builds.

https://github.com/ethereumjs/ethereumjs-monorepo/pull/1638/
https://github.com/crypto-browserify/cipher-base/pull/16

If you're having trouble using the Solana wallet adapter with Create React App 5, can you patch this PR in and report back? I might have missed some polyfills.
Fixes #241.

This is a revert and patch of https://github.com/solana-labs/wallet-adapter/pull/275.

Added test plan:
cd packages/starter/example
yarn dev
open http://localhost:3000

Next.js example app loaded this time.

Thanks so much for doing this @steveluscher. Is there a timeline for this getting merged in? Would be a great help since the building process errors out when trying to use the version up on NPM.

No problem, @TomLisankie! I think the core team must have been crunching last weekend, supercharging the validators 🚀
Fingers crossed I hit all the cases with this PR, but I want someone more familiar with all the wallet use cases to give it a good test.
Speaking of testing, I've been thinking about how we could write automated tests for this thing. I'm pretty sure there's a world where we could image a test environment that has every wallet installed, and run Playwright end-to-end tests against that. Would make an awesome project for someone.

I built the React starter app, then gripped the dist/ folder for each of these removed Node polyfills: https://github.com/webpack/node-libs-browser
# eg. grepped for...
(['"]zlib['"]|new zlib\(|\bzlib\.)

The only one that I found was URL, which is supported natively by all browsers except IE 11 and earlier.

The example works! https://solana-labs.github.io/wallet-adapter/example/
Not sure if CRA 5 does, but at least everything is building, and the packages have been published.

Is this working with CRA 5?

Is this working with CRA 5? Mine seems not working though.

I think it's possible an issue was reintroduced by
https://github.com/solana-labs/wallet-adapter/pull/296
I'm looking into it. cc @armaniferrante

@gaolingxiao @armaniferrante
This is fixed via #299 but you'll need to use react-app-rewired with config here to do the polyfills correctly. See the new create-react-app-starter project. The key parts are the config-overrides.js file and npm:process dependency.
The core issue is that the Torus and Ledger JS libraries don't correctly polyfill and incorrectly use globals, and this isn't handled by Webpack 5 without additional configuration, which you can't add with CRA5 alone. We use react-app-rewired to override, as Craco doesn't support CRA5 yet.
Published:

@solana/wallet-adapter-ledger@0.9.7
@solana/wallet-adapter-torus@0.11.9
@solana/wallet-adapter-wallets@0.15.3

authors: TomLisankie gaolingxiao jordansexton steveluscher

repo: solana-labs/wallet-adapter


text:
Add IIO node sample include Gryosope,Magnet, Accelerate, Color, Humidity, Light, ADC, Pressure and Temperature

Change-Id: I5c8389510c91547b9617f4058ae5e302eec2ff09
Signed-off-by: guchaojie chao.jie.gu@intel.com

@barbieri @bdilly  @edersondisouza  This two category sensors test work well in Minnow Max board as reference by grove-kit, please have a review for these two category code style and picture. According to your comments and no problem, I will submit other sensor category as a bunch for further reviewing.Thanks

looks excellent to me :-)
@mbelluzzo and @edersondisouza ?

\o/
+2

@barbieri @bdilly @edersondisouza All the IIO node samples have been submitted now, please have a review. If no problem, you can merge it. Thanks!

@edersondisouza we didn't demand, at least right now, pictures for all platforms. Just one, but I agree that would be nice to have a picture for configuration available, but would not block the PR because of this.
Regarding to sol-flow.conf, it will fallback to it in platforms other than the specified ones. That's also why there is no need to explain when to use each conf file, but rather explain what to do if your platform is neither minnow nor galileo. But one interesting thing that you brought to my attention is that if there is a sol-flow.json, it needs to be at least enough to successfully assemble the flow, IOW it need to have all required options on it so the nodes can be construct and everything, it may not work everywhere because options choices, but never for lack of required options. @guchaojie have you tested this?

@mbelluzzo Oh, I see. Fair enough. And I don't think sol-flow.json is enough to build, as iio_device option doesn't have a default value.
@guchaojie Could you check this, please? Maybe just add the option with name of device for this fallback conffile.
And I was just curious about the Galileo photo =D

Having a dummy sol-flow.json is good so at least the error message is more meaningful. It's easier to get an error that it failed to load due missing options, or the options do not match the hardware, instead of "MyGyroscope not found" and be clueless that it is missing a configuration file entry.
Thus keep the sol-flow.json as proposed in this PR.
As for PICTURES, I do have a comment: please name the files after the test so automated tools can link them (we'll provide those soon in "soletta's dev-app"). Then if the test is temperature.fbp, the schema should be called schema-temperature.jpg, not "-temperature-sensor" as it is now. It would also be better to name them after the current board in use, so the correct name would be: schema-temperature-intel-minnow-max-linux_gt_3_17.jpg (i know stating the kernel version in the board name is kinda weird, but hey... at least it is consistent).
The plan is for the GUI to show the configuration file for that FBP and when you press "run" it will first show the assembly picture (schema-${FBP}-${BOARD_NAME}.jpg)

@edersondisouza @mbelluzzo ADC module is built in the Galileo board, so there is no wiring picture in this PR.
There are two reasons putting sol-flow.json here:

sol-flow.json is dummy now but just for fallback conffile in the future. According my test, if we want to sol-flow.json take effect, we have to let this sol-flow.json include all the option detail for different platform like sol-flow-intel-minnow-max-linux_gt_3_17.json.
According to  https://github.com/solettaproject/soletta/blob/master/src/samples/flow/grove-kit/README, I found one error happen
$ ./grove-button.fbp
./grove-button.fbp:37:1 Couldn't resolve type name 'Button'
It shows that defining sol-flow.json  in the current folder can avoid this.

What's your point for sol-flow.json to keep current style or add all the required options for different platform into it?

Ah, ok about the picture then =D
Keep sol-flow.json as is, just fix the comments and image names as @barbieri proposed.

@edersondisouza I have already fixed the issue about comments and image name, BTW, add README file according to your suggestion, please have a review:)

@guchaojie pr seems good.
I've invited you to join soletta-dev teams, so you'll be able to push your changes to master.
Just check our approach before doing it. We're not following regular github flow.
https://github.com/solettaproject/soletta/wiki/Contributing#contributions-flow
Special attention to step 8.
Thanks

+2 @guchaojie take the opportunity to test if you can successfully merge this!

According to previous experience, we push the button to merge PR in github.
And I misunderstand  https://github.com/solettaproject/soletta/wiki/Contributing#contributions-flow just states that how a soletta developer push his own source code from local reviewed_branch not for every review source code PR which need to do these steps too. When I git log in the master branch,  I found that we push the merge button wrongly.
And I want to repair the commit statement by trying two methods:

git reset --hard HEAD^  & git apply 1443.patch & git push  (failed because protected branch hook declined)
git checkout reviewed_branch & rebase the branch & git commit -s --amend(modify the commit message) & git push origin HEAD:master (failed because a pushed branch tip is behind its remote)
However, both cannot take effect .
So can anyone tell me how to remedy this commit in the master branch?

Hi,
We are not using merge commits, that's why we don't push Github merge button - we rebase our changes on top of current master and send it with git push.
As we also do not allow 'force pushes' on master, I'd say that there's nothing to do about this merge - but be more careful next time =D

@guchaojie that's ok. Next time, when you face any problem, any unexpected situation, or you see something doesn't seem clear, please talk to us first. There's nothing we can do about what was done. We shouldn't change master branch history, never. Lot's of developers we'll be working on top of this branch, so you may affect the work of all of them. It's a bad practice. Fortunately github allows us to deny this kind of change, and we're using this feature.
In our instructions there isn't anything about using a  "merge button", right? There are a few git commands that should be used instead.
We prefer to keep our repository history more linear.
Anyway, I've asked another engineer to review these instructions to make it more clear.
Please feel free to make suggestion as well, or even edit the wiki page to avoid that others developers make the same mistake in the future.
Thanks

Bruno Dilly notifications@github.com [2016-02-25 07:08:45 -0800]:

@guchaojie that's ok. Next time, when you face any problem, any unexpected situation, or you see something doesn't seem clear, please talk to us first. There's nothing we can do about what was done. We shouldn't change master branch history, never. Lot's of developers we'll be working on top of this branch, so you may affect the work of all of them. It's a bad practice. Fortunately github allows us to deny this kind of change, and we're using this feature.
In our instructions there isn't anything about using a  "merge button", right? There are a few git commands that should be used instead.
We prefer to keep our repository history more linear.
Anyway, I've asked another engineer to review these instructions to make it more clear.
Please feel free to make suggestion as well, or even edit the wiki page to avoid that others developers make the same mistake in the future.

And it's done. I hope we're more clear now.

Thanks

Reply to this email directly or view it on GitHub:
https://github.com/solettaproject/soletta/pull/1443#issuecomment-188827779

--
Gustavo Lima Chaves
Intel - Open Source Technology Center

authors: barbieri bdilly edersondisouza glima guchaojie mbelluzzo

repo: solettaproject/soletta


text:
Unable to GET JSON-LD Verifiable Credential in Turtle

After having PUT a JSON-LD Verifiable Credential with the following example code ...
PUT http://localhost:3000/creds.jsonld HTTP/1.1
Content-Type: application/ld+json

{
  "@context": [ "https://www.w3.org/2018/credentials/v1" ],
  "type": "VerifiableCredential",
  "id": "http://localhost:3000/creds#1",
  "proof": {
    "type": "RsaSignature2018",
    "verificationMethod": "http://localhost:3000/keys#1",
    "jws": "eyJhbGciOiJSUzI1NiIsImI2NCI6ZmFsc2UsImNyaXQiOlsiYjY0Il19..TCYt5XsITJX1CxPCT8yAV-TVkIEq_PbChOMqsLfRoPsnsgw5WEuts01mq-pQy7UJiN5mgRxD-WUcX16dUEMGlv50aqzpqh4Qktb3rk-BuQy72IFLOqV0G_zS245-kronKb78cPN25DGlcTwLtjPAYuNzVBAh4vGHSrQyHUdBBPM"
  }
}

... a GET request with the Accept header set to text/turtle fails with the following error:
[BaseHttpServerFactory] info: Received GET request for /creds.jsonld
[WebAclAuthorizer] info: Reading ACL statements from http://localhost:3000/.acl
[StreamUtil] warn: Piped stream errored with Attempted to override the protected keyword proof from "https://w3id.org/security#proof" to "sec:proof"
[StreamUtil] warn: Piped stream errored with Attempted to override the protected keyword proof from "https://w3id.org/security#proof" to "sec:proof"
[StreamUtil] warn: Piped stream errored with Attempted to override the protected keyword proof from "https://w3id.org/security#proof" to "sec:proof"
[BasicResponseWriter] error: Writing to HttpResponse failed with message Attempted to override the protected keyword proof from "https://w3id.org/security#proof" to "sec:proof"

This error originates in the JSON-LD parser library. Do I take this issue to that repo, or is this something related to how the library is used?

@rubensworks do you have an idea?

Looks like a missed edge-case in https://github.com/rubensworks/jsonld-context-parser.js/.
For reference, this is probably where things go wrong: https://github.com/rubensworks/jsonld-context-parser.js/blob/master/lib/ContextParser.ts#L281-L319
Probably requires an additional normalization/expansion step.

Fixed in jsonld-context-parser@2.1.3.
(A lockfile reset should be fine if the fix is urgent)

authors: joachimvh rubensworks woutermont

repo: solid/community-server


text:
Basic authentication with passwords is deprecated

Hello
The application is throwing this error on JIRA cloud login:
System.Security.Authentication.AuthenticationException: Response Content: Basic authentication with passwords is deprecated.  For more information, see: https://developer.atlassian.com/cloud/confluence/deprecation-notice-basic-auth/
at Atlassian.Jira.Remote.JiraRestClient.GetValidJsonFromResponse(IRestRequest request, IRestResponse response)
at Atlassian.Jira.Remote.JiraRestClient.d__11.MoveNext()
when using:
jira-export -u jiraaccount@some.domain -p xxxxxxx --url https://my.jira.url --config config-scrum.json --force
Is there a fix for this?

Try https://github.com/solidify/jira-azuredevops-migrator/issues/690

Try https://github.com/solidify/jira-azuredevops-migrator/issues/690

authors: Alexander-Hjelm yogeshmoodoo

repo: solidify/jira-azuredevops-migrator


text:
feat: update to jest 27

This updates the jest-solid dependency as well as 'jest' and 'babel-jest' to support version 27.
All tests pass, I once again didn't touch the package.json version.

Thanks again. Published in 0.2.1.

authors: StalkAltan ryansolid

repo: solidjs/solid-testing-library


text:
When Google Translate is enabled on a website, SolidJS can't update some of the DOM

Describe the bug

I go on a Swedish website that uses SolidJS under the hood.
I don't speak Swedish, so the built-in Google Translate feature of Chrome kicks in and translates the website I'm on.
As soon as the translation is enabled, some of the information on the page is off.

Your Example Website or App
https://playground.solidjs.com/anonymous/2c6ddc27-d592-4f8d-b3b4-eec01d4a5b12
Steps to Reproduce the Bug or Issue

Go to https://playground.solidjs.com/anonymous/2c6ddc27-d592-4f8d-b3b4-eec01d4a5b12.
Export the project as a .zip.
Unzip the project.
Go to the folder.
yarn.
yarn start.
Go to http://localhost:5173/ using Chrome.
Observe the counters going up.
Enable the Google Translate translation.
Observe the counters stopping.

Expected behavior
As a user, I expect the website to keep working even with Google Translate enabled, but it's currently not the case.
Screenshots or Videos

DOM without Google Translate enabled:

DOM with Google Translate enabled:

Platform

OS: macOS
Browser: Chrome
Version: Version 108.0.5359.124 (Official Build) (arm64)

Additional context
I saw @ryansolid mentioned Google Translate messing things up here: https://github.com/solidjs/solid/issues/1122#issuecomment-1202115320.

It's most likely because Google Translate replaces the text nodes and Solid requires the node's position to apply updates. Once the translation happens, the text node is removed and Solid cannot append the new text node given that the original text node was missing.

I thought that the issue was caused by solid not keeping a reference to the Text node but rather walking to it via parent.ChildNodes (see screenshot) but you are right, google translate also straight up replaces the text node.

I think one way to fix it would be to get google translate to use the same text node (and just replace the content) and solid to keep a reference to it?

Yeah but will they do that? Other programs messing with the DOM is pretty problematic. The only thing we could do is check if the textNode has a parentNode before going into the optimization. Just trying to think if that falls down anywhere.

Yeah React and countless other frameworks are waiting on issues like: https://bugs.chromium.org/p/chromium/issues/detail?id=872770
I'm long to close this one unfortunately as there is nothing to be done it looks like except hope Google does something here.

TBF because text nodes are immutable (correct me if I'm wrong), this would just be deemed unfixable

@ryansolid fair point. I think it would be good to meet google halfways and propose a middle ground that would work for both sides instead of putting it entirely on them (if you check the issue you linked someone claims the DOM is inherently mutable and it's 100% on "framework authors"). But it's hard to solve from solid's position. I proposed a way for google to solve it in their bug but there might be a better solution. Let's see how it goes.
@lxsmnsyc text nodes are not immutable, if you check the solid-js code in my screenshot above you can see that solid-js actually mutates them without creating new ones by changing https://developer.mozilla.org/en-US/docs/Web/API/CharacterData/data

authors: arnaud-cortisse danieltroger lxsmnsyc ryansolid

repo: solidjs/solid


text:
Completes NETWORK_FILTER support (TCP), which was present in BaseCont…

…ext but not wired to the ABI.
Testing: Works for us on Istio 1.8 with a configuration like the following:
apiVersion: networking.istio.io/v1alpha3
kind: EnvoyFilter
spec:
  configPatches:
    - applyTo: NETWORK_FILTER
      match:
        listener:
          filterChain:
            filter:
              name: "envoy.tcp_proxy"

I'd appreciate your review.

I'd appreciate your review.

sorry for the delay! thank you for the PR!

sorry for the delay! thank you for the PR!

authors: chandlernine yuval-k

repo: solo-io/proxy-runtime


text:
🛑 svet.kz is down

In 8bb3cd8, svet.kz (https://svet.kz/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: svet.kz is back up in c38aa16.


text:
Word wrap in cell

Hi,
How can i implement wrapping in long sentences. Line height is not a problem.

Hi! Check out the long text example in the examples/examples.js and the demo page for how it looks like. Basically you can set the overflow option to linebreak, like this:
var cols = [
    {title: "ID", key: "id"},
    {title: "Name", key: "first_name"},
    ...
];
var data = [{
    "id": 1,
    "first_name": "Russell",
    ...
}, {
    "id": 2,
    "first_name": "Laura",
    ....
}];

doc.autoTable(cols, data, {overflow: 'linebreak'});

I hope my answer solved your issue. If not, feel free to open the issue again.

repo: someatoms/jsPDF-AutoTable


text:
[resotocore][feat] clearer Jira custom command parameter names

Description
Introduces clearer Jira custom command parameter names
To-Dos

[x] Add test coverage for new or updated functionality
[x] Lint and test with tox
[x] Document new or updated functionality (someengineering/resoto.com#380)

Code of Conduct
By submitting this pull request, I agree to follow the code of conduct.

Also want to remove chunk 25, as discussed on Discord.

authors: TheCatLady anjafr

repo: someengineering/resoto


text:
Fix: Make meta-viewport rule work with viewport-fit property

From https://webkit.org/blog/7929/designing-websites-for-iphone-x/

The first new feature is an extension to the existing viewport meta tag called viewport-fit, which provides control over the insetting behavior. viewport-fit is available in iOS 11.
The default value of viewport-fit is auto, which results in the automatic insetting behavior  seen above. In order to disable that behavior and cause the page to lay out to the full size of the screen, you can set viewport-fit to cover. After doing so, our viewport meta tag now looks like this:
<meta name='viewport' content='initial-scale=1, viewport-fit=cover'>

(See also: https://www.w3.org/TR/css-round-display-1/#viewport-fit-descriptor)
Using that viewport-fit property currently generates an error because it needs to be added to metaviewport-parser (see: https://github.com/dontcallmedom/metaviewport-parser/issues/5).

Related: In a discussion with @molant  we agreed that the meta-viewport rule should not enforce the usage of  the viewport-fit property, as blindly using it without any other adjustments can potentially create a bad user experience (i.e. part of the website may be obstructed by the sensor housing).

See also: https://www.w3.org/TR/css-round-display-1/#viewport-fit-descriptor

Using that viewport-fit property currently generates an error because it needs to be added to metaviewport-parser (see: dontcallmedom/metaviewport-parser#5).

I've open a pull request: https://github.com/dontcallmedom/metaviewport-parser/pull/6.

repo: sonarwhal/sonar


text:
Investigate displayName

It should show something friendly.

Typo, referenced the wrong issue

repo: sonaye/qaf


text:
Ternary shorthands parsing

Are you planning to add support for ternary shorthands parsing?
I mean expressions like "a = b ? c : d"
Thanks!

It does already, but it is the assign that is not supported.

@EricSmekens are you planning to implement assign?

Probably not.
Soney meant this library as a lightweight parser of Javascript expressions, and no operations.
Have a look into Esprima if you look for this functionality.

jsep does not parse JavaScript operations (e.g. var a = b;) nor blocks of code (e.g. if (...) {...}.) Think of jsep as a tool to parse the kinds of expressions that would be written in individual Excel cells.

authors: EricSmekens dimaninc

repo: soney/jsep


text:
Moonshot 自动填充的模型类型错误

例行检查

[x] 我已确认目前没有类似 issue
[x] 我已确认我已升级到最新版本
[x] 我已完整查看过项目 README，尤其是常见问题部分
[x] 我理解并愿意跟进此 issue，协助测试和提供反馈
[x] 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

问题描述
在v0.6.2版本中，Moonshot 自动填充的模型类型错误。在更正模型类型并填入相应的密钥之后，通过测试渠道进行验证时，结果显示【401鉴权失败】。
可能出问题的相关代码
复现步骤
【渠道】-【新建渠道】-选择【Moonshot 】-填入【Key】-【提交】
预期结果
正确填充，同时能够正常访问渠道。
相关截图

已经有 PR 修复了哈

更新版本即可

authors: Alwaysbesideyou songquanpeng

repo: songquanpeng/one-api


text:
国产化

例行检查

[ ] 我已确认目前没有类似 issue
[ ] 我已确认我已升级到最新版本
[ ] 我已完整查看过项目 README，已确定现有版本无法满足需求
[ ] 我理解并愿意跟进此 issue，协助测试和提供反馈
[ ] 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

功能描述
支持国产化服务器及系统， 支持aarch64架构，华为鲲鹏服务器
应用场景

和国产化有什么关系？
Go和Node都支持aarch64架构，直接构建就好。
哪个依赖报错就找对应的依赖包提issue。

authors: dyyxcc imshuhao


text:
readme 中宝塔部署部署教程 # 175 issue 无法访问，出现404，如下图：

例行检查

[x] 我已确认目前没有类似 issue
[x] 我已确认我已升级到最新版本
[x] 我已完整查看过项目 README，尤其是常见问题部分
[x] 我理解并愿意跟进此 issue，协助测试和提供反馈
[x] 我理解并认可上述内容，并理解项目维护者精力有限，不遵循规则的 issue 可能会被无视或直接关闭

问题描述
readme 中宝塔部署部署教程 # 175 issue 无法访问，出现404，如下图：
复现步骤
预期结果
相关截图

我也遇到了

这个#175是不是被删了


text:
[SAIP4] Add missing ACL Ingress constraints.

Build and Test Results:
...
INFO: Elapsed time: 133.329s, Critical Path: 44.87s
INFO: 201 processes: 230 linux-sandbox, 18 local.
INFO: Build completed successfully, 201 total actions
//gutil:collections_test                                                 PASSED in 0.5s
//gutil:io_test                                                          PASSED in 0.5s
//gutil:proto_matchers_test                                              PASSED in 0.6s
//gutil:proto_ordering_test                                              PASSED in 0.5s
//gutil:proto_test                                                       PASSED in 0.5s
//gutil:status_matchers_test                                             PASSED in 0.5s
//gutil:test_artifact_writer_test                                        PASSED in 0.8s
//gutil:testing_test                                                     PASSED in 0.5s
//gutil:timer_test                                                       PASSED in 5.0s
//gutil:version_test                                                     PASSED in 0.9s
//lib:basic_switch_test                                                  PASSED in 0.8s
//lib:ixia_helper_test                                                   PASSED in 1.1s
//lib/basic_traffic:basic_p4rt_util_test                                 PASSED in 0.9s
//lib/basic_traffic:basic_traffic_test                                   PASSED in 14.9s
//lib/gnmi:gnmi_helper_test                                              PASSED in 2.8s
//lib/gnoi:gnoi_helper_test                                              PASSED in 0.5s
//lib/p4rt:p4rt_port_test                                                PASSED in 0.5s
//lib/p4rt:p4rt_programming_context_test                                 PASSED in 0.8s
//lib/utils:generic_testbed_utils_test                                   PASSED in 1.2s
//lib/utils:json_utils_test                                              PASSED in 0.5s
//lib/validator:validator_backend_test                                   PASSED in 0.5s
//lib/validator:validator_lib_test                                       PASSED in 25.8s
//p4_fuzzer:constraints_util_integration_test                            PASSED in 0.7s
//p4_fuzzer:fuzz_util_test                                               PASSED in 3.5s
//p4_fuzzer:oracle_util_test                                             PASSED in 1.0s
//p4_fuzzer:switch_state_test                                            PASSED in 0.7s
//p4_fuzzer:table_entry_key_test                                         PASSED in 0.1s
//p4_pdpi:built_ins_test                                                 PASSED in 0.5s
//p4_pdpi:entity_keys_test                                               PASSED in 0.5s
//p4_pdpi:ir_properties_test                                             PASSED in 0.5s
//p4_pdpi:ir_to_ir_test                                                  PASSED in 0.6s
//p4_pdpi:ir_tools_test                                                  PASSED in 0.7s
//p4_pdpi:names_test                                                     PASSED in 0.8s
//p4_pdpi:p4_runtime_matchers_test                                       PASSED in 0.6s
//p4_pdpi:reference_annotations_test                                     PASSED in 0.7s
//p4_pdpi:references_test                                                PASSED in 0.7s
//p4_pdpi:sequencing_util_test                                           PASSED in 0.6s
//p4_pdpi/netaddr:ipv4_address_and_network_address_test                  PASSED in 0.5s
//p4_pdpi/netaddr:ipv6_address_test                                      PASSED in 0.6s
//p4_pdpi/netaddr:mac_address_test                                       PASSED in 0.5s
//p4_pdpi/packetlib:packetlib_fuzzer_test                                PASSED in 16.3s
//p4_pdpi/packetlib:packetlib_matchers_test                              PASSED in 0.5s
//p4_pdpi/packetlib:packetlib_test                                       PASSED in 0.1s
//p4_pdpi/packetlib:packetlib_test_runner                                PASSED in 0.1s
//p4_pdpi/packetlib:packetlib_unit_test                                  PASSED in 2.1s
//p4_pdpi/string_encodings:bit_string_test                               PASSED in 0.5s
//p4_pdpi/string_encodings:byte_string_test                              PASSED in 0.5s
//p4_pdpi/string_encodings:decimal_string_test                           PASSED in 0.0s
//p4_pdpi/string_encodings:decimal_string_test_runner                    PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test                               PASSED in 0.0s
//p4_pdpi/string_encodings:hex_string_test_runner                        PASSED in 0.0s
//p4_pdpi/string_encodings:readable_byte_string_test                     PASSED in 0.5s
//p4_pdpi/testing:helper_function_test                                   PASSED in 0.6s
//p4_pdpi/testing:info_test                                              PASSED in 0.1s
//p4_pdpi/testing:info_test_runner                                       PASSED in 0.1s
//p4_pdpi/testing:main_pd_test                                           PASSED in 0.0s
//p4_pdpi/testing:mock_p4_runtime_server_test                            PASSED in 1.6s
//p4_pdpi/testing:old_get_entries_unreachable_from_roots_with_matchfield_reference_test PASSED in 0.1s
//p4_pdpi/testing:old_get_entries_unreachable_from_roots_with_matchfield_reference_test_runner PASSED in 0.1s
//p4_pdpi/testing:packet_io_test                                         PASSED in 0.1s
//p4_pdpi/testing:packet_io_test_runner                                  PASSED in 0.1s
//p4_pdpi/testing:references_test                                        PASSED in 0.1s
//p4_pdpi/testing:references_test_runner                                 PASSED in 0.1s
//p4_pdpi/testing:rpc_test                                               PASSED in 0.1s
//p4_pdpi/testing:rpc_test_runner                                        PASSED in 0.1s
//p4_pdpi/testing:sequencing_test                                        PASSED in 0.1s
//p4_pdpi/testing:sequencing_test_runner                                 PASSED in 0.1s
//p4_pdpi/testing:sequencing_util_test                                   PASSED in 0.1s
//p4_pdpi/testing:sequencing_util_test_runner                            PASSED in 0.1s
//p4_pdpi/testing:table_entry_gunit_test                                 PASSED in 0.7s
//p4_pdpi/testing:table_entry_test                                       PASSED in 0.1s
//p4_pdpi/testing:table_entry_test_runner                                PASSED in 0.1s
//p4_pdpi/utils:annotation_parser_test                                   PASSED in 0.5s
//p4_pdpi/utils:ir_test                                                  PASSED in 0.5s
//p4_symbolic/bmv2:ipv4_routing_exact_test                               PASSED in 0.1s
//p4_symbolic/bmv2:ipv4_routing_subset_test                              PASSED in 0.1s
//p4_symbolic/bmv2:port_hardcoded_exact_test                             PASSED in 0.0s
//p4_symbolic/bmv2:port_hardcoded_subset_test                            PASSED in 0.1s
//p4_symbolic/bmv2:port_table_exact_test                                 PASSED in 0.0s
//p4_symbolic/bmv2:port_table_subset_test                                PASSED in 0.1s
//p4_symbolic/bmv2:reflector_exact_test                                  PASSED in 0.0s
//p4_symbolic/bmv2:reflector_subset_test                                 PASSED in 0.8s
//p4_symbolic/bmv2:set_invalid_exact_test                                PASSED in 0.0s
//p4_symbolic/bmv2:set_invalid_subset_test                               PASSED in 0.1s
//p4_symbolic/ir:ipv4_routing_test                                       PASSED in 0.1s
//p4_symbolic/ir:port_hardcoded_test                                     PASSED in 0.0s
//p4_symbolic/ir:port_table_test                                         PASSED in 0.0s
//p4_symbolic/ir:reflector_test                                          PASSED in 0.0s
//p4_symbolic/ir:set_invalid_test                                        PASSED in 0.0s
//p4_symbolic/symbolic:ipv4_routing_test_output                          PASSED in 0.0s
//p4_symbolic/symbolic:port_hardcoded_test_output                        PASSED in 0.1s
//p4_symbolic/symbolic:port_table_test_output                            PASSED in 0.0s
//p4_symbolic/symbolic:reflector_test_output                             PASSED in 0.0s
//p4_symbolic/tests:sai_p4_component_test                                PASSED in 1.2s
//p4rt_app/event_monitoring:app_state_db_port_table_event_test           PASSED in 0.9s
//p4rt_app/event_monitoring:app_state_db_send_to_ingress_port_table_event_test PASSED in 1.0s
//p4rt_app/event_monitoring:config_db_cpu_queue_table_event_test         PASSED in 1.0s
//p4rt_app/event_monitoring:config_db_node_cfg_table_event_test          PASSED in 1.0s
//p4rt_app/event_monitoring:config_db_port_table_event_test              PASSED in 1.0s
//p4rt_app/event_monitoring:debug_data_dump_events_test                  PASSED in 0.9s
//p4rt_app/event_monitoring:state_verification_events_test               PASSED in 1.0s
//p4rt_app/p4runtime:cpu_queue_translator_test                           PASSED in 0.5s
//p4rt_app/p4runtime:ir_translation_test                                 PASSED in 0.7s
//p4rt_app/p4runtime:p4info_verification_schema_test                     PASSED in 0.7s
//p4rt_app/p4runtime:p4info_verification_test                            PASSED in 0.9s
//p4rt_app/p4runtime:packetio_helpers_test                               PASSED in 0.9s
//p4rt_app/p4runtime:resource_utilization_test                           PASSED in 0.8s
//p4rt_app/sonic:app_db_acl_def_table_manager_test                       PASSED in 0.7s
//p4rt_app/sonic:app_db_manager_test                                     PASSED in 0.8s
//p4rt_app/sonic:app_db_to_pdpi_ir_translator_test                       PASSED in 0.8s
//p4rt_app/sonic:hashing_test                                            PASSED in 0.7s
//p4rt_app/sonic:packet_replication_entry_translation_test               PASSED in 0.7s
//p4rt_app/sonic:packetio_impl_test                                      PASSED in 0.6s
//p4rt_app/sonic:packetio_port_test                                      PASSED in 0.6s
//p4rt_app/sonic:response_handler_test                                   PASSED in 0.7s
//p4rt_app/sonic:state_verification_test                                 PASSED in 0.7s
//p4rt_app/sonic:vrf_entry_translation_test                              PASSED in 0.7s
//p4rt_app/sonic/adapters:fake_sonic_db_table_test                       PASSED in 0.1s
//p4rt_app/sonic/adapters:fake_warm_boot_state_adapter_test              PASSED in 0.1s
//p4rt_app/tests:acl_table_test                                          PASSED in 1.7s
//p4rt_app/tests:action_set_test                                         PASSED in 1.4s
//p4rt_app/tests:api_access_test                                         PASSED in 1.2s
//p4rt_app/tests:arbitration_test                                        PASSED in 1.4s
//p4rt_app/tests:cpu_queue_name_and_id_test                              PASSED in 2.3s
//p4rt_app/tests:debug_data_dump_test                                    PASSED in 1.3s
//p4rt_app/tests:fixed_l3_tables_test                                    PASSED in 3.5s
//p4rt_app/tests:forwarding_pipeline_config_test                         PASSED in 7.4s
//p4rt_app/tests:grpc_behavior_test                                      PASSED in 5.5s
//p4rt_app/tests:p4_constraints_test                                     PASSED in 0.3s
//p4rt_app/tests:p4_constraints_test_runner                              PASSED in 0.3s
//p4rt_app/tests:p4_programs_test                                        PASSED in 1.9s
//p4rt_app/tests:packet_replication_table_test                           PASSED in 2.6s
//p4rt_app/tests:packetio_test                                           PASSED in 4.5s
//p4rt_app/tests:port_name_and_id_test                                   PASSED in 3.9s
//p4rt_app/tests:resource_limits_test                                    PASSED in 4.9s
//p4rt_app/tests:response_path_test                                      PASSED in 4.4s
//p4rt_app/tests:role_test                                               PASSED in 1.3s
//p4rt_app/tests:state_verification_test                                 PASSED in 2.6s
//p4rt_app/tests:vrf_table_test                                          PASSED in 2.2s
//p4rt_app/tests/lib:app_db_entry_builder_test                           PASSED in 0.0s
//p4rt_app/utils:event_data_tracker_test                                 PASSED in 0.0s
//p4rt_app/utils:table_utility_test                                      PASSED in 0.7s
//sai_p4/instantiations/google:clos_stage_test                           PASSED in 0.5s
//sai_p4/instantiations/google:fabric_border_router_p4info_up_to_date_test PASSED in 0.0s
//sai_p4/instantiations/google:middleblock_p4info_up_to_date_test        PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_build_test      PASSED in 0.0s
//sai_p4/instantiations/google:sai_nonstandard_platforms_cc_test         PASSED in 0.6s
//sai_p4/instantiations/google:sai_p4info_fetcher_test                   PASSED in 0.6s
//sai_p4/instantiations/google:sai_p4info_test                           PASSED in 0.9s
//sai_p4/instantiations/google:sai_pd_proto_test                         PASSED in 0.0s
//sai_p4/instantiations/google:sai_pd_util_test                          PASSED in 0.5s
//sai_p4/instantiations/google:tor_p4info_up_to_date_test                PASSED in 0.1s
//sai_p4/instantiations/google:union_p4info_up_to_date_test              PASSED in 0.1s
//sai_p4/instantiations/google:wbb_p4info_up_to_date_test                PASSED in 0.0s
//sai_p4/instantiations/google/test_tools:table_entry_generator_helper_test PASSED in 1.3s
//sai_p4/instantiations/google/test_tools:test_entries_test              PASSED in 0.8s
//sai_p4/tools:p4info_tools_test                                         PASSED in 0.5s
//sai_p4/tools:packetio_tools_test                                       PASSED in 0.7s
//thinkit:bazel_test_environment_test                                    PASSED in 0.5s
//thinkit:generic_testbed_test                                           PASSED in 0.9s
//thinkit:mock_control_device_test                                       PASSED in 0.6s
//thinkit:mock_generic_testbed_test                                      PASSED in 0.7s
//thinkit:mock_mirror_testbed_test                                       PASSED in 0.7s
//thinkit:mock_ssh_client_test                                           PASSED in 0.0s
//thinkit:mock_switch_test                                               PASSED in 0.6s
//thinkit:mock_test_environment_test                                     PASSED in 0.1s
//thinkit:switch_test                                                    PASSED in 0.8s
//sai_p4/instantiations/google/test_tools:table_entry_generator_test     PASSED in 44.9s
Stats over 5 runs: max = 44.9s, min = 1.0s, avg = 20.5s, dev = 19.8s
//sai_p4/instantiations/google/tests:p4_constraints_integration_test     PASSED in 0.8s
Stats over 5 runs: max = 0.8s, min = 0.6s, avg = 0.7s, dev = 0.0s
Executed 169 out of 169 tests: 169 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these aINFO: Build completed successfully, 201 total actions
sdivya@e25b91aea928:/sonic/src/sonic-p4rt/sonic-pins$
Keyword Check:
sdivya@eonms6vm1:~/sonic_sep6/sonic-buildimage/src/sonic-p4rt/sonic-pins$ ~/keyword_check.sh .
Keyword check Passed.

Co-authored-by: Jonathan Dilorenzo dilo@google.com

repo: sonic-net/sonic-pins


text:
test_vxlan_ecmp.py failed occasionally

test_vxlan_ecmp.py failed occasionally. It appears that vpp_vxlan_tunnel_add_del of a new tunnel sometimes mistakenly returns the sw_ifindex of the vxlan tunnel deleted right before it. The suspicion is that set_reply_status in vl_api_bfd_udp_session_event_t_handler, which is unsolicited event callback, messes up the call sequence.

I was testing vxlan-related use cases recently, and I just found it. I am checking the code. If you have code updates, please @ me and I want to learn from it. If I can fix the whole problem, I will also submit a PR. Thank you very much

@linqingxuan, I have created a PR to fix this issue. With the fix, the sonic mgmt test passed 5 times in a roll. Please take a look.

I applied this patch and it did solve the problem. I recently had a requirement to have different vxlan  macs based on the inner vxlan subnet.
For example

1 2 3 are three VMs, they have different MACs, but they do not accept vxlan arp layer 2 learning, which is quite awkward. I am currently using centec and broadcom chip switches, which can accept routing with MACs. I recently read the vpp source code and it seems that it does not support this scenario. In the tofino chip, I used acl to modify the inner MAC in egress.
If this scenario should be modified in vpp? If you can give me some advice, I will be very grateful

用这个可以吗https://docs.fd.io/vpp/17.04/clicmd_src_vnet_l2.html

Is it okay to use this?https://docs.fd.io/vpp/17.04/clicmd_src_vnet_l2.html

Is it inner source Mac or destination Mac that you want to change based on subnet? And again, is it subnet of source IP or destination IP?

base inner destination IP change destination Mac

I have refined the content of the picture. As shown in the picture, I expect to dynamically change the inner mac of the datagram based on vni and inner ip. They are a vm under bm, and bm has closed vxlan layer 2 learning.

sonic supports setting dmac in vxlan ecmp route: https://github.com/sonic-net/SONiC/blob/master/doc/vxlan/Vxlan_hld.md#22-app-db. In your examples, you need to create 3 entries in VNET_ROUTE_TUNNEL_TABLE, each matching the prefix listed above and setting dmac accordingly.
It is not supported in sonic-vpp currently but should not be too difficult. Basically, when it programs ip neighbour (https://github.com/sonic-net/sonic-platform-vpp/blob/main/docs/HLD/vxlan-vnet.md#vm-to-baremetal), use the Mac passed in from SAI attribute instead of hardcoded 00:00:00:00:00:01 or router MAC is that's configured.
Is remote vtep also sonic-vpp? you cannot treat it as l3 vxlan because that will remove inner ether header. I guess you need to map the vxlan to vlan in the remote vtep to do l2 forwarding in order to preserve the inner ether. That's is not supported in sonic-vpp.

I looked at it carefully and you are not quite right. My problem is that the same vtep has different inner dst macs. The remote end is not sonic-vpp. It is actually an old LB service. Because there are customers on it, I can't modify its logic for the time being.

I think I would be more suitable to find a L2 rewrite dest MAC.

thank you very much

I think you need to design it in the frame of SONiC. Otherwise, it will be too much work in control plane. With vxlan vnet tunnel route, I am not sure if you can have multiple such routes pointing to the same VTEP (same address and VNI). You can see if SONIC allows it or not. If it does, you can explore how to make it work in sonic-vpp. In vpp data plane, this should be supported. Basically, multiple ip neighbour with different nexthop address and Mac pointing to the same vxlan tunnel.
You can explore l2 rewrite. But I am not sure how to fit it into SONiC.

I think the sonic layer is easy to modify, but the vpp layer, hahahahahaha, I just want to write a simple plug-in to modify it directly,

authors: linqingxuan yue-fred-gao

repo: sonic-net/sonic-platform-vpp


text:
As a player, I want to test my knowledge on a specific topic by selecting one of all available topics in order to test and deepen my knowledge

Acceptance Criteria:

[x] The topics to choose from are all available topics
[x] The selection is shown before a new single player game starts
[x] All following questions are of the chosen topic

Dev Tasks:

[x] sopra-fs23-group-10/sopra-fs23-group-10-client#43
[x] sopra-fs23-group-10/sopra-fs23-group-10-client#44
[x] sopra-fs23-group-10/sopra-fs23-group-10-client#45
[x] sopra-fs23-group-10/sopra-fs23-group-10-server#105
[x] #113

All dev tasks are completed and acceptance criterias are met. Issue is therefore closed.


text:
Async loader

const asyncLoader = new AsyncLoader(p1)

await asyncLoader
asyncLoader.data // => get async loaded value

https://github.com/soraLib/sa-lambda/commit/f365c78d96a9be9162dfc6eb92e86bb7a5e21d87

repo: soraLib/sa-lambda


text:
Fix track of opened ws connections

We see that number of opened ws sessions is not decreasing when they are being closed. Need to fix that

It's not an issue per se, but a specifics of metrics reporting.

authors: GaroRobe kamilsa

repo: soramitsu/kagome


text:
Allow methods on Dir to use Pathname

Motivation
Some of the functions on Dir can take Pathname objects in addition to strings.
Test plan
Just an RBI change so not much to test.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build result here:
→ https://go/builds/bui_HbGuyRT3iQYtFd

authors: elliottt mgriisser

repo: sorbet/sorbet


text:
Fix missing generics arity error

The idea is that we're not supposed to short circuit this function, because it
reports an arity mismatch error we care about.
While I was there, I decided to make the error a little more informative.
Motivation

Fixes #6507
Test plan

See included automated tests.

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_Nd4rWKuc5FfFqW
→ https://go/builds/bui_Nd4rNOI8R4s7BV

We have a policy of testing changes to Sorbet against Stripe's codebase before
merging them. I've kicked off a test run for the current PR.  When the build
finishes, I'll share with you whether or how it failed. Thanks!
Stripe employees can see the build results here:
→ https://go/builds/bui_Nd9vWSChv0eyBR
→ https://go/builds/bui_Nd9wGMDf3Ka2UJ

authors: jez neilparikh


text:
fix issues when Exception#backtrace_locations returns nil

This reverts parts of #7710.
cc @casperisfine
Motivation

The changes to this file in #7710 cause errors when backtrace_locations is nil.  It's not obvious to me why backtrace_locations is nil, but it is on a number of Stripe's internal tests.  I see references in the Ruby source to setting backtrace_locations to nil when exceptions are marshaled (!), but AFAICT we are not going through marshaling in the codepaths that are erroring.
This is error-handling code, so I'm not too concerned with the efficiency win from iterating over backtrace_locations rather than taking apart the backtrace itself.
Test plan

I was not able to write a reproducible test case for this.

Ah sorry, I should have thought of that.
This generally comes from raising exceptions with a backtrace from another exception, e.g.:
raise SomeError, previous_error.message, previous_error.backtrace

The above exception will have #backtrace_location return nil.
I recently implemented a way to preserve it though: https://github.com/ruby/ruby/pull/10017, but it will take a long time before most code is migrated.

https://github.com/sorbet/sorbet/pull/7779

authors: casperisfine froydnj


text:
🛑 CPH.dev is down

In f22b25d, CPH.dev (https://cph.dev) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CPH.dev is back up in 57c3b87 after 972 days, 3 hours, 54 minutes.


text:
MAUDE backend

To do:

[ ] Add unit tests
[ ] User documentation
[ ] Merging cxc and maude streams
[ ] Units handling
[ ] Handle requests for 5min or daily stats
[ ] Handle differences in available MSIDs in the two backends

This branch does not pass unit tests.  Run py.test from the command line in the top-level directory of the repo.

@gmrehbein - ignore the (now-deleted) comment about unit tests failing.  That was intended for the maude repo.

@gmrehbein - I added a to-do list in the description for this PR.

Superceded by #125.

authors: gmrehbein taldcroft


text:
SOT 164: Add Parser

Remember to merge #12 before merging this branch

Need someone to review this ASAP

repo: sota-zk-labs/zkp-implementation


text:
ScrollArea content should not get the focus when the user is scrolling

Hello,
Thank you for the nice plugin.
I'm wondering why the ScrollArea content is getting the focus by default on mouse wheel ? It breaks the default behavior of the browser. If an input field has the focus it should not lose it if the user is scrolling.
Best regards

any solution?

+1

I made fork and fix this problem
https://github.com/ScriptArtist/reactScrollbar
npm install react-scrollbar-homy

This behaviour causes another problem:
When height of the scroll content more than window height Safari tries to fit it and scrolls page itself.
How to reproduce:
Open https://souhe.github.io/reactScrollbar/ in Safari desktop
Make window small. I made it 278 height.
When you start scrolling demo items you will notice instant page scrolling as well
This is very annoying when you have component with scrolling somewhere in the middle of the page

authors: RoeyMaor ScriptArtist cedricalfonsi limpbrains

repo: souhe/reactScrollbar


text:
Playlist created, no songs

I am having an odd problem - things seem to work ok, the log shows songs being match and a playlist being created.
When I check in GM when it is complete, there is indeed a playlist created, but the contents are empty.
I am using a 2FA account, with a generated password. Logs + CSV are in the attached zip, is there somewhere else I can look for error logs?
playlist+log.zip

NM. forgot to put the trackNumber switch in for Rdio :)

Hi @glasspear, what's the "trackNumber switch" that you mentioned here? I'm attempting to import Rdio playlists as well and am also getting empty playlists. Is there something I need to change in the CSV they provided? Thanks!

authors: KurtTrowbridge glasspear

repo: soulfx/gmusic-playlist


text:
Fix playground share link

Description

Closes #2526
Type of change

[x] Bug fix (non-breaking change which fixes an issue)

How to test

Check that share links work properly
Checklist

[x] I have tested this code

Pull Request Test Coverage Report for Build 5333905404
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 36.494%

Totals

Change from base Build 5333159135:
0.0%

Covered Lines:
5267

Relevant Lines:
13577

💛  - Coveralls

authors: chownces coveralls

repo: source-academy/frontend


text:
Do not invoke a search unnecessarily

This should reduce the number of search queries for repositories with LSIF data.

@gbrik there is your STINKY test

repo: sourcegraph/code-intel-extensions


text:
chore(gha): comment on PR about reviews

Implements https://www.notion.so/sourcegraph/Set-up-a-restriction-on-PRs-to-require-approval-for-merging-89710798660744e8a84dab75a17deb85?pvs=4

@jhchabran what do you think of...

[!WARNING]
As we're migrating to Notion, we want to make sure that changes to the handbook are absolutely necessary. To ensure it is the case, it's now mandatory to get an approving review to merge a pull request.

Examples

Setting up a redirection to a Notion page: PR will be approved.
Correcting an important mistake on a page that doesn't have an equivalent yet: PR will be approved.
Updating content that isn't mission critical: PR will be rejected.

Sourcegraphers: Reach out to #wg-notion if you have any question.

authors: burmudar jhchabran

repo: sourcegraph/handbook


text:
bug: java.util.concurrent.TimeoutException

Plugin version: 5.3.27
IDE version: WS-233.14475.40
Stacktrace:
java.util.concurrent.TimeoutException
	at java.base/java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1960)
	at java.base/java.util.concurrent.CompletableFuture.get(CompletableFuture.java:2095)
	at com.sourcegraph.cody.agent.CodyAgentService.startAgent$lambda$3(CodyAgentService.kt:69)
	at com.intellij.openapi.application.impl.ApplicationImpl$2.run(ApplicationImpl.java:249)
	at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539)
	at com.intellij.util.concurrency.ContextCallable.call(ContextCallable.java:32)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at com.intellij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:702)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:699)
	at java.base/java.security.AccessController.doPrivileged(AccessController.java:399)
	at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:699)
	at java.base/java.lang.Thread.run(Thread.java:840)

Closing in favor https://github.com/sourcegraph/jetbrains/issues/723

authors: exigow realjohncreator

repo: sourcegraph/jetbrains