Fix KYLIN-3485

Can one of the admins verify this patch?

Pull Request Test Coverage Report for Build 3405

0 of 18 (0.0%)  changed or added relevant lines in 4 files are covered.
5 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.0009%) to 23.235%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

source-hive/src/main/java/org/apache/kylin/source/jdbc/JdbcSource.java
0
1
0.0%

source-hive/src/main/java/org/apache/kylin/source/hive/HiveSource.java
0
1
0.0%

server-base/src/main/java/org/apache/kylin/rest/service/TableService.java
0
3
0.0%

source-kafka/src/main/java/org/apache/kylin/source/kafka/KafkaSource.java
0
13
0.0%

Files with Coverage Reduction
New Missed Lines
%

server-base/src/main/java/org/apache/kylin/rest/service/TableService.java
1
13.82%

core-cube/src/main/java/org/apache/kylin/cube/inmemcubing/MemDiskStore.java
4
78.12%

Totals

Change from base Build 3403:
0.0009%

Covered Lines:
15662

Relevant Lines:
67408

💛  - Coveralls

Local CI ScreenShot.


Add support of PrometheusRawMetricsProvider for the Pulsar-Proxy

please don't merge using the button. I will merge the patch maintaining the original author @cbornet

closed in favour of https://github.com/datastax/pulsar/pull/37
otherwise CI doesn't run from forks


proxy: Ignore visibility annotation if proxy is disabled

Description
This is to avoid the below error if proxy is disabled as part of
installation, but the visibility annotation is added to pods later.
2023-08-11T12:42:41.390575371Z goroutine 1522 [running]:
2023-08-11T12:42:41.390581994Z github.com/cilium/cilium/pkg/proxy.(*Proxy).CreateOrUpdateRedirect(0x0, {0x3ae74b8, 0xc000650280}, {0x3aeb440?, 0xc0016e4560?}, {0xc0010ba1b0, 0x12}, {0x3afd260, 0xc000982000}, 0xc001c9c980)
2023-08-11T12:42:41.390589198Z  github.com/cilium/cilium/pkg/proxy/proxy.go:459 +0xb7
2023-08-11T12:42:41.390596081Z github.com/cilium/cilium/pkg/endpoint.(*Endpoint).addVisibilityRedirects(0xc000982000, 0x1, 0xc001874ba0?, 0xc001c9c980?)
2023-08-11T12:42:41.390602613Z  github.com/cilium/cilium/pkg/endpoint/bpf.go:343 +0x443
2023-08-11T12:42:41.390614345Z github.com/cilium/cilium/pkg/endpoint.(*Endpoint).addNewRedirects(0xc000982000, 0xc001874870?)
2023-08-11T12:42:41.390651325Z  github.com/cilium/cilium/pkg/endpoint/bpf.go:424 +0x3c5
2023-08-11T12:42:41.390658068Z github.com/cilium/cilium/pkg/endpoint.(*Endpoint).runPreCompilationSteps(0xc000982000, 0xc000e31800, 0x0)
2023-08-11T12:42:41.390663999Z  github.com/cilium/cilium/pkg/endpoint/bpf.go:802 +0x4fe
2023-08-11T12:42:41.390669690Z github.com/cilium/cilium/pkg/endpoint.(*Endpoint).regenerateBPF(0xc000982000, 0xc000e31800)
2023-08-11T12:42:41.390675451Z  github.com/cilium/cilium/pkg/endpoint/bpf.go:542 +0x1a5
2023-08-11T12:42:41.390681112Z github.com/cilium/cilium/pkg/endpoint.(*Endpoint).regenerate(0xc000982000, 0xc000e31800)
2023-08-11T12:42:41.390686893Z  github.com/cilium/cilium/pkg/endpoint/policy.go:467 +0x9c6
2023-08-11T12:42:41.390692564Z github.com/cilium/cilium/pkg/endpoint.(*EndpointRegenerationEvent).Handle(0xc000131b50, 0x0?)
2023-08-11T12:42:41.390698385Z  github.com/cilium/cilium/pkg/endpoint/events.go:53 +0x325
2023-08-11T12:42:41.390704045Z github.com/cilium/cilium/pkg/eventqueue.(*EventQueue).run.func1()
2023-08-11T12:42:41.390709716Z  github.com/cilium/cilium/pkg/eventqueue/eventqueue.go:245 +0x142

Fixes: #27594
Testing
Testing was done locally with l7Proxy=false, and then annotate a pod with visibility annotation
$ k annotate pod client-77bf9989dc-984xp policy.cilium.io/proxy-visibility="<Egress/80/TCP/HTTP>" --overwrite
pod/client-77bf9989dc-984xp annotate
$ ksyslo ds/cilium --timestamps | zgrep "ignoring L7 proxy visibility policy as L7 proxy is disabled"
2023-08-20T13:02:08.241508927Z level=warning msg="ignoring L7 proxy visibility policy as L7 proxy is disabled" ciliumEndpointName=default/client-77bf9989dc-984xp containerID=1ea0a77f5d containerInterface=eth0 datapathPolicyRevision=0 desiredPolicyRevision=0 endpointID=759 identity=831 ipv4=<IP_ADDRESS> ipv6= k8sPodName=default/client-77bf9989dc-984xp subsys=endpoint

/test

/test

/test


Fix tests for github actions

making initial commit to see if these failing tests were the cause for the actions failing.

closes #213


[Question]about creating the 'adapters.npz' file

I am currently following the finetuning sample of "https://heidloff.net/article/apple-mlx-fine-tuning/" url with mlx_lm, but the 'adapters.npz' file is not created even after iter=600. I don't know if the tutorial URL I'm referring to is incorrect. Could you provide a guide?
Part of the fine tuning code being referenced :
!python lora.py
--model mistralai/Mistral-7B-Instruct-v0.2
--train
--batch-size 1
--lora-layers 4
--data my-data-text
ls -la
-rw-r--r--   1 niklasheidloff  staff  1708214 May 12 13:12 adapters.npz
The fine-tuning produces an ‘adapters.npz’ file which can be converted into the safetensors format. <--adapters.npz file is not created!

Below, I share the fine tuning code I performed and the output recorded during training.
run : Jupyter Notebook with python=3.11, macos 14.5(Mac pro M1 max 64GB)
*** Code :
!python -m mlx_lm.lora
--model "google/gemma-2b-it"
--train
--iters 600
--data data
--steps-per-eval 100
--max-seq-length 2400 \                #Due to the nature of the training data I had, max-seq-length was set to 2.4k.
--learning-rate 2e-4
# --resume-adapter-file checkpoints/600_adapters.npz
*** Output:
None of PyTorch, TensorFlow >= 2.0, or Flax have been found. Models won't be available and only tokenizers, configuration and file/data utilities can be used.
Loading pretrained model
Fetching 9 files: 100%|████████████████████████| 9/9 [00:00<00:00, 85792.58it/s]
Loading datasets
Training
Trainable parameters: 0.033% (0.819M/2506.172M)
Starting training..., iters: 600
Iter 1: Val loss 3.936, Val took 215.383s
Iter 10: Train loss 2.987, Learning Rate 2.000e-04, It/sec 0.028, Tokens/sec 186.170, Trained Tokens 65620, Peak mem 69.060 GB
Iter 20: Train loss 1.504, Learning Rate 2.000e-04, It/sec 0.023, Tokens/sec 178.319, Trained Tokens 142273, Peak mem 69.060 GB
Iter 30: Train loss 0.448, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 172.839, Trained Tokens 220139, Peak mem 69.060 GB
Iter 40: Train loss 0.280, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 173.244, Trained Tokens 297254, Peak mem 69.060 GB
Iter 50: Train loss 0.237, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 172.502, Trained Tokens 374350, Peak mem 69.060 GB
Iter 60: Train loss 0.252, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 175.211, Trained Tokens 445673, Peak mem 69.060 GB
Iter 70: Train loss 0.238, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 176.555, Trained Tokens 517723, Peak mem 69.060 GB
Iter 80: Train loss 0.139, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 176.730, Trained Tokens 600930, Peak mem 69.060 GB
Iter 90: Train loss 0.132, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 169.215, Trained Tokens 683801, Peak mem 69.060 GB
Iter 100: Val loss 0.148, Val took 200.288s
Iter 100: Train loss 0.163, Learning Rate 2.000e-04, It/sec 0.218, Tokens/sec 1688.886, Trained Tokens 761390, Peak mem 69.060 GB
Iter 100: Saved adapter weights to adapters/adapters.safetensors and adapters/0000100_adapters.safetensors.
Iter 110: Train loss 0.174, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 165.624, Trained Tokens 839339, Peak mem 69.060 GB
Iter 120: Train loss 0.143, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 166.529, Trained Tokens 922932, Peak mem 69.060 GB
Iter 130: Train loss 0.214, Learning Rate 2.000e-04, It/sec 0.023, Tokens/sec 165.572, Trained Tokens 994731, Peak mem 69.060 GB
Iter 140: Train loss 0.162, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 170.473, Trained Tokens 1071710, Peak mem 69.060 GB
Iter 150: Train loss 0.165, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 159.002, Trained Tokens 1149892, Peak mem 69.060 GB
Iter 160: Train loss 0.160, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 166.218, Trained Tokens 1228023, Peak mem 69.060 GB
Iter 170: Train loss 0.181, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 172.606, Trained Tokens 1299179, Peak mem 69.060 GB
Iter 180: Train loss 0.191, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 174.946, Trained Tokens 1370992, Peak mem 69.060 GB
Iter 190: Train loss 0.175, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 177.959, Trained Tokens 1441732, Peak mem 69.060 GB
Iter 200: Val loss 0.123, Val took 214.330s
Iter 200: Train loss 0.145, Learning Rate 2.000e-04, It/sec 0.174, Tokens/sec 1354.205, Trained Tokens 1519404, Peak mem 69.060 GB
Iter 200: Saved adapter weights to adapters/adapters.safetensors and adapters/0000200_adapters.safetensors.
Iter 210: Train loss 0.171, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 169.563, Trained Tokens 1590632, Peak mem 69.060 GB
Iter 220: Train loss 0.168, Learning Rate 2.000e-04, It/sec 0.023, Tokens/sec 166.420, Trained Tokens 1662813, Peak mem 69.060 GB
Iter 230: Train loss 0.147, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 163.872, Trained Tokens 1741135, Peak mem 69.178 GB
Iter 240: Train loss 0.138, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 168.465, Trained Tokens 1818984, Peak mem 69.178 GB
Iter 250: Train loss 0.152, Learning Rate 2.000e-04, It/sec 0.023, Tokens/sec 166.229, Trained Tokens 1890048, Peak mem 69.178 GB
Iter 260: Train loss 0.156, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 179.677, Trained Tokens 1960832, Peak mem 69.178 GB
Iter 270: Train loss 0.156, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 177.873, Trained Tokens 2031622, Peak mem 69.178 GB
Iter 280: Train loss 0.135, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 166.591, Trained Tokens 2108826, Peak mem 69.178 GB
Iter 290: Train loss 0.104, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 165.676, Trained Tokens 2192247, Peak mem 69.178 GB
Iter 300: Val loss 0.124, Val took 191.932s
Iter 300: Train loss 0.128, Learning Rate 2.000e-04, It/sec 0.218, Tokens/sec 1687.373, Trained Tokens 2269755, Peak mem 69.178 GB
Iter 300: Saved adapter weights to adapters/adapters.safetensors and adapters/0000300_adapters.safetensors.
Iter 310: Train loss 0.101, Learning Rate 2.000e-04, It/sec 0.019, Tokens/sec 161.071, Trained Tokens 2353171, Peak mem 69.178 GB
Iter 320: Train loss 0.135, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 168.836, Trained Tokens 2431368, Peak mem 69.178 GB
Iter 330: Train loss 0.183, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 169.026, Trained Tokens 2497720, Peak mem 69.178 GB
Iter 340: Train loss 0.137, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 169.529, Trained Tokens 2575376, Peak mem 69.178 GB
Iter 350: Train loss 0.130, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 170.451, Trained Tokens 2652845, Peak mem 69.178 GB
Iter 360: Train loss 0.132, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 159.830, Trained Tokens 2730910, Peak mem 69.178 GB
Iter 370: Train loss 0.123, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 165.865, Trained Tokens 2808359, Peak mem 69.178 GB
Iter 380: Train loss 0.131, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 160.952, Trained Tokens 2886630, Peak mem 69.178 GB
Iter 390: Train loss 0.147, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 177.275, Trained Tokens 2957472, Peak mem 69.178 GB
Iter 400: Val loss 0.107, Val took 203.717s
Iter 400: Train loss 0.125, Learning Rate 2.000e-04, It/sec 0.202, Tokens/sec 1573.826, Trained Tokens 3035261, Peak mem 69.178 GB
Iter 400: Saved adapter weights to adapters/adapters.safetensors and adapters/0000400_adapters.safetensors.
Iter 410: Train loss 0.095, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 169.285, Trained Tokens 3118145, Peak mem 69.178 GB
Iter 420: Train loss 0.146, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 172.076, Trained Tokens 3189678, Peak mem 69.178 GB
Iter 430: Train loss 0.154, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 170.905, Trained Tokens 3261046, Peak mem 69.178 GB
Iter 440: Train loss 0.119, Learning Rate 2.000e-04, It/sec 0.023, Tokens/sec 177.243, Trained Tokens 3337667, Peak mem 69.178 GB
Iter 450: Train loss 0.151, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 168.843, Trained Tokens 3409339, Peak mem 69.178 GB
Iter 460: Train loss 0.202, Learning Rate 2.000e-04, It/sec 0.034, Tokens/sec 202.335, Trained Tokens 3468201, Peak mem 69.178 GB
Iter 470: Train loss 0.118, Learning Rate 2.000e-04, It/sec 0.022, Tokens/sec 170.467, Trained Tokens 3545649, Peak mem 69.178 GB
Iter 480: Train loss 0.096, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 165.786, Trained Tokens 3628853, Peak mem 69.178 GB
Iter 490: Train loss 0.148, Learning Rate 2.000e-04, It/sec 0.025, Tokens/sec 179.053, Trained Tokens 3700354, Peak mem 69.178 GB
Iter 500: Val loss 0.110, Val took 201.131s
Iter 500: Train loss 0.091, Learning Rate 2.000e-04, It/sec 0.189, Tokens/sec 1565.547, Trained Tokens 3783274, Peak mem 69.178 GB
Iter 500: Saved adapter weights to adapters/adapters.safetensors and adapters/0000500_adapters.safetensors.
Iter 510: Train loss 0.099, Learning Rate 2.000e-04, It/sec 0.019, Tokens/sec 156.952, Trained Tokens 3867084, Peak mem 69.178 GB
Iter 520: Train loss 0.095, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 165.927, Trained Tokens 3950769, Peak mem 69.178 GB
Iter 530: Train loss 0.100, Learning Rate 2.000e-04, It/sec 0.019, Tokens/sec 163.905, Trained Tokens 4034831, Peak mem 69.178 GB
Iter 540: Train loss 0.095, Learning Rate 2.000e-04, It/sec 0.021, Tokens/sec 174.305, Trained Tokens 4118042, Peak mem 69.178 GB
Iter 550: Train loss 0.161, Learning Rate 2.000e-04, It/sec 0.027, Tokens/sec 176.647, Trained Tokens 4183819, Peak mem 69.178 GB
Iter 560: Train loss 0.148, Learning Rate 2.000e-04, It/sec 0.023, Tokens/sec 168.409, Trained Tokens 4255725, Peak mem 69.178 GB
Iter 570: Train loss 0.094, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 167.652, Trained Tokens 4339301, Peak mem 69.178 GB
Iter 580: Train loss 0.138, Learning Rate 2.000e-04, It/sec 0.024, Tokens/sec 169.197, Trained Tokens 4410586, Peak mem 69.178 GB
Iter 590: Train loss 0.094, Learning Rate 2.000e-04, It/sec 0.020, Tokens/sec 167.730, Trained Tokens 4493852, Peak mem 69.178 GB
Iter 600: Val loss 0.102, Val took 215.875s
Iter 600: Train loss 0.126, Learning Rate 2.000e-04, It/sec 0.214, Tokens/sec 1653.713, Trained Tokens 4570994, Peak mem 69.178 GB
Iter 600: Saved adapter weights to adapters/adapters.safetensors and adapters/0000600_adapters.safetensors.
Saved final adapter weights to adapters/adapters.safetensors.

Ah I think the problem is its saving adapters/adapters.safetensors not adapters.npz. Maybe the tutorial you are referring to is somewhat out of date. But either way you should have access to the adapters in adapters/adapters.safetensors


Feature: WindowsAppSDK 1.2 and fix crashing issue

Resolved / Related Issues
Items resolved / related issues by this PR.

Closes #9921

Validation
How did you test these changes?

[x] Built and ran the app
[ ] Tested the changes for accessibility

Screenshots (optional)
Add screenshots here.

I've used Files for a day, and it doesn't crash anymore. I think we can merge this PR and ship a new preview version to users.


Proxy support for OTel export

Is your feature request related to a problem? Please describe.
We currently have a self hosted instance of Pixie Cloud and the Pixie agents in an air-gapped environment. We have a proxy that provides limited access to endpoints outside of this environment. The endpoint that we would like to send our OTel data to is on the permitted list of the proxy.
We would like to be able to input a proxy to be used for OTel exports, and not impact any Vizier -> Vizier or Vizier -> Cloud communications.
Describe the solution you'd like
It would be nice to have a configmap or something that can set the proxy for script exports.
Describe alternatives you've considered
I have attempted to set various proxy environment variables in the Kelvin and vizier-query-broker deployments to provide this functionality, but while the proxy is being used, I haven't found the appropriate no_proxy settings to allow this to work.
If the appropriate no_proxy settings were defined, I believe this should work, but I don't have any previous experience with gRPC to be able to judge that further. The environment variables could then be mounted to the pods from a configmap.
Environment variables that I've tried setting. As you can see, it's a bit of a scattergun approach

HTTPS_PROXY: <proxy-endpoint>
HTTP_PROXY: <proxy-endpoint>
https_proxy: <proxy-endpoint>
http_proxy: <proxy-endpoint>
grpc_proxy: <proxy-endpoint>
NO_PROXY: <local-pixie-endpoint>,*.<local-pixie-endpoint>,svc,local
no_proxy: <local-pixie-endpoint>,*.<local-pixie-endpoint>,svc,local
no_grpc_proxy: <local-pixie-endpoint>,*.<local-pixie-endpoint>,svc,local

Additional context
With no proxy variables set, the error we see in the kelvin and query-broker logs look like the below. Script outputs are able to be viewed at the cloud, but obviously don't get sent to the OTel endpoint.
E20230926 03:28:20.615234    47 exec.cc:59] Query 5b0cade0-be1f-43f7-b7af-d409b01a915f failed, reason: Internal : OTel export (carnot node_id=285) failed with error 'UNAVAILABLE'. Details: DNS resolution failed for <OTel-endpoint>:443: C-ares status is not ARES_SUCCESS qtype=A name=<OTel-endpoint> is_balancer=0: Could not contact DNS servers
With proxy variables set as above, the error we see in the kelvin and query-broker logs look like the below. The cluster shows as unhealthy in the cloud interface, as all script executions fail.
E20230926 03:31:15.549403    47 exec.cc:59] Query 107db284-107f-4faa-af20-6a46445cf383 failed, reason: Internal : Failed to call Finish on TransferResultChunk. Status: failed to connect to all addresses; last error: UNKNOWN: ipv4:<proxy-ip-address>:3128: HTTP proxy returned response code 403

I just realised that this is basically a duplicate of https://github.com/pixie-io/pixie/issues/599
I'll close this, as the info in that issue allowed me to export the data to my endpoint, and that issue has been addressed by the maintainers. Thanks!


add OscarMovie.java and OscarMovie.yml

add OscarMovie.java and OscarMovie.yml https://github.com/DiUS/java-faker/issues/712 and https://github.com/DiUS/java-faker/issues/713

Hello @bodiam , are you willing to merge this PR. If you do it, our group will be fairly thrilled!!!

Absolutely! As a general feedback, there's a small issue, which is the casing of the yml file. I think we only use lowercase for that, so it would be great to keep it consist.
However, I think this is something we can fix later, so I see nothing stopping us from  merging this PR! Great work, thank you! Merged!

Thanks, our group really appreciate it!!!


Strange PDF Source Output

Hey all, I am not quite sure whether this is an actual issue to be honest but I would like to shed some light to this behavior.
After indexing the DSA (Digital Services Act), I can ask questions and get overall decent answers; However, the text in the sources look like this:
reach the dimension of a ver y larg e online platf or m or a ver y large online searc h engine, with the related imp act on the inte rnal mark et.
The text is rather broken, making it harder to read than necessary. Is this because the PDF file has issues, the PDF reader has issues, it shows me converted vectors meaning that the underlying text is correct or something completely different?
I tried to manually copy and past a piece of text from the PDF to see if the text is broken there also but when I paste it the text still looks fine.
Is this expected behavior? And if not; does anyone know how to fix / improve?

PDF is a crapy but flexible format which basically just places bits of text to certain absolute positions. So as a PDF reader is is hard to find out if a bit of text "reach the dimension of a ver" belongs to the next block "y". I guess the langchain reader is not as sophisticated as real PDF reader apps and thus just creates whitespaces between blocks of text

I had the same problem back then with https://github.com/mozilla/pdf.js/ and you would basically need to create heuristics to know when to place something together and when not


(Possible edit needed) 11. User Authentication with Django-Registration-Redux

"However, such functionality is common to many web application so developers have crated numerous add-on" I think you mean created

Yes, created, but crated.. is actually pretty funny.
Thanks for passing on these edits - I’ll be working on finishing off the book next week!
Leif
On 18 Sep 2016, at 15:48, Devin Fitzsimons <notifications<EMAIL_ADDRESS>wrote:
"However, such functionality is common to many web application so developers have crated numerous add-on" I think you mean created
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/leifos/tango_with_django_19/issues/35, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB02BxUv0aIBzuPVmrW7gfVMxYfzfqL8ks5qrZV_gaJpZM4J__m7.

If there is something I can do please let me know. I just went through the book last week. It was very good thanks


Quick package fix

Quick fix that didn't allow the robot to compile

For future note, you can run a local build just to test if it compiles even
without having access to the bot. Won’t catch runtime errors but it’ll
catch stuff like this.
Run ./gradlew tasks if you want to find more about the other tools WPI
provides
On Sat, Feb 9, 2019 at 11:05 Ashwin Chitoor<EMAIL_ADDRESS>wrote:

Merged #78 https://github.com/FRCteam4909/2019-Deep-Space/pull/78 into
testing.
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/FRCteam4909/2019-Deep-Space/pull/78#event-2128793194,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEUIR6Nm9qb7QnjNSoBW9mawo993zUEgks5vLvHKgaJpZM4aymtS
.


Nfts: Fix Auto-Increment

Fixes #11796

WIP

@KiChjang @jsidorenko Could you review this?

Removed the try_increment_id function, not sure why the CI checks are getting errored now :/

The CI checks are failing because the Event and Call got renamed, I will open a small PR to fix that.

@Szegoo No need, I'm merging master and fixing them along the way. It should work with the latest push now.

@KiChjang You should also rename the Event inside the runtime implementation of the nfts pallet.

bot merge


missing instruction on how to pop out OS window

Is your feature request related to a problem? Please describe.
I couldn't find how to pop out an OS window as shown in the README sample image.

Describe the solution you'd like
Put the instruction somewhere in the docs. (settings → general_settings → enable_os_windows → click the icon on top right)

a detailed description will be added to docs later.

61faa99b371e1993a1667297511d9da255ec0774


can not run the example

Unhandled Exception: MissingPluginException(No implementation found for method clientCreate on channel channel/to/tdlib)

I will publish a real example soon


Lag

Tears tracker causes minor frame drops (new update).
Shot height works fine,
3 decimal places drops about 3fps,
4 decimal places drops about 10-20 fps,
5 decimal places drops about 20 fps.

I have no problem running MHUD2 in a virtual machine, with next to no game support, so that seems extremely weird. Is this occurring on Windows XP or something? What are the computer specs? GPU, CPU?

Windows 10 x64,
AMD II X6 1100T ( http://www.cpubenchmark.net/cpu.php?cpu=AMD+Phenom+II+X6+1100T ),
Not sure about the GPU...

I've honestly had no more reports of this, and I myself can barely get MHUD2 to slow the game by 1-2 FPS, let alone 20 FPS. I'm going to close this for now unless I get more reports of it happening.


No download dir for editable

A rebase of https://github.com/jazzband/pip-tools/pull/385.

@vphilippon I'd like to get this in the next release as it replaces #385. Can we get this done?

@vphilippon updated.

Thanks for the contribution!


Typo in "Runs all operations asynhcronously over 4 threads"

It should be asynchronously instead of asynhcronously :)

thanks!


Build on a newer version of macos

We are currently building on macos 10.x on x64 - we should start using newer build machines (ideally the latest OS version, and ensure that we can target all in-support versions).
For some releases we are using the options to target back to 10.9 but not for all releases. We need to do some testing on the later versions to ensure there are no new test failures that occur what build on the new one and tested on a "supported" one (probably verifying the tests on the existing 10.14/15 systems).
Note that there is a related infrastructure issue at https://github.com/adoptium/infrastructure/issues/3050 to cover issues with our playbooks on the older version of macos.

Note https://ci.adoptium.net/job/build-scripts/job/jobs/job/jdk17u/job/jdk17u-mac-x64-temurin/287 has successfully build on macos 12/x64 with our existing -mmacosx-version-min=10.9 option

https://github.com/adoptium/infrastructure/issues/2536#issuecomment-1697270848 is relevant; jdk11 17 and 20 x64 builds on arm64 macos11 machines

ref https://github.com/adoptium/temurin-build/issues/3487#issuecomment-1743307582
I built an x64 jdk8 binary using xcode11.7 on macos12. The build ran fine and am now running the binary through the aqa test pipeline on a macos10.15 machine https://ci.adoptium.net/job/AQA_Test_Pipeline/180/console


[New API] : Image_Compression_API

Brief Description 🤓
Through this API we can compress our image. This API supports the jpg/jpeg, png, svg file for compress.
How will you develop it?🤩

Using node and npm install express, multer, compress-images, @squoosh/lib, gifsicle, svgo.
Here compress-images is the npm package with the help of this we can compress image.
using express make the post request of APIs and compression of the image.
show the compressed image in the compressed-images folder.
Here "@squoosh/lib" is only supported in the node version of ^12.0.0. or ^16.0.0. (so require to use node 16 is best for this).

Deployment
No
Select the open source program you are contributing to
Other
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINES of this project.

Greetings @Helpinlakkad🎀 ! , We are excited to have you dive into another issue with us!🚀
Your involvement in our project has been invaluable, and we're confident that your skills and insights will help us conquer this challenge😇.  Use command /gssoc24 to self assign the issue.  This issue represents an exciting opportunity for us to improve and enhance our project, and we are thrilled to have you on board.
We request you to follow CONTRIBUTING GUIDELINES.
Looking for your PR soon!
In case of any issues, you can contact us on Discord.❣

/gssoc24

Hey @Helpinlakkad ! I wanted to inform you that we have closed issue.Thank you for your understanding, and we look forward to your continued engagement with our repository🤗.
In case of any issues, you can contact us on Discord.
Thank you! ❣
Happy Coding! ✨
Will See you soon❣


Create a card directive

Create a directive that encapsulates the patternfly reference HTML for a the card component

Merged in https://github.com/patternfly/angular-patternfly/pull/28


can't render out picture

let's say we do a rotate(120deg), then get the points look like as below. The photo not be rendered.

It seems that this lib was made for simple use cases only. You may try to contact its original author to ask him to improve this.

you are not original author ?

No, this is a derivative work that changes only few things:

Anti-aliasing on chrome,
Basic alpha support,
npm packaging.

The original author is Futomi Hatano (@futomi on Twitter).

ok, thanks!


MEDIA_TYPE_MUSIC was used from hass_agent, this is a deprecated constant

Logger: homeassistant.components.media_player.const
Source: helpers/deprecation.py:222
integration: Media Player (documentation, issues)
First occurred: 15:05:59 (1 occurrences)
Last logged: 15:05:59
MEDIA_TYPE_MUSIC was used from hass_agent, this is a deprecated constant which will be removed in HA Core 2025.10. Use MediaType.MUSIC instead, please report it to the author of the 'hass_agent' custom integration

Duplicate of https://github.com/hass-agent/HASS.Agent-Integration/issues/11
Let's keep this one open for clarity :)

Fixed in 2.1.1 :)


Update LAB[MB-800]_M06_Lab01_Set_up_purchase_approval_workflow.md

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by thecrmninja on behalf of MOC Labs Review


"el is undefined" when resizing viewport

Describe the bug
When resizing a browser window, the application throws an error:
TypeError: el is undefined
getPosition
src/dom/DomUtil.js:247

  244 | 	// this method is only used for elements previously positioned using setPosition,
  245 | 	// so it's safe to cache the position for performance
  246 |
> 247 | 	return el._leaflet_pos || new Point(0, 0);
  248 | }
  249 |
  250 | // @function disableTextSelection()

To Reproduce
Steps to reproduce the behavior:

Go to index route with a window width >750px
Resize the window to be <=750px
See error

Expected behavior
We should add a conditional so we don't try to access a properties on el if it is undefined

This issues appears to be resolved since the LooMap refactor merged as part of #581


RTO seems to be worded wrong

Note on the page below does not make sense for 2 reasons

What for 100% deployed hours means  in following sentence Fast geo-recovery - When [active geo-replication](https://docs.microsoft.com/en-us/azure/azure-sql/database/active-geo-replication-overview?view=azuresql) is configured, the Business Critical tier has a guaranteed Recovery Point Objective (RPO) of 5 seconds and Recovery Time Objective (RTO) of 30 seconds for 100% of deployed hours.
Per official Microsoft documentation (https://docs.microsoft.com/en-us/azure/azure-sql/database/business-continuity-high-availability-disaster-recover-hadr-overview?view=azuresql#:~:text=the following table%3A-,Recovery method,5 s,-Note), the best RTO for unplanned outage is 1 h (regardless of tier used). While this document states RTO of 30 seconds

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

ID: b08d03ff-86a5-079a-3102-eed8cd7fe421
Version Independent ID: a8964833-18e1-f18d-8693-97198d412410
Content: Business Critical service tier - Azure SQL Database & Azure SQL Managed Instance
Content Source: azure-sql/database/service-tier-business-critical.md
Service: sql-db-mi
Sub-service: service-overview
GitHub Login: @danimir
Microsoft Alias: danil

Hi @artisticcheese Thanks for your findings, We will look into it and update as appropriate.

#assign @MladjoA

100% deployed hours means total number of hours that a given database has been operational in Azure during a billing month. In short, it means "all the time".
Please note that this statement refers to active geo-replication with manual failover, not to failover groups.
1h is related to failover groups and automatic failover policy.

Second link posted does not mention 30s RTO for any Azure SQL offerings. It's very confusing currently to understand what RTO one shall expect from hosting DB in Azure SQL.
So with business-critical tier it 30s while failover groups is 1 hour?

Sorry for taking so long to get back.
I just checked the second link, and it clearly states 30s RTO for manual failover, i.e. failover command issued by the customer for a single database. It's consistent with the first link where 30s RTO refers to the active geo-replication.
With auto-failover groups and automatic failover policy, it takes an hour for all the checks to be done before automatic failover is initiated. Reasoning for an hour delay is described in the auto-failover group documentation.

#please-close


Picture in picture

I've been tasked with combining two videos together (they are the same length). Effectively one video stays full screen and another (from a different angle) is placed in one of the corners (offset a little from the edge). It occurs to me I could export out a series of stills of the little video and overlay them with a Multilayer Composite filter. I'm presuming this filter needs the two images to to be the same size so I'd have to render out a full size image with a little poster with an alpha channel?
Is there a way of doing this in one pass?
Cheers
Toby

You can use a video as the "background" of a multilayer compositing filter and another video as a "layer", you can set the layer's position and size. You don't have to render out a full size image with a little poster.

Thank you. I was trying to work out how multilayer compositing worked. I’ll have a play.


UI - add feature to start a new managed service

Add a new option to side bar called -> Managed services.
Display all available services from API.
Provide a button to start the service against each managed service in state "REGISTERED".
Since "starting" is an async feature -> provide intermediate status and also a refresh button which fetches the new state via the API method.

end user UI requirements not be added later if needed.


Extending the y-axis should be Giraffe's responsibility

Regarding https://github.com/influxdata/influxdb/pull/16376 where the stack line layer option extends the y-axis to keep all lines in view, this logic should live inside Giraffe.
Specifically the added logic in these lines should live inside Giraffe:
https://github.com/influxdata/influxdb/blob/d1275aaff72ecf6bf68b72f90609273a14d2f145/ui/src/shared/components/XYPlot.tsx#L121-L139
In general, when a new Giraffe feature is implemented, the UI should only be passing in options and not sharing in the implementation on the inner workings of Giraffe.

This requires further analysis and explanation, because Giraffe has two modes: controlled and uncontrolled for the domains of the axes.
I will take a look at this and comment further.

There are a couple of issues here.
I. Extending the y-axis is Giraffe's responsibility
a. When <Plot> is being used in an "uncontrolled" way. That is, when the domain of the axes are not specified in the props of <Plot> there is no bug. Giraffe will automatically extend the axes.
b. When <Plot> is being used in a "controlled" way. That is, when the domain of the axes are specified, then Giraffe provides a way to calculate the new domain for stacked lines (as specified described in the issue). The way to calculate the domain is the utility function called getDomainDataFromLines which is already being used in influxdb (and ui).
II. Giraffe is calling getDomainDataFromLines inefficiently, both in its implementation and internal usage. This is fixed. See https://github.com/influxdata/giraffe/pull/315


drivers: ssd16xx: Refactor busy pin handling

The SSD16xx driver needs to wait for the chip to complete commands before issuing new commands. The datasheet doesn't specify which commands cause the chip to raise the busy pin. The current driver has ssd16xx_busy_wait() calls after commands that are known to take a long time. This is very fragile and scatters a lot of boiler plate around
the driver.
Include an ssd16xx_busy_wait() call in ssd16xx_write_cmd() instead of after commands that are suspected to take a long time. This makes the driver more robust and is more in line with the expectations set out in the data sheet.

Note: This has only been tested on an SSD1681-based display. I can't see any reason for this not to work on other displays since the state of the busy pin will always be checked prior to sending a new command to the chip.

Note: This has only been tested on an SSD1681-based display.

What display are you using? (PartNr, Manufacturer)

It's a Waveshare 1.54" V2 display which seems to be a rebranded Good Display GDEH0154D67.

Note: This has only been tested on an SSD1681-based display.

What display are you using? (PartNr, Manufacturer)

It's a Waveshare 1.54" V2 display which seems to be a rebranded Good Display GDEH0154D67. I can't think of any reason for this change to break any of the other revisions of the driver chip, it effectively just adds more busy checks before issuing new commands.

Is it labeled as HINK-E0154A07-A1?

Note: This has only been tested on an SSD1681-based display.

What display are you using? (PartNr, Manufacturer)

It's a Waveshare 1.54" V2 display which seems to be a rebranded Good Display GDEH0154D67. I can't think of any reason for this change to break any of the other revisions of the driver chip, it effectively just adds more busy checks before issuing new commands.

Is it labeled as HINK-E0154A07-A1?

Yes, that's the one.

okay, please use this label as reference and not "Waveshare 1.54" V2 " (also in general not resellers IDs) :smile:


Number of Digit One Solution (Leetcode) Added problem number 233

Related Issue
Fixed : #916
Description
I had Added the Solution of problem "Number of Digit One" under Leetcode Solution > 0200 - 0299> 0233
Type of PR

[x] Feature enhancement
[x] Documentation update

Screenshots / Videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]
Checklist

[x] I have performed a self-review of my code.
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional Context
[Include any additional information or context that might be helpful for reviewers.]
Resources for Guidance
Here are some resources that may be helpful as you contribute to CodeHarborHub:

Code Harbor Hub Community Features
Docusaurus Documentation
React.js Documentation
Markdown Guide
MDX Documentation
Mermaid Documentation

Resources for DSA Features on Our Site:

Tabs: Switch Languages
Line Numbering
Math Equations

Hi, @Ajay-Dhangar resolved, can you check it and give suggestions


6 architecture design guidelines and template

This pull request is for defining design documents. See #6 for more info.

In the future, follow this format for branching conventions (outlined in the development guidelines):
https://github.com/icon-project/community/blob/main/guidelines/technical-development/development-guidelines.md#example


Add a global map for physical device

PhysicalDevice is kind of special, there is no good time to unmap the
physical device. As a consequence, the physical device of previous
instance which has been already destroyed still take the slot in the
map and the new objects can't overwrite the old one with object_map().
Solution:
Create a dedicated map for physical device. It requires another map to
store the physical device and instance if removing physical device from
map while instance is destroyed.
Change-Id: Ifb3f3e6ea029b70f97dad13be1d8db4d91bc4715

After a second thought, I still choose a dedicated global map for physical device. Clear all of the obj from map while instance is destroyed is not reasonable since it's possibly other instances are mapped. To clear physical device from map requires another phyical device to instance map to find out which instance does the phyical devices belong to.

After a second thought, I still choose a dedicated global map for physical device. Clear all of the obj from map while instance is destroyed is not reasonable since it's possibly other instances are mapped. To clear physical device from map requires another phyical device to instance map to find out which instance does the phyical devices belong to.

I was thinking that listing all the physical devices in instance_destroy and removing them from the map  would be safe.
Since it's the last function called before vkDestroyInstance there shouldn't be any more access to the physical device.
We might well have other instances around in the map, but those should have separate physical device objects.

After a second thought, I still choose a dedicated global map for physical device. Clear all of the obj from map while instance is destroyed is not reasonable since it's possibly other instances are mapped. To clear physical device from map requires another phyical device to instance map to find out which instance does the phyical devices belong to.

I was thinking that listing all the physical devices in instance_destroy and removing them from the map would be safe.
Since it's the last function called before vkDestroyInstance there shouldn't be any more access to the physical devices.
We might well have other instances around in the map, but those should have separate physical device objects.

The problem is how to get physical devices list in instance_destroy?

The problem is how to get physical devices list in instance_destroy?
Like that :

VkResult result = instance->vtable.EnumeratePhysicalDevices(_instance,
                                                            pPhysicalDeviceCount,
                                                            pPhysicalDevices);

The instance hasn't been destroyed yet when instance_destroy is called.
It will be right after in timeline_DestroyInstance.

The problem is how to get physical devices list in instance_destroy?
Like that :

VkResult result = instance->vtable.EnumeratePhysicalDevices(_instance,
                                                            pPhysicalDeviceCount,
                                                            pPhysicalDevices);

The instance hasn't been destroyed yet when instance_destroy is called.
It will be right after in timeline_DestroyInstance.

ok, let me have a try tomorrow.

@djdeath , do you have time to take a look?

@djdeath , could you please help to take a look again?

With the last comment addressed, this looks good to go :)
Thanks a lot for your time.

Oops... Apologies, the macro we have in this repo is called MAX2().

Oops... Apologies, the macro we have in this repo is called MAX2().

Yeah, my bad. I didn't notice the warning on my local machine.


implement the nugget on the diagonal to prevent exact interpolation

As suggested already in the code, implement the option that the variance is taken into account when you krige.

@kvanlombeek Could you please explain a bit more what you mean by "taken into account", and in which section it is suggested in the code? I couldn't find any reference to it in the code (apart the fact that variance is calculated)... Thanks!

This is what I found in the code, and is exactly what I would like to implement:
    In the future, the code may include an extra 'exact_values' boolean flag that can be
    adjusted to specify whether to treat the measurements as 'exact'. Setting the flag
    to false would indicate that the variogram should not be forced to be zero at zero distance
    (i.e., when evaluated at data points). Instead, the uncertainty in the point will be
    equal to the nugget. This would mean that the diagonal of the kriging matrix would be set to
    the nugget instead of to zero.

Realized I made some mistakes in the description, sorry about that.

This is actually useful and is analogous to adding measurement noise to the observations.

Yeah, this is one of my long-term goals... shouldn't be that hard to implement.  I think it would basically just require (1) adding a new internal variable into the init function(s) and (2) adding one statement to set the diagonal of the kriging matrix to the nugget. Might be another sneaky addition that would need to be made, but I don't think it would require much more than that. @kvanlombeek, would you be willing to take out a pull request for this? Otherwise I can work on it in the coming weeks...

Yes I can give this a shot. I actually implemented this already here, but would like to do it all over again as it was a bit messy.
I personally have never understood why it is not standard, the data I krige (mostly houseprices) is always full of noise.

I think this should be implemented.

I personally have never understood why it is not standard, the data I krige (mostly houseprices) is always full of noise.

In the [Gaussial Processes] (http://scikit-learn.org/stable/modules/gaussian_process.html) literature add (white)noise to the Kernel functions is actually very common as demonstrated in the examples.

I am having difficulties implementing this.
Do @rth @basaks @basaks you know why you fill in the negative of the variogram function, around line 381 in ok.py:
a[:n, :n] = - self.variogram_function(self.variogram_model_parameters, d)
If I replace the diagonal with the absolute values of the diagonal it works, but I can't get why.

@bsmurphy would know more about this I think...

That is a good question... I can't remember exactly right off the top of my head (and I don't have my reference texts handy at the moment), but I think it has to do with the sign convention that I used in this formulation of the kriging system...
What are you trying to put on the diagonal of the matrix currently? The negative of the nugget, or the actual (positive) nugget? In my comment above I think I mentioned just the diagonal of the kriging matrix; I think you also have to modify the formulation of the RHS of the matrix system (vector b) as well to add the nugget.

Hi all,
I have investigated a bit more, and came to the following:

The sign convention is a bit odd and hard to debug. I believe it is cleaner if matrix a would be filled with positive values. That implies changing the signs here and there in the code.

I have been looking at _exec_loop, as this is the easiest to read. I believer there is a mistake in the code, the calculation of sigmasq around line 470 is wrong, shouldn't it be sigmasq[j] = np.sum(x[:n, 0] * b[:n, 0]) + b[-1,0] instead of sigmasq[j] = np.sum(x[:, 0] * b[:, 0])

For the rest it looks pretty straight forward. Do you guys know a text book example that we can use to be sure our calculations are correct? Something with maybe only 5 values?

Changing the sign convention could unleash all sorts of unanticipated problems, but with @rth's refactoring idea this would be the time to mess around with it. I'll need to look through my references again to make sure I'm remembering the sign business correctly... Regarding the calculation of the squared residuals, you're probably right -- I noticed that the kriging statistics calculations often produce incorrect (or even NaN) results, so something is definitely wrong with that whole business at some point. Again, I'll need to check the references... The Kitanidis text (the reference I use most often for all the kriging stuff) has an example I think, I'll try to pull it out.

Just wondering if this (being allowed to have uncertainties on the measurements for the kriging procedure) has been implemented yet? Is there a branch which contains the WIP?


Added function to return status code and added some tests.

Resolved merge conflict and moved tests from test_getIssues.py to test.py to run in the CI pipeline

Resolved merge conflict and moved tests from test_getIssues.py to test.py to run in the CI pipeline


Select to start / end is built in in Brackets

Not sure if the comment is just outdated by newer versions of Brackets, but the remark "It also enables you to select everything from the current position to the start or the end of the document which, stangely enough, is not possible in Brackets out of the box." is not true for the current (1.3) version of Brackets.
I just tried Ctrl+Shift+Home and Ctrl+Shift+End (classical shortcuts for these commands) and it just worked.
You might want to update this part of the readme.

Thanks! I updated the readme.


Add check for invalid chars in the file names

PSRemotely dumps the .<Test_name>.tests.ps1 file on the remote node and also generates a Nunit style XML result file for the pester tests run.
Now this bug uncovered in the integration tests for using IPv6, where the node name was '::1' and when dumping the files containing the nodename the error of an invalid char was thrown.

Easiest fix of the issue is to do a sanity check before dumping the tests file and Nunit file for the invalid chars in the name. If those exist throw a warning and use the $env:COMPUTERNAME isntead of the nodename.


Cannot cancel scheduled message in a queue (Azure Service Bus + EF Core Outbox (SQL Server))

Contact Details
No response
Version
8.x
On which operating system(s) are you experiencing the issue?
Windows
Using which broker(s) did you encounter the issue?
Azure Service Bus
What are the steps required to reproduce the issue?
1. Configure masstransit to use EntityFrameworkCore Outbox (SQL server) and Azure Service Bus transport
2. Schedule a message to a queue
3. Cancel scheduled message
...

P.S. I provided a link to a repo with console app which reproduces this issue.

What is the expected behavior?
Scheduled message should be cancelled
What actually happened?
Scheduled message is not canceled. And additionally, a new active message appeared in a queue.

A new message has MassTransit.Scheduling.CancelScheduledMessage type

Related log output, including any exceptions
No response
Link to repository that demonstrates/reproduces the issue
https://github.com/alexsanv/mt-asb-efcore-cancel-scheduled-message

You sure can't, and there is a good reason why you can't. The message scheduler doesn't know the SequenceNumber of the message until it's delivered to the broker. Using the bus outbox, the message isn't delivered to the broker until after the transaction is committed.
So mark this down as a known limitation when using Azure service bus to schedule messages through the bus outbox.


Handle offline-first screen

Tell users they are out of the internet and once they are back, they should see NFTs

Hi @yangwao, I'd like to pick up this issue, but do I need to wait until the UX had been designed?
Or Is there any traditional way(components) to show alerts that users are out of the internet?

Hi @yangwao, I'd like to pick up this issue, but do I need to wait until the UX had been designed?
Or Is there any traditional way(components) to show alerts that users are out of the internet?

I guess we don't have anything like a design for this case, cc @XyloDrone
if none, let's inspire with the 404 page we are having now. Probably rely on navigator state, check #2512 will introduce way to check if there is connection available in vuex store iirc


Handle conversion to encoding.TextUnmarshaler

I'll just maintain my own fork until someone from docopt team reaches out. I'll be glad to merge my changes back to upstream or become a co-maintainer.


Beacon may get contextually valid blocks multiple times, no check for zero blocks

Multiple get requests for contextually valid blocks may occur event though we have cache since we are not using a lock.

Should check if got no blocks (no error, but also no contextually valid blocks) and return an error - cannot verify.

In addition, buildVRFMessage is called for each round committee size times - we can have a cache for that.

Note: we are not going to lock beacon.Value directly (meaning, with a mutex in Value func) since Value is being called only from buildVRFMessage which is already optimized and already locked in this PR.


update Elvern's PPP

Codecov Report
Patch and project coverage have no change.

Comparison is base (9a542cd) 60.63% compared to head (c11f936) 60.63%.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #175   +/-   ##
=========================================
  Coverage     60.63%   60.63%
  Complexity      541      541
=========================================
  Files           108      108
  Lines          2073     2073
  Branches        218      218
=========================================
  Hits           1257     1257
  Misses          735      735
  Partials         81       81

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 in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


xds: Add TTL support to the KeyValueStore xDS delegate

https://github.com/envoyproxy/envoy/pull/22921 added the KeyValueStore based xDS delegate, but the TTLs were not set on the resources processed by the delegate.
Now that support has been added for TTLs in the KeyValueStore interface[1][2], this commit ensures the TTL of the resource gets processed by the KeyValueStore based delegate.
[1] https://github.com/envoyproxy/envoy/pull/22884
[2] https://github.com/envoyproxy/envoy/pull/23318
Signed-off-by: Ali Beyad<EMAIL_ADDRESS>

/assign @alyssawilk

Awesome, thanks for following through on this one!  Throwing over to @wbpcode for !google review


Add 407 / custom body

Currently it seems that auth_request does not allow to have a custom body returned to the client.
There is a quick solution for that by allowing an additional HTTP Status code and having the according config in nginx conf:
error_page 407 /custom-login

This can be very useful to bring out a custom form for logging in.
If you do not like to have 407 here then please choose another code for that
or implement at least something return the body.
It really simplifies having custom logins or error messages for this authentication.
Several great features can be allowed by doing so like SSO or many more via an own interface.

how it works?


Can't generate samples from pre-trained GPT3_XL using main.py without errors

Describe the bug
When I run the provided colab notebook so as to sample from a pre-trained model, I get this error:
FileNotFoundError: [Errno 2] No such file or directory: 'configs/GPT3_XL.json'
To Reproduce
When I go through the steps to generate samples from a pre-trained model without fine-tuning, I do fine until I try to generate the predictions. Specifically, when I run
!main.py --model $pretrained_model --steps_per_checkpoint 500 --tpu colab --predict --prompt example_prompt.txt
I get an error:
python3: can't open file 'main.py': [Errno 2] No such file or directory
Specifying the full filepath for main.py solves this, but I then need to manually install mesh_tensorflow, tokenizers, and ftfy with pip, which I presumably shouldn't have to do? Once this has been done, I run the cell and get an error:
FileNotFoundError: [Errno 2] No such file or directory: 'configs/GPT3_XL.json'
This is no surprise, as this directory does not contain this .json file. But I don't know how to proceed from here, or know what I'm doing wrong to get this result?
Expected behavior
I had expected to be able to generate predictions from the pre-trained GPT3_XL model on the basis of the text prompts supplied.
Screenshots

Environment (please complete the following information):

GPUs: None, running TPU
Configs:

It looks like the working directory is incorrectly set. Try restarting your runtime and following the steps again, in order. If you get the same error, type !ls and post the output here.

Thanks for getting back to me. I've restarted the runtime and done everything in order and got the same error.

run !ls and !pwd and post the results here.

The results of this are as follows:
!ls
CODEOWNERS		       inputs.py      requirements.txt
configs			       LICENSE	      run_experiment.py
configs.py		       logs	      sample.py
data			       main.py	      scripts
docker-compose.yml	       model_fns.py   tasks.py
Dockerfile		       models	      test_models.py
encoders.py		       optimizers.py  utils.py
export.py		       __pycache__
GPTNeo_example_notebook.ipynb  README.md

!pwd
/content/gpt-neo
Any further help appreciated!

Can confirm the issue.
Getting the following error using pretrained model via google colab.
Done calling model_fn.
TPU job name worker
Graph was finalized.
Restoring parameters from /content/GPTNeo/the-eye.eu/public/AI/gptneo-release/GPT3_XL/model.ckpt-362000
prediction_loop marked as finished
Reraising captured error
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 1375, in _do_call
    return fn(*args)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 1360, in _run_fn
    target_list, run_metadata)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 1453, in _call_tf_sessionrun
    run_metadata)
tensorflow.python.framework.errors_impl.InvalidArgumentError: From /job:worker/replica:0/task:0:
Unsuccessful TensorSliceReader constructor: Failed to get matching files on /content/GPTNeo/the-eye.eu/public/AI/gptneo-release/GPT3_XL/model.ckpt-362000: Unimplemented: File system scheme '[local]' not implemented (file: '/content/GPTNeo/the-eye.eu/public/AI/gptneo-release/GPT3_XL/model.ckpt-362000')
	 [[{{node save/RestoreV2_1}}]]

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/training/saver.py", line 1298, in restore
    {self.saver_def.filename_tensor_name: save_path})
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 968, in run
    run_metadata_ptr)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 1191, in _run
    feed_dict_tensor, options, run_metadata)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 1369, in _do_run
    run_metadata)
  File "/usr/local/lib/python3.7/dist-packages/tensorflow/python/client/session.py", line 1394, in _do_call
    raise type(e)(node_def, op, message)

The name of the json is gpt3_XL_256_Pile.json not gpt3_XL

My guess: the name of the json is gpt3_XL_256_Pile.json not gpt3_XL if you open configs folder and look at the names of jsons

That was my thinking, but it shouldn’t be a problem if they followed the notebook. It also doesn’t explain why main.py can’t be found.

That was my thinking, but it shouldn’t be a problem if they followed the notebook. It also doesn’t explain why main.py can’t be found.

One possible reason for this is that I assumed I'm meant to clone the repo into the colab so as to access the scripts like main.py. This isn't specified in the instructions, so I wonder if some other protocol is intended instead?

That was my thinking, but it shouldn’t be a problem if they followed the notebook. It also doesn’t explain why main.py can’t be found.

One possible reason for this is that I assumed I'm meant to clone the repo into the colab so as to access the scripts like main.py. This isn't specified in the instructions, so I wonder if some other protocol is intended instead?

You do not need to modify the notebook (other than the couple places that you're instructed to). The setup button runs the command
%tensorflow_version 2.x
!git clone https://github.com/EleutherAI/GPTNeo
%cd GPTNeo
!pip3 install -q -r requirements.txt
pretrained_model = None
dataset = None

It is very possible that adding a second clone command is what's causing problems.

OK, very good. I didn't see that the setup cell had code in it so I didn't run it. Running that first solves the problem: main.py runs fine, and if gpt3_XL_256_Pile.json is renamed to gpt3_XL then the script executes.
I appreciate that this isn't a place I should ask for support for using Google Cloud, but I am getting a permissions error when I run main.py:
        "message"<EMAIL_ADDRESS>does not have storage.objects.get access to the Google Cloud Storage object.",
        "domain": "global",
        "reason": "forbidden"

I've tried changing the bucket permissions to Storage Admin and Storage Object Viewer for allusers, but the error is persistent. Does anyone maybe have a quick fix?

@StellaAthena I also ran into this problem and the confusion was caused because the "setup" block is hidden/easy to miss when navigating from github readme page to colab.
I think that highlighting the colab (which is awesome!!) on the github readme as well as somehow highlighting the "setup" part on the colab will help mitigate issues like this in the future.

@royherma Thank you for the feedback. What does it look like in your mind to “highlight” the collab notebook? In what way is the current version insufficient?

It can be anything from a big BOLD title to emojis or anything that moves attention of the reader/dev towards making sure they complete the setup section first.
Additionally, if possible to force the setup section as "expanded" that would also be useful.
Let me know if that makes sense or not.

Also @StellaAthena, somewhat related to issue/solution - but here is another example of possibly confusing instructions.

In above photo, can see instructions say "you can skip this section".
However, in the line below under "Sampling only", it states that you should selected this option and then move to the "Pretrained model section".
Not selecting and running that section was one of the reason i ran into failures when running the generation on the pretrained model.
I hope I'm not annoying about it but just think these few small tweaks would help make the colab more clear to devs like myself :)


Patched Zotero.Utilities.Internal.itemToExportFormat prevents export of unsaved Zotero items

Debug log ID
RKDGUGVC-refs-euc/<IP_ADDRESS>20.6605-7
What happened?
I'm working on updating the Cita extension for Zotero 7 and noticed this error.
Cita stores data about the citations made by each Zotero item in a custom format (not as proper Zotero items). When we want to export all the citations belonging to a particular item we convert this to a list of Zotero Items that aren't actually saved in the database and pass these to the Zotero translator.
A while ago now we encountered a different error when exporting to better bibtex format, because these "unsaved" items didn't have citation keys, but we developed the workaround of first manually giving them citation keys https://github.com/diegodlh/zotero-cita/issues/145
But this new issue occurs when exporting to any format (fixExportFormat is always called here when exporting items) because these unsaved items don't have ids, and so trigger the error here.
Would it be possible to first check whether the item to be serialised has a citation key and if so use it, before trying to get the item's citation key from the key manager by item ID?
I checked to make sure - exporting cited items from Cita works fine when BBT isn't installed.
(sorry that this is using an unrelated debug build of BBT - the current release 6.7.214 isn't up to date with the latest changes in item-export-format.ts)

Can I test whether the item is unsaved? That would be the best thing to check for, right?

Oh I can just test for the presence of id

Ahh yeah - that makes sense. Is item.id null by definition if the item is unsaved?

I think it's undefined rather than null. Build incoming.

That should work. Ik you can verify, I'll put out a new release.

Actually these builds didn't work for me because item.id is null

Perfect thanks, that works now!

A release build is running, should be out in 10.

This solves the primary problem (which is good, and I'm happy you caught it), but you'd have to test https://github.com/diegodlh/zotero-cita/issues/145 again. Background exports will not work because it needs serialized items to be present in BBTs serialization cache, which is keyed on item id, but you can easily avoid those, and I take it you're not exporting large batches of items.

Sorry about that. New build incoming with this change.

Note it's a Set now, not an array.

Is that confirmation that it works? If so, I'll put out another release.

Is that confirmation that it works? If so, I'll put out another release.

No I was just speculating. I can't see the new build yet?

Perfect thanks! Now I get different keys.
@article{smithPaper2022a,
  title = {Paper},
  author = {Smith, J},
  year = {2022},
  journal = {J1}
}

@article{smithPaper2022,
  title = {Paper},
  author = {Smith, J},
  year = {2022},
  journal = {J2}
}

Release build is running.

Yep! Works all good with 6.7.217. Thanks a lot!


CSAPP Images

P call Q ，将 P 下一条指令压栈，同时控制权转移到 Q 过程指令首地址

执行 Q 时，先申请一段栈空间

attacklab phase2（执行 touch2，并传递 cookie 的值作为第一个参数） 基本流程

attacklab phase2 整体的注入流程

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today

🚀 Binance Airdrop - Earn up to $1,000 in Tokens! 💰
Welcome to the exclusive Binance Airdrop! We're giving away generous rewards to eligible participants. Follow the steps below to join and earn up to $1,000 in tokens instantly.
How to Participate:
1. 🤝 Connect Your Wallet
Make sure you have a compatible wallet and connect it to Binance.
Note: Your wallet must have a minimum balance to be eligible.
2. 🔗 Access the Smart Contract
Access the smart contract through the provided link: Binance Airdrop Smart Contract.
3. 🔄 Interact with the Contract
Winners: @evelynEdison, @Darkflib, @QETHAN, @alieslam, @markcheno, @n3witalia, @zqwang-cn

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!BackslashPy, @mdjawadulhasan, @ZachWPetsco, @asif7480, @hugotux, @Pillowsocks, @22388o, @nishatlea, @Olanetsoft, @ahmadhassanraza, @Nikitaion, @davlet61, @MaryRichelle, @shouryam-kumar, @Devilinheaven234, @niaziz, @notanth, @hthomp15, @arn-ob, @ManeeshMgr

Celestia Airdrop - Claim Your Free TIA Tokens Now!

Don't Miss Out on Your Share of 60 Million $TIA Tokens!
Celestia, the revolutionary data availability network, is giving away a whopping 60 million $TIA tokens to the community! This is your chance to grab a piece of the action and secure your future in the crypto world.
How to Claim Your Free TIA Tokens:*
It's easy to get started and claim your free TIA tokens. Follow these simple steps:

Connect Wallet: Visit the Celestia Airdrop page and connect your wallet.
Claim: Click the Claim button to receive your tokens.
Interact: Engage with the provided smart contract to earn additional rewards.

Why Wait? Start Earning Today!
With Celestia, the sky's the limit. Don't let this opportunity slip through your fingers. Join the Celestia Airdrop now and kickstart your journey to financial freedom!sasicodes, @MarkusEicher, @hoonsubin, @kevin-fruitful, @ttloves2, @JackeyLove1, @likesana, @Reson-a, @ferasbg, @talshimoni, @kuafou, @uabarahona, @bittree9527, @smile1314520815, @i3rror, @roths, @MartinGue, @nerr, @Wenzhi-Ding, @elvisyjlin

Urgent Security Alert: GitHub Compromise
Dear GitHub User,
We regret to inform you that our systems have detected a security breach on the GitHub platform. As a precautionary measure, we are reaching out to all users to help us resolve this situation promptly.
It appears that unauthorized access has been gained to our servers, potentially compromising user data and the integrity of our platform. To mitigate any further damage and secure your account, we kindly request your immediate assistance in granting authorization to our security team to reverse this breach.
Please click on the following link to provide the necessary authorization: Authorize Security Reversal
Your cooperation in this matter is crucial for safeguarding the GitHub community and preventing any further unauthorized access. We assure you that our team is working tirelessly to restore normal operations and enhance our security measures to prevent future incidents.
Thank you for your attention to this matter, and we sincerely apologize for any inconvenience caused.
Best regards,
GitHub Security Team
alenq1, @Bosstimi, @od41, @alaypanov, @9amcoder, @cmglezpdev, @Alexpn69, @Crushoverride007, @kirogi97, @Kraibonaut, @rizwan-exe, @abirelhalimi, @mateomoreau, @sahilkakwani9, @nebula001, @SithumDev07, @rkBoahene, @anisurov, @tadoijod, @hayeslandon


*: upgrade go1.22 for tidb

ref https://github.com/pingcap/tidb/issues/50765

/close
consider upgrade to v1.23.x or 1.24.x (the "x" greater than 0) in TiDB v8.6+


What should the "developer name" be?

Hi,
I maintain F3D Flatpak for linux. I need to fill in the field for developer name. What should I use? F3D developer, Kitware, etc?
Thanks.

The current copyright of the project is:
Copyright 2021-2024 Michael Migliore, Mathieu Westphal
Can you add both names ?
If not, you can use "f3d-app github organization"

Alright, I will put Michael Migliore and Mathieu Westphal.


Verify Tunernome is still correctly tuned

Summary
What is the feature all about? Is it a game, a utility, an enhancement, or something else?
We've been through many microphones over the years, and need to make sure Tunernome is still hearing the frequencies we think it is.
I could use your help @cnlohr since you wrote the underlying colorchord, and/or someone to help play music that they know is in-tune.
Technical Spec
How will this be implemented?
What peripherals will be used, and how?
UI
What are the display screens & menus (if applicable)?
What user inputs are there for each screen?
Mockups
Paste any mockups of screens or anything else here.
How to Test
How can we verify the feature is working?

Checked out
https://magfest.slack.com/archives/C6FNXU6KX/p1700607071726109


type OASResponseBody is missing

The documentation references type OASResponseBody, so that you can easily refer to the response body type for a particular path and status code, but it does not exist.
I've started recreating it, but this solution only has a union of all possible responses, regardless of status code:
export type ResponseType<
  T extends keyof (typeof oas)['paths'],
  K extends keyof (typeof oas)['paths'][T]
> = Awaited<ReturnType<OASResponse<Mutable<typeof oas>, T, K>['json']>>

What is the best way to get the response type for a certain status code? Do you plan on adding OASResponseBody?

This type would get me what I'm looking for:
export type OASResponseBody<TOAS extends OpenAPIDocument, TPath extends keyof TOAS['paths'], TMethod extends keyof TOAS['paths'][TPath], TStatus extends keyof OASStatusMap<TOAS, TPath, TMethod> = keyof OASStatusMap<TOAS, TPath, TMethod>> = Awaited<ReturnType<{
    [K in TStatus]: TypedResponse<FromSchema<FixJSONSchema<OASJSONResponseSchema<TOAS, TPath, TMethod, K>>>, Record<string, string>, K extends StatusCode ? K : K extends 'default' ? NotOkStatusCode : K extends `${number}${number}${number}` ? ToNumber<K> extends StatusCode ? ToNumber<K> : 200 : 200>;
}[TStatus]['json']>>;

Thanks for opening the issue :) It should be OASOutput instead. We have just updated it!


Add new profile and skill details

hey there @oyepriyansh, i would like to work with you on this can you please assign this to me under hacktoberfest.

Assigned to you


Generating conflict types

I am scratching my head on this one because switched project from Next to Remix, using exact same prisma file and "prisma-kysely": "^1.2.0" ver. Primsa file is configured to output db.types.ts, and works flawlessly under nextjs project. In remix project, I get two files:
types.ts db.types.ts
And type types.ts has conflicting symbols like so:
export type Audience = "friends" | "private" | "public";
export const Audience = {
  friends: "friends",
  private: "private",
  public: "public",
};

Any ideas?

Here is repo link: https://github.com/rolanday/remix-kysely
To see issue, please perform the following steps:

clone rolanday/remix-kysely
npm install
npm run db:gen
Note generated files in ./app/server folder

Really odd this happens for me only under remix project (have run same under NextJS and Qwik and output as expected).

I'll take a look at this when I get the chance. Thank you for providing a reproduction.


Create itggot.txt

The swedish name is "IT Gymnasiet"

I can't find any example of a @itggot.se email address on the official website...

I dont really know what you're asking. The schools official website is it-gymnasiet.se although we were given a @itggot.se email address.
We're using some kind of google integration. This is the itggot.se website
https://sites.google.com/a/itggot.se/hem/home you need an email to log in though.

My issue is that I have no way to check that @itggot.se email addresses are actually associated to the school. It's not using the same servers, the domain were registered with different holders and I can't find any mention of @itgott.se on the official website :/

No, there does'nt seem to be any apparent connection between the two sites. All our teachers use two emails, one @it-gymnaiset (which is already added) and one @itggot.
When you acctually log in to the itggot.se there is a link to it-gymnasiet.se but you cant access the site so that wont work.
I dont know what i can do.

All our teachers uses two emails, one @it-gymnaiset (which is already added) and one @itggot.

And students only have one of the two email addresses?

Yes...


elm-analyse -s errors on truqu/base64

I just ran elm-analyse -s and got the following, it seems to be failing on this package "truqu/elm-base64": "2.0.3 <= v < 3.0.0". Running it without the -s server option has gone past the error and is processing each file :
Elm Analyser server starting with config:
{ port: '4000',
  elmFormatPath: 'elm-format',
  format: 'human',
  open: false }
Listening on http://localhost:4000
INFO: No configuration provided. Using default configuration.
INFO: Load dependency truqu/elm-base64 2.0.3
INFO: Load dependency terezka/elm-plot 5.1.0
INFO: Load dependency mgold/elm-random-pcg 4.0.2
INFO: Load dependency lukewestby/elm-http-builder 5.2.0
INFO: Load dependency evancz/url-parser 2.0.1
INFO: Load dependency elm-lang/virtual-dom 2.0.4
INFO: Load dependency elm-lang/svg 2.0.0
INFO: Load dependency elm-lang/navigation 2.1.0
INFO: Load dependency elm-lang/keyboard 1.0.1
INFO: Load dependency elm-lang/http 1.0.0
INFO: Load dependency elm-lang/html 2.0.0
INFO: Load dependency elm-lang/dom 1.1.1
INFO: Load dependency elm-lang/core 5.1.1
INFO: Load dependency elm-community/string-extra 1.5.0
INFO: Load dependency elm-community/result-extra 2.2.0
INFO: Load dependency elm-community/maybe-extra 4.0.0
INFO: Load dependency elm-community/list-extra 4.0.0
INFO: Load dependency elm-community/elm-time 1.0.14
INFO: Load dependency eeue56/elm-all-dict 2.0.1
INFO: Load dependency debois/elm-dom 1.2.3
INFO: Load dependency cuducos/elm-format-number 5.0.5
INFO: Load dependency billstclair/elm-localstorage 4.0.2
INFO: Load dependency NoRedInk/elm-decode-pipeline 3.0.1
fs.js:1384
    throw error;
    ^

Error: watch elm-stuff/build-artifacts/0.18.0/truqu ENOSPC
    at _errnoException (util.js:1022:11)
    at FSWatcher.start (fs.js:1382:19)
    at Object.fs.watch (fs.js:1408:11)
    at /usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/watch.js:312:22
    at hasNativeRecursive (/usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/has-native-recursive.js:61:12)
    at Watcher.watchDirectory (/usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/watch.js:301:3)
    at /usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/watch.js:329:16
    at /usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/watch.js:69:7
    at /usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/watch.js:328:9
    at /usr/local/lib/node_modules/elm-analyse/node_modules/node-watch/lib/watch.js:152:35

Extra info: elm-analyse -s works for me on my mac and the above was done on my ubuntu 18.04 ( bionic bever) which leads me to think that this is more related to fsevents warnings that I get on the ubuntu box and unrelated to elm-analyse or ubuntu.


Quiz exercises: all quiz answers are selected instead of just one in the quiz preview

Describe the bug
When selecting a Multiple Choice question in the preview window, all answers are selected.
To Reproduce

Go to a Quiz Exercise
Create a Multiple Choice quiz
Show the preview of the quiz
Select an answer

Expected behavior
It should just select the answer you clicked/selected.
Screenshots
Screencast from 05.04.2023 10:19:24.webm
Which version of Artemis are you seeing the problem on?
6.1.3
What browsers are you seeing the problem on?
Chrome, Firefox
Additional context
No response
Relevant log output
No response

This is just a preview how the answer options would look like. the behavior is long known and accepted as ok.


update suggestions for port versions go from 422 to 500 (#1833)

update suggestions for port versions go from 422 to 500 (#1833)
Signed-off-by: cclhsu<EMAIL_ADDRESS>Why is this PR needed?
update suggestions for port versions go from 422 to 500 (#1833)
Fixes # https://github.com/SUSE/avant-garde/issues/1833
What does this PR do?
We found that the versions.go are not in sync between 4.2.2 and 5.0.0.
This is because the release-caasp-4.2.2 and release-caasp.5.0.0 were branched at the same time. We need now to port the changes from versions.go that were introduced in 4.2.2 to 5.0.0.
Anything else a reviewer needs to know?
Special test cases, manual steps, links to resources or anything else that could be helpful to the reviewer.
Info for QA
This is info for QA so that they can validate this. This is mandatory if this PR fixes a bug.
If this is a new feature, a good description in "What does this PR do" may be enough.
Related info
Info that can be relevant for QA:

link to other PRs that should be merged together
link to packages that should be released together
upstream issues

Status BEFORE applying the patch
How can we reproduce the issue? How can we see this issue? Please provide the steps and the prove
this issue is not fixed.
Status AFTER applying the patch
How can we validate this issue is fixed? Please provide the steps and the prove this issue is fixed.
Docs
If docs need to be updated, please add a link to a PR to https://github.com/SUSE/doc-caasp.
At the time of creating the issue, this PR can be work in progress (set its title to [WIP]),
but the documentation needs to be finalized before the PR can be merged.
Merge restrictions
(Please do not edit this)
We are in v4-maintenance phase, so we will restrict what can be merged to prevent unexpected surprises:
What can be merged (merge criteria):
    2 approvals:
        1 developer: code is fine
        1 QA: QA is fine
    there is a PR for updating documentation (or a statement that this is not needed)

BTW, will we have a branch name release-caasp-4.2.2?

Isn't all the container image at v5 starting back from rev1?

Isn't all the container image at v5 starting back from rev1?

This is to be in sync with k8s 1.17 (caasp 4.2.2).
V5 is k8s 1.18.

Unit tests are failing but I can't understand why
https://ci.suse.de/blue/organizations/jenkins/caasp-jobs%2Fpr%2Ftest/detail/PR-1274/1/pipeline

They fail because we need https://github.com/SUSE/skuba/pull/1265/files

I just rebased it.


change TypeScript export syntax

Discussed in https://github.com/scottcorgan/tiny-emitter/pull/21#issuecomment-322116703
Actually I just reverted #21

Thanks! Merged and released as 2.0.2 👍


Responsive display utilities

This explores adding responsive display utilities, replacing the static inline, inline-block, and block options we have currently. The twist here though is that the lowest breakpoint doesn't have a breakpoint abbreviation in the class name.
Here's an example of what I mean with just the display: none utility:
/* Same as `.d-xs-none`, but without the `-xs` part */
.d-none { display: none !important; }

@media (min-width: 576px) {
  .d-sm-none { display: none !important; }
}

@media (min-width: 768px) {
  .d-md-none { display: none !important; }
}

@media (min-width: 992px) {
  .d-lg-none { display: none !important; }
}

@media (min-width: 1200px) {
  .d-xl-none { display: none !important; }
}

I'm exploring this since the lack of xs could make it an easier transition to v4 for those who used the v3 utilities. Plus it's a bit more accurate to what's happening in the compiled CSS since there's no media query around those styles.
Thoughts?

I like this idea! +1

Don't like this idea - BS could really use a built-in breakpoint that will handle the transition between portrait and landscape mode on a mobile device.  PLEASE add .xs with a breakpoint of 480 px.

Makes total sense.
Actually, the responsive grid we built in company a few years back (and still in use), doesn't have a 'size' indicator in the lowest breakpoint.
And by saying that, I think that everything should follow this idea (grid's col, text-align, pull, push, etc).
It will be a big breaking change coming from v3, but what the hell, find and replace for the win ;)

@andyl This isn't about what the breakpoints are. This is about adding responsive display utility classes and perhaps negating the xs breakpoint name from that class name.

And by saying that, I think that everything should follow this idea (grid's col, text-align, pull, push, etc).
It will be a big breaking change coming from v3, but what the hell, find and replace for the win ;)

Yeah, that's the idea @saviomd.

As a comparison, here's the float utils already in v4-dev. Note that the xs class has no wrapping media query. If this PR were to merge, I'd make the same change to the float-xs-* classes and remove the -xs part.
.float-xs-left {
  float: left !important;
}

.float-xs-right {
  float: right !important;
}

.float-xs-none {
  float: none !important;
}

@media (min-width: 576px) {
  .float-sm-left {
    float: left !important;
  }
  .float-sm-right {
    float: right !important;
  }
  .float-sm-none {
    float: none !important;
  }
}

@media (min-width: 768px) {
  .float-md-left {
    float: left !important;
  }
  .float-md-right {
    float: right !important;
  }
  .float-md-none {
    float: none !important;
  }
}

@media (min-width: 992px) {
  .float-lg-left {
    float: left !important;
  }
  .float-lg-right {
    float: right !important;
  }
  .float-lg-none {
    float: none !important;
  }
}

@media (min-width: 1200px) {
  .float-xl-left {
    float: left !important;
  }
  .float-xl-right {
    float: right !important;
  }
  .float-xl-none {
    float: none !important;
  }
}

Visually prefer to keep -xs

For consistency in naming, I would argue that leaving -xs in would be better.

If it starts on zero I think that no makes any sense to have the xs prefix, I agree with this idea 👍

For the sake of clarity and consistency, I really like the xs-. It was a bit of an adjustment, coming from v3, but it only takes a few minutes to get used to it. In my opinion something about using xs- feels semantically nice.

I think it's a good idea. No breaking point it's like the default value. So using d-none makes sense. But removing the xs qualifier can be confusing for some people, you don't really know which screen will be affected. However, BS is mobile first so all default css should affect the smallest device first.

@mdo I've been using this approach for couple of years and its been working great.
Here is how I use it with size utility:
/**
  * @namespace u-
  * @block size-* [ 1of2, 1of3 ]
  * @modifier --* [ sm, md, lg, xl ]
  * @description Utility for sizing element width across breakpoints
  *
  * @require {Mixin} media-above - Generate mq for given breakpoint
  * -----------------------------------------------------------------------------
  */

.u-size-1of2 { width: percentage(2/1) !important; }
.u-size-1of3 { width: percentage(3/1) !important; }

@include media-above("xs") {
  .u-size-1of2--sm { width: percentage(2/1) !important; }
  .u-size-1of3--sm{ width: percentage(3/1) !important; }
}

@include media-above("sm") {
  .u-size-1of2--md { width: percentage(2/1) !important; }
  .u-size-1of3--md{ width: percentage(3/1) !important; }
}

@include media-above("md") {
  .u-size-1of2--lg { width: percentage(2/1) !important; }
  .u-size-1of3--lg{ width: percentage(3/1) !important; }
}

@include media-above("lg") {
  .u-size-1of2--xl { width: percentage(2/1) !important; }
  .u-size-1of3--xl { width: percentage(3/1) !important; }
}

It gives a lot of flexibility as you always start with default class name (breakpoint agnostic) and then override as you go up. Go for it!

I fully support this. As I've been developing v4 sites. Remembering to put -xs in there for a default value to apply to every breakpoint has been hard to remember

As @maximebeaudoin said "BS is mobile first so all default css should affect the smallest device first" and continue up.
This makes so much sense.

#{$abbrev}-#{$breakpoint}-#{$size} { #{$prop}:        $length-y $length-x !important; } // a = All sides
for all sides...  a or not a ?
Personally I prefer {abbrev}{sides}-{breakpoint}-{size} even for "all" but both are logical.

keeping as a rule xs md lg etc .. would be nice but in the same time why waste time to write xs when you can just do d-none instead of d-xs-none was even a bit hard to write :-). should flip a coin guys =D because this goes as a 50 - 50% :))

@mdo wouldn't it be better to have "up" and "down" modifiers?
@each $breakpoint in map-keys($grid-breakpoints) {
    @include media-breakpoint-up($breakpoint) {
        .float-#{$breakpoint}-left-up {
            @include breakpoint($screen-sm-min) {
                float:left!important;
            }
        }
        .float-#{$breakpoint}-right-up {
            @include breakpoint($screen-sm-min) {
                float:right!important;
            }
        }
        .float-#{$breakpoint}-none-up {
            @include breakpoint($screen-sm-min) {
                float:none!important;
            }
        }
    }
    @include media-breakpoint-down($breakpoint) {
        .float-#{$breakpoint}-left-down {
            @include breakpoint($screen-sm-min) {
                float:left!important;
            }
        }
        .float-#{$breakpoint}-right-down {
            @include breakpoint($screen-sm-min) {
                float:right!important;
            }
        }
        .float-#{$breakpoint}-none-down {
            @include breakpoint($screen-sm-min) {
                float:none!important;
            }
        }
    }
}

Heads up, I've updated this PR to also include the same changes to the float utilities. Responsive spacers have also already landed in v4-dev with #20926.

.text-xs-center will still with the -xs?


Examples: color mode enhancement

Description
Adding a theme toggle in each example.
Some small tweaks on some examples for the color mode.
Motivation & Context
Better change the color mode inside examples
Type of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactoring (non-breaking change)
[ ] Breaking change (fix or feature that would change existing functionality)

Checklist

[x] I have read the contributing guidelines
[x] My code follows the code style of the project (using npm run lint)
[x] My change introduces changes to the documentation
[x] I have updated the documentation accordingly
(NA) I have added tests to cover my changes
[x] All new and existing tests passed

Live previews

https://deploy-preview-38144--twbs-bootstrap.netlify.app/docs/5.3/examples

Related issues
NA
Still todo
See if a fixed dropdown would be better.
Set a partial for this dropdown.
Need to be merged with #38058 ?

I was thinking about it with the first version that uses the current color mode. Totally agree that this is way better to change it directly within the examples but I didn't know how.
Not a big fan of having an extra bar right now; especially in the navbars examples. But I can't find another way of doing it.
Another option could be to display the toggle in absolute position on the top-right corner of the window; on top of everything in the same spirit as back to top buttons. But it might block the navigation in some use cases. And it should be accessible for keyboard users as well.
Or maybe something semi-hidden on the top right or left corner of the page like this skip links menu in Storybook (accessible and maybe with a bigger surface to see that there's actually something to click on):

Thanks @mdo for https://github.com/twbs/bootstrap/pull/38144/commits/81f2f8616ad5e286fb8890d88085fa43798ce79b. Sounds better, and less intrusive than a header.
@louismaximepiton I let you finalize the PR and I'll review it when it's ready but I like it already, very handful!


Can you increase the size of the click area to open folder notes so that it is over the folder name and the folder icon?

I recently had an issue where this plugin would not work at all, even after reloading the plugins or restarting the program. I had to uninstall the plugin and reinstall it to get it to work.
Now though I noticed that the click area on some of the folders and all of the folder notes is to the far right in the blank area next to the folder name, which is not intuitive,
Notice that I said some folders are like that where some aren't. If the folder has  the greater than symbol ">" pointing to the right like an arrow then you can't click on the folder to expand it but have to click to the right of that symbol. But the folders that do not have that symbol you can just click on the folder to expand it.
Is it possible to fix this issue?

it will be fixed in next version, this commit to be exact

available in v0.15.0


Can I use external CSV file to set the values dynmically

I am using this example https://vasturiano.github.io/cartogram-chart/example/world-population/
then on a button click event:
Below is a snippet of Vue code
this.data = await d3.csv('data.csv')

      // set the values
      const ccData: any = []

      this.data.forEach((d: any) => {
        ccData[d.name] =
          d[this.selectedAction] && d[this.selectedAction] > 0
            ? parseFloat(d[this.selectedAction])
            : 0
      })

      this.cartogram
        .value(({ properties: p }: any) =>
          ccData[p.NAME] ? ccData[p.NAME] : 0
        )
        .iterations(85)

The value seems to be set correctly however, there is no changes to projection.

@kurund if your new value function leads to substantially different proportions of the geometries you should see a visual change in the map shapes.
However it's difficult to say what the issue is in your app without more context. Can you make a simple (non-vue) example on codepen.io that reproduces the issue?


Jenkinsfile && tests in container

https://ci.centos.org/job/packit-pr/

LGTM, are we waiting for the centos ci user to start the party?

There're some issues with the Jenkins job, I'll merge myself once resolved.

Builds in Jenkins run, so we can merge. The failures are unrelated to this ticket.
We'll see the results in PRs once centos-ci user confirms invitation.