Generalize 3D to work with 2D and 3D

Charlie,
I modified the Fast demos so they both have the same file structure and both use the 3D code. This is one step towards getting rid of the 2D code.
For comparison, you can still look at the Slow demos which are in the old standard.
I found it confusing that the *.imgparams, *.reconparams, *.sinoparams files were so different for the 2D vs. the 3D case. They should have been named *.2Dimgparams and *.3Dimgparmas and so on in the first place. But we don't need to worry about that any more soon. But note, that even in the 2D case, we enumerate the slices now: It is not shepp.2Dsinodata any more but rather shepp_slice0001.2Dsinodata and similarly for the weight and recon.
Please accept the pull request to express your approval (although your hypothetical inaction wouldn't stop me from working).

Just did it. Thanks!

On Aug 7, 2019, at 8:11 PM, Thilo Balke<EMAIL_ADDRESS>wrote:
Charlie,
I modified the Fast demos so they both have the same file structure and both use the 3D code. This is one step towards getting rid of the 2D code.
For comparison, you can still look at the Slow demos which are in the old standard.
I found it confusing that the *.imgparams, *.reconparams, *.sinoparams files were so different for the 2D vs. the 3D case. They should have been named *.2Dimgparams and *.3Dimgparmas and so on in the first place. But we don't need to worry about that any more soon. But note, that even in the 2D case, we enumerate the slices now: It is not shepp.2Dsinodata any more but rather shepp_slice0001.2Dsinodata and similarly for the weight and recon.
Please accept the pull request to express your approval (although your hypothetical inaction wouldn't stop me from working).

Reply to this email directly, view it on GitHub https://github.com/cabouman/OpenMBIR/pull/4?email_source=notifications&email_token=AFY3FKBALPFVZ5VLZJFIEWTQDNQENA5CNFSM4IKFHFC2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HEAT6OQ, or mute the thread https://github.com/notifications/unsubscribe-auth/AFY3FKGNNFFPBG5J4LICPVDQDNQENANCNFSM4IKFHFCQ.


[Bug]: zmq.error.ZMQError: No such device (addr='tcp://localhost:8000')

Your current environment
The output of `python collect_env.py`

Collecting environment information...
PyTorch version: 2.4.0+cu121
Is debug build: False
CUDA used to build PyTorch: 12.1
ROCM used to build PyTorch: N/A
OS: Ubuntu 22.04.3 LTS (x86_64)
GCC version: (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0
Clang version: Could not collect
CMake version: version 3.27.6
Libc version: glibc-2.35
Python version: 3.10.12 (main, Jun 11 2023, 05:26:28) [GCC 11.4.0] (64-bit runtime)
Python platform: Linux-5.15.0-78-generic-x86_64-with-glibc2.35
Is CUDA available: True
CUDA runtime version: 12.2.140
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration:
GPU 0: NVIDIA GeForce RTX 4090
GPU 1: NVIDIA GeForce RTX 4090
Nvidia driver version: 535.54.03
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.9.5
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.9.5
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.9.5
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.9.5
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.9.5
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.9.5
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.9.5
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True
CPU:
Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Address sizes:                   46 bits physical, 57 bits virtual
Byte Order:                      Little Endian
CPU(s):                          128
On-line CPU(s) list:             0-127
Vendor ID:                       GenuineIntel
Model name:                      Intel(R) Xeon(R) Gold 6430
CPU family:                      6
Model:                           143
Thread(s) per core:              2
Core(s) per socket:              32
Socket(s):                       2
Stepping:                        8
Frequency boost:                 enabled
CPU max MHz:                     2101.0000
CPU min MHz:                     800.0000
BogoMIPS:                        4200.00
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonstop_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16 xtpr pdcm pcid dca sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3dnowprefetch cpuid_fault epb cat_l3 cat_l2 cdp_l3 invpcid_single cdp_l2 ssbd mba ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi flexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid cqm rdt_a avx512f avx512dq rdseed adx smap avx512ifma clflushopt clwb intel_pt avx512cd sha_ni avx512bw avx512vl xsaveopt xsavec xgetbv1 xsaves cqm_llc cqm_occup_llc cqm_mbm_total cqm_mbm_local split_lock_detect avx_vnni avx512_bf16 wbnoinvd dtherm ida arat pln pts avx512vbmi umip pku ospke waitpkg avx512_vbmi2 gfni vaes vpclmulqdq avx512_vnni avx512_bitalg tme avx512_vpopcntdq la57 rdpid bus_lock_detect cldemote movdiri movdir64b enqcmd fsrm md_clear serialize tsxldtrk pconfig arch_lbr amx_bf16 avx512_fp16 amx_tile amx_int8 flush_l1d arch_capabilities
Virtualization:                  VT-x
L1d cache:                       3 MiB (64 instances)
L1i cache:                       2 MiB (64 instances)
L2 cache:                        128 MiB (64 instances)
L3 cache:                        120 MiB (2 instances)
NUMA node(s):                    2
NUMA node0 CPU(s):               0-31,64-95
NUMA node1 CPU(s):               32-63,96-127
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Mmio stale data:   Not affected
Vulnerability Retbleed:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling, PBRSB-eIBRS SW sequence
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Versions of relevant libraries:
[pip3] flashinfer==0.1.2+cu121torch2.3
[pip3] numpy==1.22.2
[pip3] nvidia-nccl-cu12==2.20.5
[pip3] onnx==1.14.0
[pip3] pytorch-quantization==2.1.2
[pip3] torch==2.4.0
[pip3] torch-tensorrt==0.0.0
[pip3] torchdata==0.7.0a0
[pip3] torchtext==0.16.0a0
[pip3] torchvision==0.19.0
[pip3] transformers==4.43.3
[pip3] triton==3.0.0
[conda] Could not collect
ROCM Version: Could not collect
Neuron SDK Version: N/A
vLLM Version: 0.5.3.post1
vLLM Build Flags:
CUDA Archs: 5.2 6.0 6.1 7.0 7.2 7.5 8.0 8.6 8.7 9.0+PTX; ROCm: Disabled; Neuron: Disabled
GPU Topology:
GPU0    GPU1    CPU Affinity    NUMA Affinity   GPU NUMA ID
GPU0     X      NODE    0-31,64-95      0               N/A
GPU1    NODE     X      0-31,64-95      0               N/A
Legend:
X    = Self
SYS  = Connection traversing PCIe as well as the SMP interconnect between NUMA nodes (e.g., QPI/UPI)
NODE = Connection traversing PCIe as well as the interconnect between PCIe Host Bridges within a NUMA node
PHB  = Connection traversing PCIe as well as a PCIe Host Bridge (typically the CPU)
PXB  = Connection traversing multiple PCIe bridges (without traversing the PCIe Host Bridge)
PIX  = Connection traversing at most a single PCIe bridge
NV#  = Connection traversing a bonded set of # NVLinks
🐛 Describe the bug
VLLM_ATTENTION_BACKEND=FLASHINFER vllm serve /checkpoints/huggingface/rtzr/ko-gemma-2-9b-it --max_model_len 3072 --quantization fp8 --enforce_eager
When running above command I get below error message. (I have installed vllm with source code of vllm (latest) & using nvidia pytorch 23-10 container)
---------------error message-----------------
INFO 08-04 03:53:43 model_runner.py:732] Loading model weights took 9.6262 GB
INFO 08-04 03:53:44 gpu_executor.py:102] # GPU blocks: 1692, # CPU blocks: 780
Process Process-1:
Traceback (most recent call last):
File "/usr/lib/python3.10/multiprocessing/process.py", line 314, in _bootstrap
self.run()
File "/usr/lib/python3.10/multiprocessing/process.py", line 108, in run
self._target(*self._args, **self._kwargs)
File "/code/jeeseung/sdk_test/dalpha-llama3-ds/vllm/vllm/entrypoints/openai/rpc/server.py", line 215, in run_rpc_server
server = AsyncEngineRPCServer(async_engine_args, usage_context, port)
File "/code/jeeseung/sdk_test/dalpha-llama3-ds/vllm/vllm/entrypoints/openai/rpc/server.py", line 33, in init
self.socket.bind(f"tcp://localhost:8000")
File "/usr/local/lib/python3.10/dist-packages/zmq/sugar/socket.py", line 302, in bind
super().bind(addr)
File "zmq/backend/cython/socket.pyx", line 564, in zmq.backend.cython.socket.Socket.bind
File "zmq/backend/cython/checkrc.pxd", line 28, in zmq.backend.cython.checkrc._check_rc
zmq.error.ZMQError: No such device (addr='tcp://localhost:8000')

can you report your zmq version?

Will look into this. For now, you can enable —disable-frontend-multiprocessing as a workaround

building a recent commit I'm getting the same error but with different port:
zmq.error.ZMQError: No such device (addr='tcp://localhost:5570')

How zmq should be installed?
Doesn't seem like the Dockerfile was updated with such a change.
I tried apt install-ing libzmq3-dev and libzmq5 but it's probably not it ...
thanks

building a recent commit I'm getting the same error but with different port:
zmq.error.ZMQError: No such device (addr='tcp://localhost:5570')

How zmq should be installed? Doesn't seem like the Dockerfile was updated with such a change. I tried apt install-ing libzmq3-dev and libzmq5 but it's probably not it ...
thanks

just replace localhost by <IP_ADDRESS>~

@hibukipanim you don't need additional install, it is already in vllm:
https://github.com/vllm-project/vllm/blob/b1c9aa3daa7dcd981f0f77231b46883624b72dd0/requirements-common.txt#L24

close by https://github.com/vllm-project/vllm/pull/7163


AGLint does not know about "Protected Audience API" permissions

https://github.com/AdguardTeam/AdguardFilters/commit/01eba10fd508fa170dd02c93b1db7fa88c621004
This rule is getting flagged:
$permissions=join-ad-interest-group=()\, run-ad-auction=()\, browsing-topics=()

If the issue is resolved, the ! aglint-disable-next-line should be removed.
https://github.com/AdguardTeam/AdguardFilters/commit/09d20a35e422d05bbf5ceb49e41d96105afab29c

@am I did not plan any new AGTree release until the completion of the tsurlfilter + AGTree integration. If it is okay for you, I will fix this it after that

Came with private-state-token-issuance and private-state-token-redemption

/.*/$permissions=private-state-token-issuance=(),document
/.*/$permissions=private-state-token-redemption=(),document


feat: production build fo code manager - support for production stage docker configs

support for docker/production/django in prod environment is add

production stage docker configs like:
i. Dockerfile
ii. entrypoint
iii. start script

for docker container.

Non-root user codemanager is created for production stage


Vinodhmohan91 dev 3

Added and edited content to show the steps to save the spam filter model in both Watson Studio Local and Remote HDP cluster. Also, has steps to do a batch scoring and model evaluation.

Made the changes requested. Please review and merge.


What is meant by "Buildtime packages release is decoupled from the SPFx release"?

What type of issue is this?
Question
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Target SharePoint environment
SharePoint Online
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[ ] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version
SPFx version
Node.js version
etc

Issue description
With regards to the 1.19 beta release, could someone elaborate on the gibberish that is in the release notes?
What are buildtime packages as opposed to SPFx release and does this have any impact to us pleb developers? Can we use whatever version of TypeScript, React or Solidjs without hacks?

I don't think it's about any version of TS, React, etc.
If you check out the minimal 1.19-beta.0 package.json file, you will notice, that now not all @microsoft/* related packages have 1.19.0-beta.0 version (see image)

Looks like these "1.20.1" packages are "build time packages" and now their versions are decoupled from SPFx release versions.

But all of this stuff is proprietary and closed source. It is internal implementation of a black box that we can't control or do anything about. Bad product, bad DX, bad documentation, slow and poor support (e.g., extensions are still randomly failing to load half-a-decade later).
Obviously, no dig at you @s-KaiNet. Your external library trick for on-prem solutions really helped me in a project I did a few years back. Wish we could do the same for SPO solutions as well or if @VesaJuvonen  did something about the dire state this product is in, instead of just adding features no one cares about (adaptive cards, etc... )

@smolattack - Flattered on the comment around the role I have, but there's a much bigger crew driving the features and priorities of the SPFx - my input matters, but so does your input, so thanks for your comments and feedback.
We have noted this feedback and have routed this back to the team for further discussion. Valuable comment and feedback on the requirements around more transparency and visibility on these kind of changes which can cause confusion.
@s-KaiNet is correct around the direction with this. So the team responsible of the build time packages wants to break the release dependency with the other SPFx packages. This will mean more flexibility on the release cycles, but can cause also confusion as then we have multiple teams doing versioning in different sequence, so documentation and input is for sure needed.
There's still ongoing discussion on getting the SPFx Yeoman generator and packages open-sourced internally at Microsoft and there's lot of people who would like to do this. It hast though also significant impact on the normal build and publishing processes with resourcing impact, which is why leadership is a bit unhesitant to do this. Hopefully we can change this at some point, so that we can get more visibility on the packages and processes.
Hopefully that provides a bit more visibility on what's going on with some background information. Feedback is always welcome and incredibly important to get shared, so that we can route that to the people who make decisions behind the scenes. Thx 🙏

During the last few years, as the principal architect of large scale monorepository, I often get frustrated by the SPFX toolbox. The main issue is the lack of extensibility. The custom gulpfile is a joke, and the actual config objects are deeply hidden under the layers of tool (rush, heft, gulp, …) which make practically impossible to tweak without some hijacking. Not using the latest React 18 (which is 2 years old now) prevent us to use some very nice 3rd part lib (react query!), unit testing is incredibly complex, …
But to be honest, I can’t really blame Microsoft. I guess design choices are made to target large scale teams where consistency and reliability is more important than “Hype drive development”. The nodejs world is a big mess. There are plenty of different ways to achieve some tasks, from easier to very complex ones. The MS approach tends to rationalize how everything works, and the resulting support is easier.
There is probably a middle ground to find. Improving extensibility without sacrificing reliability and consistency. Decoupling build from SPFX version is a small but great step into this direction.

@stevebeauge I'm not sure what  “Hype drive development” means or why consistency and reliability are blocks to having an up-to-date tool-chain.
The following quotes are from Microsoft's own literature

With the SharePoint Framework, you can use modern web technologies and tools in your preferred development environment

It's framework-agnostic. You can use any JavaScript framework that you like including, but not limited to, React, Handlebars, Knockout, Angular, and Vue.js.

How can you be framework-agnostic and modern if you're forced to use an ancient version of TypeScript? Where are the getting started guides for using alternative frameworks other than the bundled React version in use by SharePoint?
All they have to do is create a custom/advanced option in yeoman that just expects a path to a bundle css/js files. That bundle could just be an external bundle (so that the SPFx webpack configs can be completely separate from the "custom app's" webpack configs, or the custom app might not even use webpack at all). Also, publish an npm package that gives you a modern SPFx context object
import * as React from "react";
import { getContext, WebPartContext } from "@microsoft/sp-webpart-base";
//-------^^^^^^^^^^- This can just be the onInit method in the BaseClientSideWebPart
// that returns a context instead of just initializing `this.context`
// (and whatever else it might do)

// This becomes your entrypoint that you code and build in whatever
// way you want, as long as it gets bundled into a js and css file SPA App
export function App(): JSX.Element {
  const [state, setState] = React.useState<SPFX_CONTEXT_INIT_STATE>({
    _type: "IDLE",
  });
  React.useEffect(() => {
    setState({ _type: "LOADING" });
    // This is how we get our `this.context` assuming the code runs
    // inside a modern page, bootstrapped by SPFx
    getContext()
      .then((spfxContext) => {
        setState({ _type: "SUCCESS", spfxContext });
      })
      .catch((error) => {
        setState({ _type: "ERROR", error });
        console.log("SPFx context error", error);
      });
  });

  switch (state._type) {
    case "IDLE":
      return
First render. Should automatically go to loading
;
    case "LOADING":
      return
Loading...
;
    case "SUCCESS":
      // This is how you'd bootstrap your own app
      return <PageRouter spfxContext={state.spfxContext} />;
    case "ERROR":
      return (

{`Check console for "SPFx context error". Is this app running inside a modern SharePoint page?`}

      );
    default:
      absurd(state);
      return
satisfying return type signature

  }
}

// Nevermind this stuff
declare function PageRouter(props: {
  spfxContext: WebPartContext;
}): JSX.Element;
declare function getContext(): Promise<WebPartContext>;

type IDLE = { _type: "IDLE" };
type LOADING = { _type: "LOADING" };
type SUCCESS = { _type: "SUCCESS"; spfxContext: WebPartContext };
type ERROR = { _type: "ERROR"; error: unknown };

type SPFX_CONTEXT_INIT_STATE = IDLE | LOADING | SUCCESS | ERROR;

function absurd(_: never): A {
  throw new Error("absurd");
}

Extensions and properties can work in a similar way where you just import a subscriber function that lets you listen to events (like command button presses or page navigation events, etc...).
The disadvantages would be that the final solution would be bigger and the build process would be more complicated but those are tradeoffs that you must allow the developer to decide on (and by extension, whoever the developer's client is)


[Coverity CID :187077] Memory - corruptions in /samples/net/rpl_border_router/src/http.c

Static code scan issues seen in File: /samples/net/rpl_border_router/src/http.c
Category: Memory - corruptions
Function: start_http_server
Component: Samples
CID: 187077
Please fix or provide comments to square it off in coverity in the link: https://scan9.coverity.com/reports.htm#v32951/p12996

false-positive


Upgrade to Django1.9

@maurodoglio r?

I was thinking maybe this is a good time to upgrade the references to the django docs to point to the 1.9 version? At the moment they point to 1.7.

maurodoglio commented 23 hours ago
I was thinking maybe this is a good time to upgrade the references to the django docs to point to the 1.9 version? At the moment they point to 1.7.

good point, updated.

Thanks for updating the docs :+1:
:ship: it!

thnx!


InitialStateConfiguration.lastKnownStateFromJournal, and Error continuing

String exchangeId = "MY_EXCHANGE" ;
long snapshotBaseSeq = 0 ;
ExchangeConfiguration conf = ExchangeConfiguration.defaultBuilder()
.serializationCfg(SerializationConfiguration.DISK_JOURNALING)
.initStateCfg(InitialStateConfiguration.lastKnownStateFromJournal(exchangeId, 1, snapshotBaseSeq))
.build() ;
And then start the program. And when I add users and orders, It go to error below:
java.lang.IllegalStateException: File already exists: .\dumps\MY_EXCHANGE_journal_1_0001.ecj
at exchange.core2.core.processors.journaling.DiskSerializationProcessor.startNewFile(DiskSerializationProcessor.java:694) ~[classes/:na]
at exchange.core2.core.processors.journaling.DiskSerializationProcessor.writeToJournal(DiskSerializationProcessor.java:270) ~[classes/:na]
at com.lmax.disruptor.BatchEventProcessor.processEvents(BatchEventProcessor.java:168) [disruptor-3.4.2.jar:na]
at com.lmax.disruptor.BatchEventProcessor.run(BatchEventProcessor.java:125) [disruptor-3.4.2.jar:na]
at java.lang.Thread.run(Thread.java:748) ~[na:1.8.0_231]

Hi,
This scenario was not covered indeed.
This needs to be fixed, thanks for reporting.

Hi, I guess this bug still persists.

The goal is to skip loading snapshot datas if this one doesn't exists and keep the exchange-core launching without taking it in count.


Ask RedHat if they want to join

It might sound strange at the beginning but thinking more about this, it might be a clever resolution of the current situation benefiting everyone:

RedHat can share the maintenance cost with others
Free downstream distros are possible again
Would be similar to Debian but in the rpm space, RHEL would become like Ubuntu in this analogy
Mostly compatible with RHEL by definition

Everyone is welcome to join OpenELA :)
I am going to close this issue as it is out of scope for the website repository, but please do not take this as "they're not welcome."


Deleting an image from a repo with a large number of tags can be very slow

Issue with current implementation.
Currently as part of the image delete flow, we find all the tags in the given repository and then do a Lookup to work out if the tag currently points to the digest we are trying to delete. If a repository has many tags this can cause delete calls to be very slow. Had a recent real-world example where it takes >30s to delete an image with ~5000 tags.
I haven't see this in the wild but I also believe this introduces a large window where a race can occur. The race would be:

Tag test1 points at the digest we wish to delete.
test1 added to the delete slice.
Whilst we are still working on looking up all the other tags, a push is done over the test1 tag that changes the digests.
test1 is deleted.

The loop that then untags each tag that references the Digest we wish to delete is also done sequentially.
https://github.com/distribution/distribution/blob/6248a88d03badbe49c4969f802f5860b6fb2a685/registry/handlers/manifests.go#L542
Proposed solutions
There are a couple of ways we can fix this:

The simple solution is to just add concurrency - so we can make it so the code can do x number of tag lookups and Untags in parallel. The extra speed will close the window in which the race can occur.

The more complex solution would be to do solution 1 but in addition instead of appending the tags marked for Untag to a slice we add them to a channel. This channel can be consumed by a go routine that would then immediately call Untag and thus making the window for the race very small.

Open to suggestions on whether people think 1 is good enough or if we/I should look at solution 2? Always wary of adding complexity to code for a theoretical problem that we are unlikely to see in reality.

Both suggestions sound good to me. We already do goroutine dance similar to 2. in some storage drivers (like here), so I wouldnt see it as introducing huge amount of complexity. I'd go for 2.

I prefer the option 1, parallel deletion is enough for this case, we can just have another goroutine to collect the errors from error chan, and the error is raised by Untag in parallel deletion.


Reduce cascade of run-time warnings.

The uint8_t here needs to be cast to an integer to be printed
correctly. Also these warnings seem to be quite common so we should
hide them in Release builds.
These warnings probably indicate an actual problem that I do not fully
understand yet.

@prideout, I think this is due to the morphing change -- it made it "not an error" to have BindingPoints that are not set. I think it's because morphing and skinning are using the same variant, but skinning doesn't use a texture in the vtx shader, so it's binding point is empty (and there is a binding point because it's used for morphing... which is the same variant).

@daemyung, am I correct here?
Yes it its.


How to liberate the javalib from the dependency on js.JavaScriptException?

In the context of #4677, we need to "liberate" the javalib from its dependency on js.JavaScriptException. The problem comes from the semantics of a Scala-level try..catch and throw:
Reminder: language-level semantics
In the following Scala.js code:
try {
  body()
} catch {
  case t: Throwable => handle(t)
}

the try..catch is specified to catch any value thrown during body(). Because JavaScript is what it is, that can truly be any value, including primitives, any JS object, and even any Scala object that's not a Throwable (which in that case behaves as a JS object).
When catching something that is a Throwable, t is assigned to that thing. When catching some other value e, it is wrapped in a scala.scalajs.js.JavaScriptException(e).
Conversely, in the following code:
throw t

the semantics are specified as: if t is a js.JavaScriptException(e), actually throw e; otherwise throw t.
js.JavaScriptException is defined in
https://github.com/scala-js/scala-js/blob/v1.10.0/library/src/main/scala/scala/scalajs/js/JavaScriptException.scala
Consequence for library-level semantics
To be consistent, library methods that are specified as throwing a given value, or catching anything in a certain code (such as in a function value argument), must follow the same wrapping and unwrapping behavior.
This can be seen explicitly, for example, in the js.Promise <-> Future adapter:
https://github.com/scala-js/scala-js/blob/6619c4b84c25ab36efdc038be67dddbc56581101/library/src/main/scala/scala/scalajs/js/Thenable.scala#L54-L69
It is also present implicitly (through the use of the throw keyword) in java.util.Optional at
https://github.com/scala-js/scala-js/blob/bbf031451b99380b878af0d729ce12a38d984b3a/javalib/src/main/scala/java/util/Optional.scala#L71-L73
Problem
The problem with that is that the javalib has an implicit dependency on js.JavaScriptException. One that is almost specced: if java.util.Optional.orElseThrow receives a js.JavaScriptException from its exceptionSupplier, it must throw the wrapped value instead.
Currently, this involves an instance test against js.JavaScriptException followed by accessing its underlying exception field. So there is a dependency in the IR code.
Conversely, if the JDK added a method such as
def catchAll(runnable: Runnable): Optional[Throwable]`

who was supposed to call runnable.run() but catch and return any exception thrown, it would have to wrap non-Throwables into a js.JavaScriptException.
These dependencies put the independent javalib "project" in jeopardy. By definition, any dependency from the javalib on Scala-defined stuff is forbidden, and js.JavaScriptException is not exempted. We could have exempted it (with caveats) if JavaScriptException were a bare Java-like class. Unfortunately, it is a case class, and that means it depends on scala.Product and other Scala types.
What to do about it?
I propose we discuss what we can do about it in this issue. There are two situations we can examine:

How we could redesign in the best possible way for Scala.js 2.x, free of backward compatibility constraints?
How we can mitigate the issues in Scala.js 1.x, given the compatibility constraints?

Although there are no plans for anything like a Scala.js 2.x in the foreseeable future, it is still probably good to think about what the ideal design would be, to guide what kind of mitigation would be acceptable.

The least bad solution I have so far, and which I implemented in #4677, solves the unwrapping problem for Scala.js 1.x, but not the wrapping problem (and it cannot be generalized as is for the wrapping problem).
The idea is to add an internal, protected method to Throwable, as follows:
class Throwable {
  ...

  /* Not part of the JDK API, overridden internally in js.JavaScriptException
   * and used by the javalib IR cleaner to replace calls to
   * `scala.scalajs.runtime.unwrapJavaScriptException()`.
   */
  protected def unwrapJavaScriptExceptionInternal(): Any =
    this
}

and to override it in js.JavaScriptException as follows:
final case class JavaScriptException(exception: Any) {
  ...

  /* Hack: override Throwable.unwrapJavaScriptExceptionInternal, which is a
   * "public" method but not part of the JDK API. This is used by the javalib
   * IR clear to replace calls to
   * `scala.scalajs.runtime.unwrapJavaScriptException()`.
   */
  /* override */ protected def unwrapJavaScriptExceptionInternal(): scala.Any =
    exception
}

This way, the throw t instruction doesn't have to do a type-test on js.JavaScriptException. It can directly call t.unwrapJavaScriptExceptionInternal() in a Scala-agnostic way to receive the value that must actually be thrown.
This solution is enough for today's javalib. Indeed, there is only a single place (namely Optional.orElseThrow) that must perform a wrap or unwrap operation by spec, and it is only an unwrapping. Other occurrences of wrap/unwrap in the javalib can be internally eliminated, without altering the spec from the outside.
But I have no solution for the wrapping problem. If the JDK adds one day a method that must wrap by spec, I have no solution on how to implement it without depending on js.JavaScriptException so far.

Just writing down thoughts I had about this:

IMHO it is clear that machinery to deal with the differences of JS / JVM throwing semantics should be provided by the IR.
Could we make js.JavaScriptException something like a hijacked class?

Making js.JavaScriptException a hijacked class is not really solving anything, at least not in 1.x. Because it still needs to retain its class/interface hierarchy, and that depends on Scala classes such as Product.
Nevertheless, if JavaScriptException becomes a hijacked class, the question is: what is its representation?
There's an argument to be made that it should be the thrown value itself. That means that any value x that is not a Throwable would be a JavaScriptException. And then that means they would actually answer true to x.isInstanceOf[Throwable] (like any value answers true to .isInstanceOf[java.lang.Object]). The difficulty is then that it must include any Scala class. So x: List would have to be a JavaScriptException, and hence a Throwable as well. That probably opens up all kinds of cans of worms, and I'm not even considering the superclasses of JavaScriptException like Product, so the difficulty would stay in a hypothetical 2.x.
So if it's not the value itself, it must be an instance of a small wrapper class defined by the core JS lib (like $Char for boxed Char instances). We could then have Scala-agnostic IR instructions to wrap/unwrap any value in that container. Something like:
class $WrapperThrowable {
  constructor(e) {
    this.e = e;
  }
}
// Any => Throwable
function $wrapAsThrowable(e) {
  return e instanceof $WrapperThrowable ? e : new $WrapperThrowable(e);
}
// Throwable => Any
function $unwrapFromThrowable(th) {
  return th instanceof $WrapperThrowable ? th.e : th;
};

There would be two IR nodes for this wrap/unwrap function pair. The compiler would use them to compile a Scala try..catch. We could expose them as primitive methods in js.special (and perhaps even a JS-level try..catch primitive that catches an Any instead of a Throwable).
This would allow the javalib to directly use those IR nodes to wrap/unwrap when necessary.
Now it would still be awkward to (re-)define JavaScriptException as a hijacked class for this wrapper:

First, it does live in the scala namespace, so now the very definition of the IR would depend on the scala package, which is not the case currently.
It will cause all of Product, Equals, RuntimeException, Exception and Throwable to become ancestors of a hijacked class, which complicates their method dispatch and instance test. (There's also Serializable but that one is already a hijacked class ancestor).
Since Throwable has fields, we now have a case of a hijacked class with a field, which will complicate the hijacking mechanism.

A mitigating factor the second bullet is that we have good infrastructure for method dispatch of hijacked classes now. It used to be the case that we needed manual configuration of each method, but now it's pretty automated. We also already have a precedent for a class that is an ancestor, with java.lang.Number, so that shouldn't be such an issue.
So that is what we would have to do for Scala.js 1.x. Not pretty, but doable.
In a hypothetical 2.x, we could get rid of all this complexity by redefining JavaScriptException as a mere constructor/extractor:
object JavaScriptException {
  def apply(e: Any): Throwable =
    js.special.wrapAsThrowable(e)

  def unapply(th: Throwable): Any = {
    val e = js.special.unwrapFromThrowable(th)
    if (e eq th) None else Some(e)
  }
}

Rereading myself: assuming the above is the model we want for 2.x, there's actually a simpler filler solution for 1.x. It would be to use js.JavaScriptException as the class manipulated by the wrap/unwrap IR nodes, instead of $WrapperThrowable.
Pro: no need to patch JavaScriptException as a hijacked class.
Con : it makes it impossible to design the linker in a way that does not require JavaScriptException to be on the classpath. That's not good for the minilib, and it's not good for other languages that could like to target the IR without depending on the scalalib.

We could combine the advantages of both approaches with two different strategies in the emitter:

If scala.scalajs.js.JavaScriptException is on the classpath, then wrap/unwrap to and from that class.
Otherwise, use $WrapperThrowable.

It may be ugly, but I suspect it will be less ugly than making JavaScriptException a hijacked class.

Other possibility for 1.x, similar to the above but with less hackery in the emitter: the emitter could inject an IR file with a bare-bone scala.scalajs.js.JavaScriptException that does not depend on the scalalib, defined in the linkerPrivateLib:
class JavaScriptException(val exception: Any) extends RuntimeException {
  override def getMessage(): String = exception.toString()

  override def fillInStackTrace(): Throwable = {
    type JSExceptionEx = JavaScriptException {
      def setStackTraceStateInternal(e: scala.Any): Unit
    }
    this.asInstanceOf[JSExceptionEx].setStackTraceStateInternal(exception)
    this
  }
}

(the only real difference with the real one is that it's not a case class.)
If there's JavaScriptException on the classpath, it will take priority. Otherwise, the minimal one above will be used.

I think that is actually quite a decent solution. In a hypothetical 2.0, we could then just change the package of this class.
I wonder if we can avoid the reflective call though :-/

I wonder if we can avoid the reflective call though :-/

The reflective call is already present in today's js.JavaScriptException. It's probably not possible to get rid of it, other than by writing the IR of this method by hand. This class is compiled separately form the javalanglib, so the compiler doesn't know that setStackTraceStateInternal exists.


internal/fuzz: test_fuzz_minimize failures missing "got the minimum size" beginning 2021-11-17

    --- FAIL: TestScript/test_fuzz_minimize (46.15s)
        script_test.go:257:
            # We clean the fuzz cache during this test. Don't clean the user's cache. (0.000s)
            # Test that fuzzminimizetime cannot be negative seconds (18.682s)
            # Test that fuzzminimizetime cannot be negative times (2.829s)
            # Test that fuzzminimizetime can be zero seconds, and minimization is disabled (4.268s)
            # Test that fuzzminimizetime can be zero times, and minimization is disabled (7.046s)
            # Test that minimization is working for recoverable errors. (1.949s)
            # The error message that was printed should be for the one written to testdata. (0.000s)
            # Check that the bytes written to testdata are of length 50 (the minimum size) (1.023s)
            # Test that re-running the minimized value causes a crash. (4.685s)
            # Test that minimization is working for recoverable errors. Run it with -v this
            # time to ensure the command line output still looks right. (1.639s)
            > ! go test -v -fuzz=FuzzMinimizerRecoverable -run=FuzzMinimizerRecoverable -fuzztime=10000x .
            [stdout]
            === FUZZ  FuzzMinimizerRecoverable
            fuzz: elapsed: 0s, gathering baseline coverage: 0/1 completed
            fuzz: elapsed: 0s, gathering baseline coverage: 1/1 completed, now fuzzing with 16 workers
            fuzz: minimizing 427-byte failing input file
            fuzz: elapsed: 0s, minimizing
            --- FAIL: FuzzMinimizerRecoverable (0.24s)
                --- FAIL: FuzzMinimizerRecoverable (0.00s)
                    y_test.go:38: contains a non-zero byte of length 97

                Failing input written to testdata\fuzz\FuzzMinimizerRecoverable\064b38366638e28ac6d4036031db2afcda0528bfb8393486ed0358da0f930fe6
                To re-run:
                go test -run=FuzzMinimizerRecoverable/064b38366638e28ac6d4036031db2afcda0528bfb8393486ed0358da0f930fe6
            FAIL
            exit status 1
            FAIL	example.com/y	0.304s
            [exit status 1]
            > ! stdout '^ok'
            > stdout 'got the minimum size!'
            FAIL: testdata\script\test_fuzz_minimize.txt:54: no match for `(?m)got the minimum size!` found in stdout

greplogs --dashboard -md -l -e '(?ms)FAIL: TestScript/test_fuzz_minimize.*no match for ...m.got the minimum size' --since=2021-06-01
2021-11-19T00:05:59-e8cda0a/linux-386-longtest
2021-11-18T22:40:42-2375b6e/linux-386-longtest
2021-11-18T20:11:45-24898d6/windows-amd64-longtest
2021-11-18T14:00:00-14c3f74/windows-amd64-longtest
2021-11-18T02:15:36-2463b4f/windows-amd64-longtest
2021-11-18T02:10:22-e3b48af/linux-386-longtest
2021-11-17T21:26:25-0440fb8/linux-386-longtest
2021-11-17T21:26:25-0440fb8/windows-amd64-longtest
(CC @rolandshoemaker @katiehockman)

After submitting CL365175 and CL365294 (the two fuzzing changes from yesterday) I am no longer able to reproduce this (at least on the linux-386-longtest builder).

I merged CL 365315 (skipping the test) right around then. Are you testing with that rolled back?

We could always try just rolling back the skip and seeing if the builders remain clear. The failure rate was high enough previously that it should show up within a half-dozen CLs or so if it's still broken.

Rolled back the skip. Watching the builders to see whether this appears to be fixed.

A fair number of longtest runs so far and no flakes from this test. Barring further evidence to the contrary, I'm calling this fixed.


Don't collect top / logs / config if not a cluster host

Often we have diagnostics from customers where the diagnostics has been run on a machine which has a development Elasticsearch installation, but is not a node in the cluster.  In this case it is very confusing and misleading to have the top / config / logs in the diagnostics, because they usually have nothing to do with the cluster.
Would it be possible to identify if the diagnostics is being executed on a cluster node machine, and only collect these machine sections if it is a cluster node machine?
It would also be good to have some warning output noting that the config / logs have not been collected if the diagnostics was run from an external machine, or they could not be found / read.

The REST based statistics are retrieved prior to any log processing.  And you need the output from the _nodes command to find the location of the logs and config, as well as seeing whether or not at least one of the nodes IP or hostname matches that of the host where the script is being executed.
Would it be acceptable to do a check after the information is collected and write an entry to the manifest indicating if the host the script is being run from doesn't match a host in the collected list?  Could also disregard checking for logs and configs if this was the case as well.

I would prefer each diagnostic being as clear as possible (i.e. diagnostics from one node only), so noting incompleteness in the metadata would be a patch IMO, but collecting only relevant data would be the solution.

Now has a remote option to run specifically as a just a call to the REST interface.

This --type remote option is something which needs to be actively done by the user, and the default value is standard which collects top information: I have not seen any example yet of someone using the remote option, but many examples of diagnostics created from a remote machine thereby capturing invalid top / logs / configuration / uname.
Would in not be possible to have it automatic unless overridden with an explicit --type call?


Update with nested query error

Tell me how can I write a query to update a field with a nested query using quill?
Version: 3.19.0
Module: quill-jdbc-zio
Database: postgresql
Expected behavio
The query that should be the result: UPDATE table1 SET field = 'foo' WHERE id IN (SELECT id FROM table2 WHERE field IN (value1, value2))
Actual behavior
The compiler tells me that I will get the right request, but I keep getting an error.
Tell me how can I write a query to update a field with a nested query using quill?
Steps to reproduce the behavior
In quill it loks like:
val table1 = quote(querySchema[Table1]("table1"))
val table2 = quote(querySchema[Table2]("table2"))

val params = List("param1", "param2")

quote{
  table1
    .filter(t => table2.filter(t2 => liftQuery(params).contains(t2.field))
      .map(_.id)
      .contains(t.id)
    )
    .update(_.field -> lift("foo"))
}

Workaround
Not found
@getquill/maintainers

Found a solution for such a request.
quote{
  table1
    .filter(t => table2.filter(t2 => infix"${t2.field} IN (${lift(params.mkString(","))})".as[Boolean])
      .map(_.id)
      .contains(t.id)
    )
    .update(_.field -> lift("foo"))
}


Find HTML Element which represents a data-source

I have a nested model which mapped to html. I want to get a html HTML Element which represents data.
this.binding = rivets.bind(this.el, {
    tariff: this.model
});

var someMappedModel = this.model.get('submodel').get('subcollection').at(0);

// I want to
var htmlElement = this.binding.findElementByData(someMappedModel);

Closing this as it is very old and doesn't seem to be an issue with rivets itself


fix mismatching expectation of the keep alive timer

Fixes #2288.
session.maybeResetTimer() and session.run() were using slightly different definitions of when a keep-alive PING should be sent. Under certain conditions, this would make us repeatedly set a timer for the keep-alive, but on timer expiration no keep-alive would be sent.

Codecov Report

Merging #2289 into master will decrease coverage by 0.06%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #2289      +/-   ##
==========================================
- Coverage   85.99%   85.93%   -0.06%
==========================================
  Files         108      108
  Lines        8080     8089       +9
==========================================
+ Hits         6948     6951       +3
- Misses        853      857       +4
- Partials      279      281       +2

Impacted Files
Coverage Δ

session.go
73.58% <100%> (-0.43%)
:arrow_down:

Continue to review full report at Codecov.

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


Incorrect Drop after multiple attach_xdp calls

This line https://github.com/redsift/redbpf/blob/8c1d771bcd29b6e0415544ac4aaa0a3d5006519f/redbpf/src/lib.rs#L453 causes Drop to detach the XDP program from only the last interface.
I'm thinking to change the interface tracking to a Vec, but I'm not entirely sure the correct semantic for attach_xdp. The other option would be to detach from the previous interface so it only attaches once, though that doesn't match my use case. I'd be happy to attempt a PR if you have a preference.
This is discovered when I try to attach a program to all interfaces like this:
let interfaces = std::fs::read_dir("/sys/class/net").expect("failed to list interfaces");
for interface in interfaces {
  if let Ok(iface) = interface {
    if let Ok(ifa) = iface.file_name().into_string() {
      prog.attach_xdp(&ifa, xdp::Flags::default()).expect("failed to attach XDP program");
    }
  }
}

It should be possible to attach to multiple interfaces, and keeping a Vec of interfaces seems the simplest thing to do that wouldn't break the API.
Longer term, we need to come up with a better story for detaching which is now pretty much just a stub (eg Drop as it is now will detach whatever program is attached to the interface, even if in the meantime another program replaced the one that was originally attached).


Move from docker action @v1 to docker action @v2

Signed-off-by: parauliya<EMAIL_ADDRESS>

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3427566). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   23.79%
=========================================
  Files             ?       14
  Lines             ?     1244
  Branches          ?        0
=========================================
  Hits              ?      296
  Misses            ?      928
  Partials          ?       20

Continue to review full report at Codecov.

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


[TEMPLATE REQUEST] - Flutter and Android/iOS

What domain will the project template be based on?
Others (please specify in the details)
If 'Others', please specify the preferred domain.
Hybrid App
Particular directory path for the template.
template/mobile/flutter
What tech stacks do you want to include?
Flutter
Brief Description
This is a template for Android app in Flutter.
👀 Have you spent some time checking if this issue has been raised before?

[X] Yes
[ ] No

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Would you like to work on this issue?
Yes

Hey @jaiakash
Requested some changes https://github.com/Abhishek-Mallick/universal-box/pull/126#pullrequestreview-2363917187

Hey @jaiakash could you please answer to this https://github.com/Abhishek-Mallick/universal-box/pull/126#pullrequestreview-2365049883
I'll make the necessary changes to my next commit


comp/chat

PR

Types of changes

[x] New feature

Description

Checklist

[x] added: chat

DONE: https://github.com/andrejsharapov/nuxt-app/projects/1#card-59754063


URL in description and README broken

The URL in the repository description and README are pointing to GHTrainingASU's copy of the game instead of yours.
Please fix both, so they point to your copy of the game at https://GHTrainingASU.github.io/github-games-DarylTX.

Fixed.


Use the result of index when converting to Rust BigInts.

Thank you for contributing to pyo3!
Here are some things you should check for submitting your pull request:

Run cargo fmt (This is checked by travis ci)
Run cargo clippy and check there are no hard errors (There are a bunch of existing warnings; This is also checked by travis)
If applicable, add an entry in the changelog.
If applicable, add documentation to all new items and extend the guide.
If applicable, add tests for all new or fixed functions
If you changed any python code, run black .. You can install black with pip install black)

You might want to run tox (pip install tox) locally to check compatibility with all supported python versions. If you're using linux or mac you might find the Makefile helpful for testing.

Thanks, LGTM. I've added a CHANGELOG entry and will merge once CI succeeds.


Render error page and return back to previous page whenever error is encountered.

Find a way to render a default error page with a dynamic error message and whenever back is clicked, it should return to the last visited page rather than the home page

May I know if we already have a error page?
Or do I have to create it for myself?

You have to create one if you can we are cleaning up the existing react app to start all over you can initialize a create-react-app in the website folder and create a error page and the routes to render it. There is another issue in the repo to clean the react app if you want I can assign you that issue too..

If you want to work on it please comment below

Can I work on this?

Yeah you can I have deleted the existing react app because it had lot of bugs we are starting over it currently contains the default create-react-app template you can create an error page and put that there with the routes..

I'm assigning this issue to you

are you working under JWOC or just normally

Im currently working under jwoc


added NSProgress support

added implicit progress composition, also added test cases to verify that it's working.

Thanks @jay18001, I like this PR a lot. Merging.


javascript musical drum added

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a [javascript musical drum , on pressing different keys , webpage produces different sounds ]

please accept is as my contribution under hacktoberfest , if no conflicts found, please merge it with tag  hacktoberfest-accepted

Closes #XXXXX

Hey @Gaurav05082002
Thank you for opening this pull request.
This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it. This repo is not open to accept random projects.
We would welcome future pull requests from you.
Thank you and happy coding.


[Bug]: TypeError: The encoded data was not valid for encoding utf-8

Contact Details
No response
What happened?
didn't catch but backend stoped
What browsers are you seeing the problem on?
No response
Relevant log output
TypeError: The encoded data was not valid for encoding utf-8
    at TextDecoder.decode (node:internal/encoding:433:16)
    at getStringFromWasm0 (/home/ggptadmin/gpt/chatgpt-clone/node_modules/@dqbd/tiktoken/tiktoken_bg.cjs:111:30)
    at module.exports.__wbindgen_error_new (/home/ggptadmin/gpt/chatgpt-clone/node_modules/@dqbd/tiktoken/tiktoken_bg.cjs:410:27)
    at wasm://wasm/00b5f812:wasm-function[59]:0x29389
    at module.exports.encoding_for_model (/home/ggptadmin/gpt/chatgpt-clone/node_modules/@dqbd/tiktoken/tiktoken_bg.cjs:177:14)
    at askClient (/home/ggptadmin/gpt/chatgpt-clone/api/app/clients/chatgpt-client.js:71:15)    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async ask (/home/ggptadmin/gpt/chatgpt-clone/api/server/routes/ask/askOpenAI.js:174:20)
    at async /home/ggptadmin/gpt/chatgpt-clone/api/server/routes/ask/askOpenAI.js:87:10 {
  code: 'ERR_ENCODING_INVALID_ENCODED_DATA'
}

Code of Conduct

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

What was your input to reproduce? Did you only experience this once or is it continuing? Do you have any screenshots of the front end?

I've error handled any potential issues arising from encoding using the tokenizer. It would still be helpful if you could list steps to reproduce when you get the chance!

I deployed this service in my company and I can’t say who and what sent. But the backend crashed, after a reboot,  everything worked. If this is an archive again, I'll look at the logs.


[VS Code] Sharing workspace: Unable to connect to the remote server. TrackingId:d04f2cef-12c6-4b98-b1ff-67605c04db56, Address:sb://vsls-prod-ins-euw-private-relay.servicebus.windows.net/dbdd6f59553881eef2704b1c7b8e78c46152--d2486634-ddfc-476f-8e96-b89a1743fe7e, Timestamp:04.11.2018 11:14:37

<!--
For Visual Studio problems/feedback, please use the Report

Thanks for reporting this. Are you behind a proxy? If so, see here: https://docs.microsoft.com/en-us/visualstudio/liveshare/reference/connectivity#proxies
If you can reproduce the issue again, can you please run the command "Live Share: Export Logs" and drag-and-drop the zip here or send it to<EMAIL_ADDRESS>


add getter attribute to message

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+

bors r+


Ignore popup

Adds a popup buffer and refactors the status buffer selection logic for more consistent selection of files and hunks, as well as adding a flexible api for the range of selected items.

Fixes #260

Look at me back at it again with making different parts more and more consistent between each other, such as the different requirements for the popups. Is it commit, commits, revisions etc.
Now they all take the current selection context from the status buffer, which is also dogfed in the statusbuffer itself. It is not all done though and I still have to move the hunk selection staging over to the new api.
In large this will bring us one more step closer to the programmatic status buffer api

No objections to this change, just remember that the log buffer and reflog buffer are still passing in a table of oid strings to these popup constructors.

Yes thank you. I also need to make sure to reverse the commits before picking such as the cherry pick popup.

I do not know if this was a feature before, or if I just could never get it to work,
but now it works to stage and unstage a visual selection of files or hunks, and even a visual selection of files/hunks across sections in the statusbuffer, and have them all staged by s etc.
As they are sorted by path, it is not very easy to just visually select all the files in the same directory and stage them at once.
I am building this out to better allow the popups to utilize selected files and commits, rather than having to do their own lookup and logic, with no support for visual selections of files, as that was previously nested in the staging logic and free functions

Still some work left to do, but soon all stage/unstage/discard and popup will use the same simple api for getting what to act on, rather than them doing it internally in parts through multiple functions

I do not know if this was a feature before, or if I just could never get it to work,
but now it works to stage and unstage a visual selection of files or hunks, and even a visual selection of files/hunks across sections in the statusbuffer, and have them all staged by s etc.
As they are sorted by path, it is not very easy to just visually select all the files in the same directory and stage them at once.
I am building this out to better allow the popups to utilize selected files and commits, rather than having to do their own lookup and logic, with no support for visual selections of files, as that was previously nested in the staging logic and free functions

Yeah, that one works - it's not working for you? Well, good, as long as it still works haha

This is soon ready to go.
One of the advantages of the much more consistent selection is that you can visually select across sections, which previously no-op:ed as the selection was either a list of things, or a selection of a thing
Added a test to cover the case

I am pushing the ignore popup to a separate PR to keep one subject per PR

I am pushing the ignore popup to a separate PR to keep one subject per PR

Great call ;D

Left some notes - all-in-all, this is a very nice upgrade. Great work :D
I'll test-drive the branch at work this week and see if I can find anything not working.

Thank you.
It is nice to have all the selection logic in one place and structured, rather than juggling multiple returns and extra functions to get more from loose arguments.
Going to use this in the ignore popup to just very easily get the selected files during opening.

No kidding. Everything that can be done to wrangle the status buffer is a worthy goal, imo. Really makes it easy to bring the magit idea of "everything selected/under the cursor is interactive" easy to realize.

(I resolved the conflict so I could test this branch out)


Use leaflet.restoreview.js plugin to save and restore last user's map…

… position between sessions (#48)
I am not JS developer so please tell me if something is wrong with my PR. Thanks @nrenner!

Added another patch for 2nd part of #48. I added reference to Awesome font in index.html, but maybe you wish not to use it?
Again any comment's welcome, I am a truly newbie here!

Thanks for the PR! I do have comments, but don't worry, still learning myself. And I should have more documentation.
The build setup using Bower and Gulp is still a bit rough and not ideal. Also already outdated again, as people seem to have moved on to Webpack nowadays. But what I'm trying to achieve is that all dependencies are referenced and downloaded through Bower, so that the origin and the version used are documented and that managing and updating the depencencies gets a bit easier.
leaflet.restoreview:
I would prefer js/plugin/leaflet.restoreview.js to be added and downloaded via Bower although its an overhead in this case. The dir name plugin is a bit misleading here, intended for own configuration and extension of external plugins only.
As it has no bower.json and is not registered with bower (https://bower.io/search/), I think you can reference the repo and add it to the bower.json with
bower install makinacorpus/Leaflet.RestoreView#master --save

Then add the file to include (leaflet.restoreview.js) to the "overrides" section. Check if included with gulp debug.
leaflet.locatecontrol
Yes, I would prefer not to load another fontset, as we already have Glyphicons from Bootstrap, but Glyphicons is a bit limited and seems not to have a spinner. Not sure about the marker icon, maybe fa-location-arrow or something similar to glyphicon glyphicon-screenshot (but more GPSy) instead, what do you think?
But I might as well merge the commit as it is and think about that later, as I want to add more icons anyway and am not decided on the icon-/fontset yet.

Thanks!

[x] I moved leaflet.restoreview to bower
[x] I removed Awesome font dependency and instead use glyphicon-refresh and glyphicon-screenshot icons instead. They are not perfect but I guess it's OK for now. I also added overrides for locatecontrol plugin but I am unsure about it; could you take a look at it please?

Thanks for the update. Yes, the icons will do for now.
The bower override for locatecontrol isn't necessary, as the project already has a bower.json with a proper main section.
Could you please remove that again, then I think we're ready to merge.

OK I removed it, I can't wait to use these on brouter-web! :smile:


navigator: fix save mission state.

fix save_mission_state() function
https://github.com/PX4/Firmware/issues/12460

Looks right. What testing have you done?

@julianoes I found that by chance, as I was doing some work on mission.

@ToppingXu ok thanks. And the change is tested?


[no action] Warning re use of Webpack 4 in production mode.

If this didn't take me most of a day to track down, I wouldn't consider it worth posting here.
The latest Webpack, 4.1.1, in mode: production with default configuration, has a bug in minimization that affects Material-UI.  The bug occurs when UglifyJS attempts to inline a call to a function with a variable of the same name as a variable in the calling function.  I've seen it affect two independent places: in Modal (variables named container) and Popover (variables named transformOrigin).  The user-level symptom is that all modals break when opened.
See https://github.com/mishoo/UglifyJS2/issues/2842, and duplicate https://github.com/mishoo/UglifyJS2/issues/2843 which shows another symptom.  I saw both "is not defined" and "assignment to constant variable".
As noted in the Uglify issue, this can be mitigated by turning off inlining.  In Webpack 4 this undocumented feature can be used to tweak minimization:
const UglifyJsPlugin = require('uglifyjs-webpack-plugin')

{
optimization:
            minimizer: [

                new UglifyJsPlugin({
                    parallel: true,  // Webpack default
                    cache: true      // Webpack default
                    uglifyOptions: {
                        /*
                            inlining is broken sometimes where inlined function uses the same variable name as inlining function.
                            See https://github.com/mishoo/UglifyJS2/issues/2842, https://github.com/mishoo/UglifyJS2/issues/2843
                         */
                        compress: { inline:false },
                    },
                })
            ],
}

I expect you'll want to close this immediately, but maybe not, just to keep it in folks' face on the Issues page.
The bad inlined code can be easily read if you turn off mangle but leave inline on.  See https://github.com/mishoo/UglifyJS2/tree/harmony for settings.

@estaub Is this something actionable on our side?

@oliviertassinari , no, not that I'm aware of.
(I tried to flag that with [no action] in the title.)
I know it's a little spammy to post it here, but figured it might avoid some false reports of a material-ui bug.

@estaub Alright thanks for opening and documenting this issue. Hopefully it will help others!


Loss is always nan

Hello PeteryuX,
Thanks a lot for sharing your implementation of ESRGAN.
I have been testing some of the GAN based superresolution network recently. I have got a lot of training HR/LR images and would like to train the ESRGAN (PSNR+ESRGAN) network using your training code.
I have followed your instructions on data preparation and converted my 1,825,587 pairs of LR/HR samples to *bin.tfrecord checked dataset_checker no problem, LR/HR images displayed well, modified few lines of your code for the hardcoded paths etc. and started PSNR training on the RTX3090 GPU. However, the calculated and printed out "loss" is always "nan" in every iteration, and even after "successfully" finished PSNR training, the loss_D and loss_G in ESRGAN training is also shown as "nan".
in psnr training:
...
Training [>>                     ] 20004/600000, loss=nan, lr=2.0e-04  2.0 step/sec
...
in esrgan training:
...
Training [>>>                      ] 40000/285240, loss_G=nan, loss_D=nan, lr_G=1.0e-04, lr_D=1.0e-04  1.4 step/sec
[*] save ckpt file at ./checkpoints/esrgan/ckpt-32
Training [>>>>                     ] 47877/285240, loss_G=nan, loss_D=nan, lr_G=1.0e-04, lr_D=1.0e-04  1.4 step/sec
...
Do you have any suggestions on this issue?
I here attach the psnr+esrgan parameter files:
psnr.yaml:
batch_size: 64
input_size: 32
gt_size: 128
ch_size: 3
scale: 4
sub_name: 'psnr_pretrain'
pretrain_name: null
network_G:
nf: 64
nb: 23
train_dataset:
path: '/data/EOSC/EOSC_sub_bin.tfrecord'
num_samples: 1825587
using_bin: True
using_flip: True
using_rot: True
test_dataset:
EOSC_path: '/data2/EOSC_test'
niter: 600000
lr: !!float 2e-4
lr_steps: [200000, 300000, 400000, 500000]
lr_rate: 0.5
adam_beta1_G: 0.9
adam_beta2_G: 0.99
w_pixel: 1.0
pixel_criterion: l1
save_steps: 20000
esrgan.yaml:
batch_size: 64
input_size: 32
gt_size: 128
ch_size: 3
scale: 4
sub_name: 'esrgan'
pretrain_name: 'psnr_pretrain'
network_G:
nf: 64
nb: 23
network_D:
nf: 64
train_dataset:
path: '/data/EOSC/EOSC_sub_bin.tfrecord'
num_samples: 1825587
using_bin: True
using_flip: False
using_rot: False
test_dataset:
EOSC_path: '/data2/EOSC_test'
niter: 285240
lr_G: !!float 1e-4
lr_D: !!float 1e-4
lr_steps: [60000, 120000, 180000, 240000]
lr_rate: 0.5
adam_beta1_G: 0.9
adam_beta2_G: 0.99
adam_beta1_D: 0.9
adam_beta2_D: 0.99
w_pixel: !!float 1e-2
pixel_criterion: l1
w_feature: 1.0
feature_criterion: l1
w_gan: !!float 5e-3
gan_type: ragan  # gan | ragan
save_steps: 20000
Any help would be much appreciated! Thank you!

Did you solve it?


Is ServiceBusTrigger supported at all?

[FunctionName("ServiceBusTest")]
public static async Task ServiceBusTest(
    [ServiceBusTrigger("qwerty", Connection = "MyConnectionString")] string message)
{ }

throws "Microsoft Azure WebJobs SDK ServiceBus connection string 'MyConnectionString' is missing or empty." before Main() is called so I have no way of providing a connections string.

@fabiocav I just want a way to do something similar to .ConfigureAppConfiguration(...) for the host. I can probably survive with App Service Key Vault references for now but what if I need to do something that is not KeyVault? Is it possible to define my own Reference implementation similar to KeyVault like "@MyOwn.NotKeyVault(...)"? That would be a real solution as I would be able to build that reference implementation for whatever .NET the host uses.

@fabiocav I also want to be able to access the app configuration values from Azure during bootstrap.  It sounds like this isn't in scope for GA (must use local.setting.json), which I'm not really excited about.  I'm just using the consumption plan, not premium or app service.

For configuration values used by the triggers, that's where there's a limitation. For configuration within the context of your app, you should have the ability to do that just as you would with other .NET apps.

This may or may not be obvious to others, so I'll post this just in case.  If you use the "Application Settings" under the configuration tab in the azure portal (functions) you can put the connection string there and abstract it from your code.  I would like this to be in key vault for consistency, but it's at least an acceptable workaround for my use case.
This has allowed me to get a working version of Service Bus trigger working

Key Vault is supported as a source of app settings configuration.
Please see https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references for information

Key Vault is supported as a source of app settings configuration.
Please see https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references for information

Note that if you go this route and you're using Key Vault via a config builder, you should avoid loading secrets with the same name.
If the referenced secret in app configuration drifts (e.g. a new version is added to the vault), the function runtime will error on consumption plans because the trigger changed (at least for the in-process worker: https://github.com/Azure/azure-functions-host/issues/7210)

@phekmat indeed that is the behavior of the configuration system and order of registration matter here. That said, configuration does follow the order of precedence described in the feature documentation, where last one wins.

For triggers, this won't be supported at GA. The alternative here is to use App Service Key Vault references in the meantime (https://docs.microsoft.com/en-us/azure/app-service/app-service-key-vault-references)

@fabiocav I'm really looking forward to using builder.AddAzureKeyVault(...) and then referencing a secret in e.g. an EventHubTrigger. As I understand from your comment, this is currently not supported. Is this a feature that's being considered? If so, do you have any idea where this fits in the roadmap.

For us Key Vault references is a good enough solution that at least unblocked us
We still have to wrap functions in #if !DEBUG like this

though because devs can't use Key Vault references locally and we have to copy-paste the secret to local.settings.json and then remove #if !DEBUG in order to run ServiceBus trigger functions locally.
I believe I was promised at least User Secrets support in some other issue in order to mitigate the pain of not being able to use secrets from KeyVault locally.

Any news regarding this?
Creating a dotnetisolated .NET 5.0 azure function with a ServiceBusTrigger, is it still true that I can't reference my local user-secrets store when filling in the connectionstring?
When running in Azure, KeyVault reference is good, but for running locally on my devmachine I want to reference the local connectionstring that I have set in user-secrets.

I agree, seems like quite the step back. Can't use app config either. To run locally this is a real problem.

Any update on this ?

As a workaround I have set AzureWebJobsServiceBus in properties/launchSettings.json and added that file to .gitignore. This file does not need to be published (e.g. <CopyToPublishDirectory>never</CopyToPublishDirectory>). When running locally this is shown in the console:

Skipping 'AzureWebJobsServiceBus' from local settings as it's already defined in current environment variables.

So I've set the value in local.settings.json to "secretLaunchSetting" as a reminder that the value can be found elsewhere.

Unfortunately, the config gap is a limitation of the system we will not be addressing any time soon. The host needs to know about all these config values without loading any customer assemblies or running the worker at all. All of the asks here are around providing config values to the host via code and custom config sources. This will just not be possible as it is a core requirement for us to monitor triggers without loading or running any customer code.
Going to close this for now. If we decide to revisit this later we can circle back.


Added support for new filter fields for listing events

Description
This PR adds new fields for filtering events as well as a new enum.
License

I confirm that this contribution is made under the terms of the MIT license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

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

Project coverage is 80.13%. Comparing base (b42712b) to head (97382bb).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #245   +/-   ##
=========================================
  Coverage     80.13%   80.13%
  Complexity      287      287
=========================================
  Files            31       31
  Lines           861      861
  Branches         87       87
=========================================
  Hits            690      690
  Misses          121      121
  Partials         50       50

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


Add return type to ModuleWithProviders

Add return type for ModuleWithProviders to be compatible with Angular 9.1.

@tobiasengelhardt Why was this closed?


Authorization between nuxtjs and the backend API

I have a Vuejs application created using Nuxtjs. I am also using Django as the backend server, and I made an API to interact with the backend server (Django) and front-end app (Vuejs/Nuxtjs). And any API related fetch are done in the AsyncData function of the page to render the data on the server-side using axios. Also, I am using json web token authentication, and the API generates a jwt token after successful login which is stored in the cookie. So on the backend, it will always check for the request's authorization header for the token. If the request is from a logged in user (authorized token) then return authenticated json data, or else return non authenticated data.
The problem:
When the user navigates to the app, I would like to check if the user is authenticated. If the user is authenticated, render the authenticated page. If not then display non authenticated page.
My thoughts:
When the fetch is done from the App on the AsyncData function, I would check whether there is any value for the cookie. If there is then send the token with the request's authorization header. But, since the page will be rendered on the server first, and not on the client side (where the cookie actually is) it will never find the token for the authorization.
How can I check if the user is already logged in or not so that I can get authenticated and non authenticated data respectively from the API?

When the user navigates to the app, I would like to check if the user is authenticated. If the user is authenticated, render the authenticated page. If not then display non authenticated page.

You may use nuxt pages middleware for doing exact same job.

But, since the page will be rendered on the server first, and not on the client side (where the cookie actually is) it will never find the token for the authorization.

That's true. But one thing we may do is using req object which is available in server side to retrieve client side cookies and append them to axios Cookies.
Unfortunately, we still don't have a complete guide on SSR authentication but for second problem of having Cookies in server-side i recommend using [axios-module(https://github.com/nuxt-community/axios-module) it will do this automatically.
For the first problem, i also suggest taking a look at auth-module which integrates with axios for a complete solution. (You may also brow only some parts like auth middleware)

@Benjamin5050 I've been building Django + NuxtJS. I use Django https://github.com/GetBlimp/django-rest-framework-jwt to check token. In your case, you can use Middleware to do.

@pi0 Hi! I have checked out the nuxt-axios module, but I am still not clear. It does not tell how to retrieve cookie from the client side. How can I retrieve client side cookie and add them to axios?
@feedgit Yes, I am also using django-rest-framework-jwt with django-rest-framework. How are managing the token between the client side and the nuxt server?

I'm using Rails as an API and Nuxt.js.
I have pretty much the same problem. Tokens are stored in the client side, fetch runs only the server side. The closest to a decent route authorization I managed to do is to check the cookie on page create. But it still displays the "protected" page content for a second before it is redirected to a login page.

Hi @Benjamin5050 and @samirph
I think the auth-module will help you solve the problem because it manage both SSR and client cookie registration, try to use all the attributes the library offers

I've seen that auth-module before.
This module uses axios for its requests, but my application is making only apollo requests.

We use django with REST framework JWT Auth combined with nuxtServerInit to achieve this. When a user logs in, the auth token gets set to the cookie. When nuxtServerInit runs, this token is extracted from the cookie and verified. It looks something like this:
export const mutations = {
  setError (state, error) {
      state.loginError = error
  },
  logout (state) {
    Cookies.set('token', null)
    Cookies.set('id', null)
    state.user = null
  },
  setUser (state, { token, id }) {
    Cookies.set('token', token)
    state.user = { id }
  }
}

export const actions = {
  async nuxtServerInit ({ dispatch, commit }, { req }) {
    if (req.headers.cookie) {
      let { token } = cookie.parse(req.headers.cookie)
      try {
        var { data } = await axios.post(endpoint + '/auth/verify', { token })
        if (data.token) {
          commit('setUser', { token: data.token, id: data.id })
        }
      } catch (err) {
        if (err.response.status === 400) {
             commit('logout')
        }
      }
    }
  },
  async login ({ commit }, { email, password }) {
    try {
      var { data } = await axios.post(endpoint + '/auth/login', { email, password })
      await commit('setUser', {
        token: data.token,
        userId: data.id
      })
    } catch (err) {
      if (err.response.status === 400) {
        commit('setError', 'Invalid credentials')
      }
    }
  }
}


Add documentation caveat without main guard

If a script's code isn't behind a main guard, this fails.
Add documentation with basic example of pass/fail scripts.

Example failing script:
import gs_fastcopy

gs_uri = "gs://bucket/path/tmp.txt"
with gs_fastcopy.write(gs_uri) as f:
    f.write(bytes([1, 2, 3]))

Example passing script:
import gs_fastcopy

def main():
    gs_uri = "gs://davids-genomics-data-public/cellular-segmentation/deep-cell/vanvalenlab-multiplex-20200810_tissue_dataset/mesmer-sample-3-dev/tmp.txt"
    with gs_fastcopy.write(gs_uri) as f:
        f.write(bytes([1, 2, 3]))

if __name__ == "__main__":
    # The freeze_support call is required to produce a frozen executable.
    # See: https://docs.python.org/3/library/multiprocessing.html
    # heading: Safe importing of main module
    # freeze_support()
    main()

Note the optional freeze_support call for frozen executables.

Failure error:
RuntimeError:
        An attempt has been made to start a new process before the
        current process has finished its bootstrapping phase.

        This probably means that you are not using fork to start your
        child processes and you have forgotten to use the proper idiom
        in the main module:

            if __name__ == '__main__':
                freeze_support()
                ...

        The "freeze_support()" line can be omitted if the program
        is not going to be frozen to produce an executable.

        To fix this issue, refer to the "Safe importing of main module"
        section in https://docs.python.org/3/library/multiprocessing.html


added australia to the list of phone numbers

Australia is much needed. I'm looking forward to this change.

Thanks.


Add Install section

systemd do not enable the service without Install section

I just see that there is #24


v2024 07 14 - VST3 format not showing up in REAPER.

As the title says, the VST3 version of the plugin isn't showing up in REAPER. It's been installed, but it's not showing up.
The CLAP and AU do show up.

Which macOS and reaper version? Intel or arm? Thanks!

Macos 13.6.3, latest reaper version, arm
Thank you!
On Jul 19, 2024 at 07:24 +0300, Paul @.***>, wrote:

Which macOS and reaper version? Intel or arm? Thanks!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>


OSIDB-3004: Add suggestions to flaw owner field

OSIDB-3004: Add suggestions to flaw owner field
Checklist:

[x] Linting passed
[x] Type checks passed
[x] Tests suite passed
[x] Commits consolidated
[x] Changelog updated
[x] Test cases added/updated
[x] Jira ticket updated

Summary:
Added a dropdown suggestion integrated with jira

Closes OSIDB-3004

For some users there are two options, I think we could filter those cases to use only the one that has an email associated

I think that is only on stage, in production there's only 1 user, also we cannot filter, because not all users have the email as the user id (mine for example)


test: create integration test suite

Create a Gradle test suite for integrations tests, move the disabled
TisTraineeApplicationTest to the new suite and enable it.
Rewrite the controller tests, split in to unit tests and integration tests.
The unit tests should provide the actual test coverage, checking all
branches/conditions etc.
The integration tests should verify the main/happy path of each
endpoint against the expected state of the database.
NO-TICKET

Much neater! The build.gradle.kts changes look quite deep, or at least unfamiliar to me 😀

It is a deviation from our usual, super simple, build scripts. I was hoping for a quick and easy config when I first looked in to it but no.
The Test Suite plugin is incubating too, which doesn't help finding clear info and examples. The previous alternative was more config-ey, so this seems the better alternative even in an incubating state.


fix: Support boolean fields with is prefix for JSON serde

When a boolean field is used to define collection schema - For Java class or Kotlin the document serialization of object will drop is prefix based on standard accessor convention. This PR adds a config flag that will allow users to keep the is prefix intact for documents.
This PR also updates API proto submodule.

Codecov Report
Base: 83.75% // Head: 83.68% // Decreases project coverage by -0.07% :warning:

Coverage data is based on head (94f5be0) compared to base (6a65b7a).
Patch coverage: 72.72% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff              @@
##               main     #144      +/-   ##
============================================
- Coverage     83.75%   83.68%   -0.07%
  Complexity      640      640
============================================
  Files            71       71
  Lines          2000     2011      +11
  Branches        184      189       +5
============================================
+ Hits           1675     1683       +8
  Misses          274      274
- Partials         51       54       +3

Impacted Files
Coverage Δ

...grisdata/db/client/config/TigrisConfiguration.java
74.54% <72.72%> (-0.21%)
:arrow_down:

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

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


Feature: Http 2

Summary:
Briefly describe the changes made in this PR.
Issue Reference(s):
Fixes #605
/claim #605
Build & Testing:

[x] I ran cargo test successfully.
[x] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[x] I have performed a self-review of my own code.

@ologbonowiwi Can you look at the conflicts please.


weird bundle update <specific gem> behavior with Gemfile.lock's with platform locks

pretty decent replication case that isn't too horrible here:
% git clone https://github.com/chef/opscode-pushy-client.git
% cd opscode-pushy-client
% git checkout 65ea3f70313ab23aeb8ac58c8b712c18c3bc979e
% bundle update opscode-pushy-client
Fetching gem metadata from https://rubygems.org/........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Bundler could not find compatible versions for gem "win32-api":
  In snapshot (Gemfile.lock):
    win32-api (= 1.5.3)

  In Gemfile:
    win32-api x86-mingw32

    windows-pr x86-mingw32 was resolved to 1.2.6, which depends on
      win32-api (>= 1.4.5)

Running `bundle update` will rebuild your snapshot from scratch, using only
the gems in your Gemfile, which may resolve the conflict.
% bundle --version
Bundler version 1.16.1

win32-api 1.5.3 should satisfy >= 1.4.5 so something is going wrong.

Can you please attach the output of bundle env, we can't really help you without having a Gemfile & Gemfile.lock available.

Digging into this, I think the issue is that windows-pr is actually a ruby platform gem, and so Bundler expects to be able to find ruby versions of its dependencies

I think the issue is also that windows-pr isn't actually used by any of the other gems in the bundle, causing the platform headache. Simply removing it from the Gemfile seems to fix the issue for me :)

lolz.  i will give that a go.  =)

ping @lamont-granquist were you able to resolve your issue?


Floodlight throwing java.lang.ClassNotFoundException: org.restlet.engine.ssl.SslUtils while trying to set up REST API using HTTPS

Hi! I am trying to set up my restserver to use HTTPS on port 8081.
However, when I try to start the controller, it throws out this exception:

Any help in resolving this issue will be much appreciated!
Thanks!

@atharvak21 this looks like is not a bug but a problem. We typically reserve "Issue" as a place to report a potentially Floodlight bug that needs to be resolved.
Do you mind to re-post this question to our Floodlight mailing list<EMAIL_ADDRESS>one more time? We'll be happy to help you resolve the issue there. Thanks for your kind understanding!
I'll close this issue for now -- feel free to re-open it if you think this is a Floodlight bug. Thanks.


streams.py still has several instances of .params()

The holoviews.streams module still has several usages of .params(), the old-style API of param, which causes warnings when using holoviews (see https://github.com/pyviz/panel/issues/420).

@jlstevens, I thought you had eliminated all those?  Sounds like it's time to do a deeper search.

Don't think @jlstevens was involved in any of these updates. Would be happy to have help on that front of course.


Sending payment

        Congratulation You successfully receive the payment of $2000 bitcoin on your blockchain wallet account

https//:

<EMAIL_ADDRESS>


Add merge method

Hello!
First, thanks for creating this library, it's great.
I made a small addition in my own fork which I needed and thought I'll ask if you're interested in pulling in the changes. I know this project is in passive maintenance mode and I fully respect that. I'm perfectly fine with using my own fork, just thought someone may find this useful as well. Feel free to close it.

This adds merge method which allows building a final chain by merging 2 other chains of the same order:
use markov::Chain;

let mut new_chain = Chain::of_order(2);
new_chain.feed_str("I like cats and I like dogs");

let mut another_chain = Chain::of_order(2);
another_chain.feed_str("I like puzzles and I don't like dogs");
another_chain.feed_str("I don't like puzzles and I like dogs");

new_chain.merge(another_chain);

Handy when you want to speed up training by parallelizing it with e.g. rayon:
use markov::Chain;
use rayon::prelude::*;

let input = <iterator built from lots of data, e.g. files on disk>;

let chain = input
  .par_bridge()
  .map(|items| Chain::new().feed(&items))
  .reduce(|| Chain::new, |a, b| a.merge(b));

Looks good to me, thanks!


[Enhancement] Project boards / KanBan: Compact view mode

I've just started trying out the new Project boards / KanBan feature, which is really great, however there are a number of things that would need to be improved before it is really usable for me:
When you have a project (as in repo) with many hundreds of open issues, the KanBan board would be a great place to try to get an overview of a subset of these. However, when issues have a usefully descriptive name thats wraps to 2 or more lines, a milestone assigned and several labels, they take up a lot of screen space in the project 'board' or column, such that my board is full with only 3 issues and I have to use the horizontal scroll to see the rest. Thus it is pretty hard to get an overview, rendering the purpose of the board fairly useless. It is still much easier for me to get an overview of a particular category / status of issues by using labels.

We need a view mode where 10s of issues can be seen within the 'board' without horizontally scrolling.

The horizontal scrolling is really filthy. It seems to be a flex container that wraps to the next column if needed. I'd just avoid flex here completely and make those elements normal blocks in sequence
I made a dirty quickhack to override horizontal scrolling
.board-column > .cards {
    flex: 0;
    display: block;
    height: 100%;
    flex-grow: 1;
}

.ui.cards {
    flex-wrap: nowrap;
}

.ui.card, .ui.cards > .card {
    display: block;
    min-height: 3rem;
}

.ui.cards > .card {
    margin-bottom: 0.5rem !important;
}

This snippet shouldn't get pushed into the repo somewhere, but just be taken as a reference point


Error in plot_signals

Hi,
I have problem with factorCol and when I use this command :  plot_signals(Autotuner,  threshold, sample_index = 1:3, signals = signals), I am facing with this error:Error in plot_signals(Autotuner, threshold, sample_index = 1:3, signals = signals) :
factorCol is not within the MSest metadata.

Good Afternoon,
This is pretty weird... Were you able to run the command createAutotuner prior to running plot_signals? Did this give you an error? The error indicates that the string containing the name of a column from your metadata was not found within the column names of the metadata. However, createAutotuner should have checked for the same thing.

Hi,
Yes It looks weird. createAutotuner is: > Autotuner <- createAutotuner(rawPaths,

                          metadata,

                          file_col = "Raw.Spectral.Data.File",

                          factorCol = "Factor.Value.genotype.")

~~~ Parsing Raw Data into R ~~~

~~~ Extracting the Raw Data from Individual Samples ~~~

~~~ Storing Everything in Autotuner Object ~~~

~~~ The Autotuner Object has been Created ~~~
There isn't any error what I should do. Could you please find a solution I realy tend to run it.
Thank you

I think the easiest way for me to solve the problem would be if I tried to recreate the issue on my computer. Could you please share 3 of your samples and the metadata spreadsheet with me?

Hi again,
Sure
It is a big file I couldn't upload that I only mention the name of dataset form metabolight: MTBLS265
(Person01_blood_youth_POS.mzML, Person02_blood_youth_POS.mzML, Person03_blood_youth_POS.mzML)
Thank you

Which file should I use for metadata?

a_mtbls265_POS_mass_spectrometry.txt

Awesome! Thanks! I'll try and have this fixed in the next few days.

Thank you so much. I am looking forward to hearing from you

Good Afternoon,
I think I identified the issue. I fixed a bug with checking the column names within createAutotuner. If you were to run createAutotuner, you should receive a similar error as what you are getting now.
So, how do you fix it? You are not providing the name of a column from your metadata into the argument factorCol. Try running the software again with a column name within your metadata. Please, do let me know if you have any issues.

Good morning,
Thank you for your time but It is so weird. I have same error because I had inserted a column as factorCol and there is not any error for  createAutotuner again.
a_mtbls265_POS_mass_spectrometry.txt

Good Morning,
You don't want to insert a column. You want to insert a string that contains the name of a column. Is this what you did?
All the best,
Craig


Add an ability to set a diameter of the selection circle

Add the property selectionCircleDiameter into the header file

Can you look into why the tests fail?

RSully, the problem is here:
color = colorFromCMYK(0, 0, 0, 1, 0.5);
RSGetComponentsForColor(components, color);
testColor = [UIColor colorWithWhite:0 alpha:0.5];
[self assertColor:color equalsColor:testColor];

testColor = [UIColor colorWithRed:0 green:0 blue:0 alpha:0.5];
[self assertColor:color equalsColor:testColor];

colorFromCMYK returns next color with components:
([0] = 0.10362756997346878, [1] = 0.099162332713603973, [2] = 0.097511671483516693, [3] = 0.5)
I seem my PR is not the reason of that.


Support Scientific Linux CVEs [edited]

Currently RHEL CVE feeds are not being used, so scanning RHEL/Scientific linux results in  "cannot perform CVE scan: no CVE data is currently available for the detected base distro type (redhat:6,redhat:6.9)"
Any plans to sync redhat distro CVE feeds?

RHEL6 is supported and the feed should be sync'd when you run anchore feeds sync
It's possible that we didn't correctly identify the distro.
If it's a public image can you give us the name if not can you send the content of
/etc/redhat-release
and etc/os-release

Ah. my bad - this was a Scientific Linux image
bash-4.1# cat /etc/redhat-release
Scientific Linux release 6.9 (Carbon)
Am assuming that's unsupported?

Is there also a /etc/os-release file - if so please copy it here.
I presume the vulnerabilities will be similar - looks like they have SLSAs rather than RHSAs, we'll need to look to see if there's a feed or if we just treat it like RHEL - the challenge then is that we may say a fix is available, since Red Hat has one, but it may not be available.
We'll do some research it looks like there are a number of images on DockerHub we can check out.

Changing title of issue to "support Scientific Linux".
As part of this we should validate various SL6,7 images

Any update on this? Thanks!

@hariramb is there a specific public image you're looking at or are these your own images? I'm looking at the cern/slc6-base:latest. Is that similar to what you're using or do you have a specific flavor you are building yourself?

@zhill I tried checking in on the images I am trying to scan on - these are images that we build internally
bash-4.1# cat /etc/redhat-release
Scientific Linux release 6.9 (Carbon)
The CERN image seems like the same version
[root@4ad424fcb9d1 /]# cat /etc/redhat-release
Scientific Linux CERN SLC release 6.9 (Carbon)
So, I think the answer is yes to your question. Let me know if that helps.

Hi all,
I've made a commit to the latest anchore (master and 1.1-master) that includes a mapping between images that identify as 'redhat' and out internal RHEL/centos flavor (which is used for both package style analysis and then related CVE scanning).  If you give it a try, would love to hear about what you think!
With the fix, both package detection/analysis and cve-scans produce results:
# docker pull docker.io/cern/slc6-base
...
...
# anchore analyze --image docker.io/cern/slc6-base --force
Analyzing image: docker.io/cern/slc6-base
96e0f7cea2df: analyzing ...
96e0f7cea2df: analyzed.
# anchore --plain query --image docker.io/cern/slc6-base list-packages all | wc
    153     608   10443
# anchore --plain query --image docker.io/cern/slc6-base cve-scan all | wc
     14     104    2131

@nurmi
I ran a scan using the Anchore CLI dev head  (based on info here) -https://github.com/anchore/anchore/wiki/Installing-Anchore
`
docker pull anchore/cli:dev
docker run -d -v /var/run/docker.sock:/var/run/docker.sock --name anchore anchore/cli:dev
docker pull docker.io/cern/slc6-base
docker exec anchore anchore --plain query  --image docker.io/cern/slc6-base cve-scan all
CVE_ID Severity *Total_Affected Vulnerable_Package Fix_Available Fix_Images Rebuild_Images URL
Warning Output
074156743960 (cern/slc6-base:latest) cannot perform CVE scan: no CVE data is currently available for the detected base distro type (redhat:6,redhat:6.9)
docker exec anchore anchore --plain query  --image docker.io/cern/slc6-base list-packages all
Image_Id Repo_Tags Package Version
`
Does this work only if I build from source?

Can confirm building from source works. I checked both the slc6-base docker image and internal SL6 images. Detected and listed packages properly. The CVE scan came back with zero output, but that might be because of completely patched images. Will try to find some vulnerable images and recheck.
When will this be available in anchore:cli/dev docker image? Thanks

Hi @hariramb - That is looking good - as long as you get package details and do not get the distro not supported warning, then the scanner should be working properly.
In terms of the dev container, we can roll a new version that contains this update, especially if you can acknowledge that the fix is looking right for your use case!
Thank You
-Dan

Hey @nurmi  - Yup, all looks good from my end. I ran scanner on a vulnerable SL6 image and it did report vulnerabilities.
Let me know if you need anything else. Will wait on the container update.

Hi @hariramb  - thanks!  We'll run our tests and then will push a new dev container, I'll let you know here when it has been pushed (or, if you're subscribed to the image on anchore.io, then you'll get a notification email automatically when the image is updated!)
Best
-Dan

Hi @hariramb - I just pushed a new docker.io/anchore/cli:dev container that has the latest from anchore master - should all synced up.
Thanks again
-Dan


Fabric SQL Db audit: Audit your DB in a breeze, with Microsoft Fabric

Project name
Fabric SQL DB audit
Description
The solution proposed involves the collection of SQL audit logs and their near real-time streaming in a simple way, into Microsoft Fabric thanks to its simplicity
This efficient process ensures that logs are stored systematically and securely.
Furthermore, the solution offers additional capabilities that are critical for data analysis and management.
Thanks to Fabric's capabilities, include the ability to analyze audit events with LLM and the compatibility with various data scientist tools.
This solution, therefore, not only streamlines the data collection process but also enhances data utility, making it a valuable addition to any data management strategy.
Project Repository URL
https://github.com/gianlucadardia/FabricHack.git
Project video
https://github.com/gianlucadardia/FabricHack/blob/main/video/FabricHack.mp4
Team members
<EMAIL_ADDRESS>

sorry for duplication