BitNet support

I'm curious: if Llama.cpp adds BitNet support (which looks imminent), will Wllama be able to run Bitnet models too by simply upgrading the Llama.cpp version? Or will there be more things that need to happen?
https://github.com/ggerganov/llama.cpp/pull/7931

It totally depends on llama.cpp side, but I suppose that it will be transparent to us (much like how support for phi-3 is added)

Any second now.. GGerganov has already signed off on it.
I was thinking: could be cool to immediately create a demo showcasing BitNet in the browser via Wllama? I could create one, but so far I've not been able to compile Wllama myself. I'm trying to get that working again now though.

I've managed to get compiling working (reinstalled Docker).
I then tried to use the very latest version of Llama.cpp with BitNet support. Unfortunately I ran into an error:

and another attempt:

and

Got a bit further. This model works fine on llama.cpp, but has some strange behaviour in wllama. But I'll try fiddling with some settings.

I've put a quick (still broken) demo here:
https://github.com/flatsiedatsie/bitnet_in_the_browser/

Keep pushing it, @flatsiedatsie!

Very cool @flatsiedatsie
Just my personal POV, maybe firstly we make sure that it runs absolutely stable on native llama.cpp, then we will see what's the problem when bringing it to wllama. That way we can narrow down the scope when searching for a bug.

Got a bit further. This model works fine on llama.cpp, but has some strange behaviour in wllama. But I'll try fiddling with some settings.

The generation seems to work fine. I suspect maybe something to do with special tokens and chat template

So, turns out the available model is not instruction-tuned, so we can't expect it to be usable for chat. See: https://huggingface.co/BoscoTheDog/bitnet_b1_58-xl_q8_0_gguf/blob/main/tokenizer_config.json
At this point, it seems to be working at inference level. Not much we can do to fix the chat issue (which requires training / fine tuning the model). I'll release a new version of wllama with up-to-date source code so we're ready when new models appear.
Also note that, mul_mat is not (yet) optimized for bitnet, so we can't expect good level of performance out of llama.cpp.

Here's another specialized version of the model, straight from the horse's mouth:
https://huggingface.co/imi2/test/resolve/refs%2Fpr%2F10/bitnet_b1_58-3B-Q1_3-1.63bpw.gguf
via
https://www.reddit.com/r/LocalLLaMA/comments/1dnbf6s/33b_bitnet_test_on_1gb_ram_retro_handheld/ (worth a read)
I couldn't get that to run on my mac yesterday though, probably because up to an hour ago it wasn't optimized for ARM yet. Things move so fast..

There's also the 700M BitNet model (named "large") which in Q1_3 takes only 171 MiB, which is useful if you're very low on RAM. And its speed is more usable on low-end devices (getting close to 7 tokens per seconds on 4 Arm cortex-a53 cores (phone), and 7.5 tok/s with 4 cortex-a72 cores (rpi4)).

I found a bitnet model that, in theory, is instruct tuned.
Running it results in the same gobbledygook though.

I'm uploading the Q16 .gguf version I made here.
I also tested it with llama.cpp and it runs, although it seems to have a fascination with Cow emojis.

This almost seemed like an answer at first:

Ah, this may explain the cow theme:

And the name "Bessie" Seems to be a good output for this model too.

I must admit I still don't quite grasp why it doesn't work.
I've kept trying with various models, but they all output.. repetitive strangeness. Often large amount of newlines.
Even if they are just base models, feeding them "Once upon a time" should result in something of a story, right? And since it does seem to work with the llama.cpp binary, what could be different about the wasm version?

IMO the most simple way is to test if the same prompt works with original HF transformers python library. After all, someone uploads a model doesn't mean it will work.

OMG I FIGURED IT OUT!
All I had to do was add <s> before the prompt!

That's great news @flatsiedatsie!
Now we just need to find a good instruction-tuned one. Keep us posted! 🎉

Thanks! Will do!

This error could be my "work offline" modification, but I thought I'd share:


Add about page with project info

📝 Changed routes:

/_version
/admin

(view full size)
(view full size)

Commit 090873e041123d335c326e78721564a145c78993 (https://cesium-link-4xcjt42g7-cesiuminho.vercel.app).


Add node creation tests

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

Project coverage is 50.54%. Comparing base (583c04f) to head (62bd207).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #88      +/-   ##
==========================================
- Coverage   50.78%   50.54%   -0.24%
==========================================
  Files          64       66       +2
  Lines        3011     3013       +2
  Branches     1112     1112
==========================================
- Hits         1529     1523       -6
- Misses        659      664       +5
- Partials      823      826       +3

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


Try find a main conainer by Common selectors

Attempt to identify the main content element
I was started and improve it more later.

@Mosharush
I think a better UX approach is to let the user determine the calculation method.
I mean that we should add a Checkbox in the popup menu that lets the user decide if he wants the percentage to be calculated by the total length of the page or the extension should try to identify the main text block on the page and calculate the percentage of it.

@dimshik100 On this!

@Mosharush
I think a better UX approach is to let the user determine the calculation method.
I mean that we should add a Checkbox in the popup menu that lets the user decide if he wants the percentage to be calculated by the total length of the page or the extension should try to identify the main text block on the page and calculate the percentage of it.

Done!


Garbled characters in scop of   history

any solution to clear the history and garbled characters ?

That might come from the regular expression here: https://github.com/MobileTribe/commit-template-idea-plugin/blob/e07bcba4bc1d4a9c513fa89262e59f9de0f8c8ab/src/com/leroymerlin/commit/GitLogQuery.java#L18
Could you please check?

That might come from the regular expression here:
https://github.com/MobileTribe/commit-template-idea-plugin/blob/e07bcba4bc1d4a9c513fa89262e59f9de0f8c8ab/src/com/leroymerlin/commit/GitLogQuery.java#L18
Could you please check?

sorry bro ,I am not familiar with java,but i can try ,where and how to check ?


Counting adding 100 more to counter

If my count number is 80, it stops at 80, but immediately it runs again until 180

My bad, its early and I did not see the +100 from the example


Add needlecast gentx

Please make sure your node is up and running. Join #validators Discord for help: https://discord.gg/QeJWCrE.


Tutorial section about async updates seems confusing

How would an instance change its props? Is this bit in reference to the deprecated setProps method? Or is this alluding to something that is discussed in later sections of this tutorial? If so, I can't find it.
In any event, it seems confusing and I've seen questions brought up about it without answers (other than those that refer to Redux).
https://github.com/reactjs/reactjs.org/blob/master/content/docs/state-and-lifecycle.md#state-updates-may-be-asynchronous-state-updates-may-be-asynchronous

A component doesn't directly change its props. But if it receives a function as a prop from a parent component and calls it, the parent component might rerender, resulting in new props being passed down.

Figured it must be referring to a new instance, but it seems like that should be explained in the cited section.


Build error in ios after downloading 4.0.1

Hi,
I was using 3.0.2 version and there was no problem. I noticed that there was newer version 4.0.1. When I tried to build the app in iOS xcode exits with code 65.  The reason I was updating to newer version was after selecting the image I was not able to save the image in my app directory as "jpg" from the imageSource. It was successful in storing the image in png format.
I am using the following version:
tns-core-module: 3.1.0
tns-ios: 3.2.0
Mac verion: 10.12.6
xcode:9.0.1
xcode command line tools: 9.0
Thanks

Hi @halaharr,
Thank you for reporting this issue.
I tested the latest version of the plugin while using NativeScript CLI 3.3.0 and tns-core-modules 3.3.0, however, was unable to recreate an issue with the image picker. For your convenience, I am attaching a sample project.
I would suggest upgrading you cli while using npm install nativescirpt --g and to upgrade the dependencies in your project, while following the below-attached sample package.json .
  "dependencies": {
    "nativescript-imagepicker": "4.0.1",
    "nativescript-theme-core": "^1.0.4",
    "nativescript-unit-test-runner": "^0.3.4",
    "tns-core-modules": "^3.3.0"
  },
  "devDependencies": {
    "typescript": "~2.5.0",

  },

If the problem still persists, please send us sample project, which could be debugged locally.
Archive.zip

@halaharr were you able to resolve your issue?
Closing due to inactivity but please do let me know if you need further assistance.


Interview crashes when there is no one on other side of the case

Error
[Retry](https://apps-dev.suffolklitlab.org/interview?i=docassemble.playground234MtntoImpound%3AMtn_to_Impound_final.yml#)

IndexError: list index out of range
History
Ran initial code at 0.00000s
(from al_saved_sessions.yml)

initial: True
code: |
  ########### Save title and progress to session list ##################
  if get_config("assembly line",{}).get("update session metadata"):
    # To limit impact on DB, save progress every 3 steps or when progress is 100 +- 1
    if get_progress() > 99 or int(_internal.get('steps',1)) % 3 == 1:
      al_temp_metadata = get_interview_metadata(
        user_info().filename, user_info().session
      )
      al_temp_metadata["auto_title"] = str(al_sessions_interview_title)
      al_temp_metadata["progress"] = get_progress()
      set_current_session_metadata(al_temp_metadata)
      del(al_temp_metadata)
Ran initial code at 0.00003s
(from al_visual.yml)

initial: True
code: |
  # Set the dropdown/hamburger menu items
  # by default we just add a "Start over" link
  if _internal.get('steps') > 1:
    menu_items = al_menu_items
  else:
    menu_items = al_menu_items[1:] # Skip the "start over" menu item
Needed definition of al_menu_items at 0.00007s
Tried to run block at 0.00013s
(from al_visual.yml)

reconsider: True
code: |
  al_menu_items_tmp = [
    {"url": url_ask(['al_start_over_confirmation','al_start_over']),
    "label": "Start over"
    },
  ]

  # Answer set feature is behind a server-wide configuration option
  if get_config('assembly line',{}).get('enable answer sets'):
    al_menu_items_tmp.extend([
    {"url": url_ask(["al_sessions_snapshot_label", {"recompute": ["al_sessions_save_session_snapshot"]}, "al_sessions_save_status"]),
    "label": "Save answer set"
    },
    action_menu_item("Load answer set", "al_load_saved_session"),
  ]
  )

  if get_config('assembly line',{}).get('enable answer set imports'):
    al_menu_items_tmp.append(
      {"url": url_ask(["al_sessions_json_file", {"recompute": ["al_sessions_import_json"]}, "al_sessions_load_status"]),
      "label": "Import answer set"
      }
    )

  al_menu_items = al_menu_items_tmp
  del al_menu_items_tmp
Ran initial code at 0.00097s
(from al_saved_sessions.yml)

initial: True
code: |
  ########### Save title and progress to session list ##################
  if get_config("assembly line",{}).get("update session metadata"):
    # To limit impact on DB, save progress every 3 steps or when progress is 100 +- 1
    if get_progress() > 99 or int(_internal.get('steps',1)) % 3 == 1:
      al_temp_metadata = get_interview_metadata(
        user_info().filename, user_info().session
      )
      al_temp_metadata["auto_title"] = str(al_sessions_interview_title)
      al_temp_metadata["progress"] = get_progress()
      set_current_session_metadata(al_temp_metadata)
      del(al_temp_metadata)
Ran initial code at 0.00099s
(from al_visual.yml)

initial: True
code: |
  # Set the dropdown/hamburger menu items
  # by default we just add a "Start over" link
  if _internal.get('steps') > 1:
    menu_items = al_menu_items
  else:
    menu_items = al_menu_items[1:] # Skip the "start over" menu item
Tried to load objects from file at 0.00118s
(from docassemble.ALMassachusetts:al_massachusetts.yml)

objects from file:
  - court_emails : court_emails.yml
Tried to ask mandatory question at 0.02450s
progress: 100
mandatory: True
id: Your form is ready to download and file
question: |
  Your form is ready to download and file
subquestion: |
  Thank you ${users}. Your form is ready to download and deliver.

  Below is a preview of your form.

  ${pdf_concatenate(Mtn_to_Impound_final_attachment['final'], filename='Mtn_to_Impound_final.pdf') }
need: Mtn_to_Impound_final
attachment code: Mtn_to_Impound_final_attachment['final']
Needed definition of Mtn_to_Impound_final at 0.02455s
Tried to run block at 0.02460s
id: interview_order_Mtn_to_Impound_final
code: |
  # This is a placeholder to control logic flow in this interview

  basic_questions_intro_screen
  Mtn_to_Impound_final_intro
  # Set the allowed courts for this interview
  allowed_courts = interview_metadata["Mtn_to_Impound_final"]["allowed courts"]
  nav.set_section('review_Mtn_to_Impound_final')
  # Below sets the user_role by asking a question.
  # You can set user_role directly instead to either 'plaintiff' or 'defendant'
  user_ask_role
  if len(users) > 1:
    multiple_users # event name
  trial_court.address.county
  str(docket_numbers)
  str(other_parties)
  other_parties[0].address
  affidavit_narrative
  delivery_mode
  str(users)
  signature_date
  # Set the answer file name.
  set_parts(subtitle=str(users))
  set_progress(14.29)
  set_progress(28.57)
  # Save (anonymized) interview statistics.
  store_variables_snapshot(
    persistent=True,
    data={'zip': showifdef("users[0].address.zip"), "reached_interview_end": True})
  Mtn_to_Impound_final_preview_question # Pre-canned preview screen
  basic_questions_signature_flow
  Mtn_to_Impound_final = True
[Show variables and values](https://apps-dev.suffolklitlab.org/vars?i=docassemble.playground234MtntoImpound%3AMtn_to_Impound_final.yml)

Log
Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8038, in assemble
    interview_status.populate(question.ask(user_dict, old_user_dict, 'None', [], None, None))
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 5094, in ask
    eval(need_code, user_dict)
  File "<need expression>", line 1, in <module>
NameError: name 'Mtn_to_Impound_final' is not defined

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/util.py", line 2281, in __getitem__
    return self.elements[index]
IndexError: list index out of range

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/flask/app.py", line 1523, in full_dispatch_request
    rv = self.dispatch_request()
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/flask/app.py", line 1509, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**req.view_args)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/webapp/server.py", line 8077, in index
    interview.assemble(user_dict, interview_status, old_user_dict, force_question=special_question)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8296, in assemble
    raise the_error
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8083, in assemble
    question_result = self.askfor(missingVariable, user_dict, old_user_dict, interview_status, seeking=interview_status.seeking, follow_mc=follow_mc, seeking_question=seeking_question)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 8746, in askfor
    exec_with_trap(question, user_dict)
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/parse.py", line 9366, in exec_with_trap
    exec(the_question.compute, the_dict)
  File "<code block>", line 16, in <module>
  File "/usr/share/docassemble/local3.10/lib/python3.10/site-packages/docassemble/base/util.py", line 2288, in __getitem__
    raise IndexError("list index out of range")
IndexError: list index out of range


⚠ Bofrost.at has degraded performance

In 17e2583, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 947 ms

Resolved: Bofrost.at performance has improved in 20777a0 after 13 minutes.


AMD Ryzen Threadripper PRO 3995WX 64-Cores [UNKNOWN DEVICE - PLEASE REPORT ON GITHUB]

Reporting unknown devices. :)

Duplicate of #1558


names are not sync in all devices

In my mobile, my name is 'Salty Lemon'.

but on my computer is appears to be 'Acidic Cactus' (I recognized the device by the purple color)

@msrl2000 The problem should now be resolved.


Fixed some typos and tried to make it read more nicely

Maybe @saana-kontenacm can make it even less robotic.

LGTM!


Publish to npm?

At some point (later), I wish we can look into publishing APEX Front-End Boost to npm.

@vincentmorneau I don't see why not do it. May be good to outline how you did it so we can apply to other OOS projects.


feat(build-cli): Add exec command

This PR adds an exec command to build-cli, which can be used to execute shell commands in the context of packages or release groups in the repo.
The following example runs pnpm -r remove @rushstack/eslint-config on all independent packages and all release group root packages:
flub exec --all --releaseGroupRoots "pnpm -r remove @rushstack/eslint-config"

I think that for this command to be useful, one needs to be able to scope the packages that it runs on to the following groups:

All independent packages in the repo - use the --packages flag.
All packages in the repo using a particular scope - use the --scope and --skipScope flags.
A single package in a directory - use the --dir flag.
All individual packages in a release group - use the --releaseGroup flag.
All release group root packages - use the --releaseGroup and --releaseGroupRoots flags together.
All release group root packages and independent packages - use the --all and --releaseGroupRoots flags together.
All release group packages and independent packages - use the --all flag.

I implemented this by adding two new flags to the BasePackageCommand class, --all and --releaseGroupRoots. Most of the code change was in the base class. This means that the typetest command can also benefit from the new flags. That said, releaseGroupRoots in particular doesn't make sense for typetests, so perhaps the new flags shouldn't be on the base class? Feedback welcome.

Making the new options work for everything (what you did) seems like the best choice. I think it would be fine to normalize type test information across all release packages after a tooling update for example.

Making the new options work for everything (what you did) seems like the best choice. I think it would be fine to normalize type test information across all release packages after a tooling update for example.

That's a great scenario that I had not considered. Cool!


Check whether offset  is null before checking if is integer

Add a check to offset to fix #87

Yay! I've been working around this for too long! @WFrancois, maybe you want to tackle one other potentially small fix? There are a couple statement types that don't use the correct limit syntax. I documented one case at issue #78 , but I know there are more.

Will you run a patch release to include this change, @FaaPz ?

@alexsasharegan I just released v1.10.1 with this change.


Migrate CircleCI to V2

CircleCI is deprecating the V1 config : https://circleci.com/blog/sunsetting-1-0/
We should move to the V2 config prior to the deprecation date.

Thanks for the pointer.
I made a start at https://github.com/weaveworks/weave/compare/circle20, but got sidetracked.


Some missing entries

These are some missing entries:
Terrain tools

FieldsPapers

Mobile Maps

Maps.ME

JavaScript

Leaflet
OpenLayers

Learn websites

TeachOSM

Hey @angoca,
Thanks for your suggestions! FieldsPapers, Leaflet, OpenLayers, and TeachOSM are great additions.
I am a bit hesitant about adding Maps.ME however, as we already have Organic Maps, which very similar to Maps.ME, as it was made by some of the original Maps.ME creators.
Do you think Maps.ME is different enough to be listed anyways?

Hi Kevin,
Well, I am not sure what is your criteria to select a project to be or not to be on the list. In the header, it says "projects using OpenStreetMap data for creative purposes, as well as projects dedicated to improving OpenStreetMap". IMHO, according to this sentence, Maps.ME could fit.
Anyway, It is up to you. However, as we dig into this OSM space, you will find many more projects, and probably you will need to create more specific ones.
On another side, this is another source of projects you can include many of them in this list: https://osm-apps.zottelig.ch/
And the last thing, thank you for this list. This kind of curated content lacks in the OSM world. I hope you keep working in this to continuously improve it, and remove the dead projects.

Hey Andres,
there are no clear cut criteria, I'm just trying to work together with everyone to build a high-quality list. This is why I didn't outright deny adding Maps.ME to the list, but asked if you think it is different enough. I think I'll create a discussion topic about adding Maps.ME to invite comments from others.
I'll look at the list you've sent, it seems to contain a lot of interesting projects, but it'll take some time to go through.
And last but not least, thank you for being part of the community and sending in suggestions! There are so many amazing projects out there I only learn about because others send them in :p

The Maps.ME discussion will now be tracked in #42 and the list you posted will be tracked in #43.
I'll have the other projects in a PR in a few minutes :)
Thanks for your additions! 😃


Make the library reentrant and thread-safe

Moves non-immutable variables from class-scope to function scope, and makes the constants shared across all class instances.
This allows to make multiple concurrent calls to OpenGraphParser.parse without having different threads and coroutines interfere with each other

@Mek101
These changes were locally committed and were being tested out currently.
Your commit, however, includes moving constants to be shared across instances.
I shall include your changes.
Thank you for your contribution.


Establish Project Tenants

As we gain more users and (hopefully) contributors it makes sense to establish some core project tenants that can live in the README and help guide feature decisions. There are a few I've been adhering to, which are:

Keep external dependencies to a minimum
No unsecured network requests should be required for operation (say, for a list of exit nodes)
Favor simplicity and code readability to make it easy for folks to understand what the script is actually doing
Assume the user is new to using the command line, make usage intuitive and errors descriptive
Maintain cross-distro Linux and OS X support

Do these make sense? Are things missing?

Also, are we currently not following any of these?

At a glance, sounds reasonable.
Also, as a suggestion, you could introduce these guidelines to the project by using this format: GitHub Blog - Contributing Guidelines

:+1: Good call. I usually just put this in the readme, but it would be better to create a distinct file and just link to it in the readme.

Thanks. How can I contribute with a small financial donation? And can you add an update feature in de script with which you start the vpn connection so that the list with exit nodes is always up to date? Or create a PPA?

Hi @hamariko! In reverse order: I'm a bit behind on the effort but there is intention to create a PPA, per #16. I'll update the README and release notes when it finally happens.
I'm not entirely clear on the UX for the exit node list being kept up to date. Currently, to avoid making unsecured network connections to determine what the current server list is, hard coded domain names are used instead. In the event a new exit node is added by ProXPN and not supported by this script please make an issue for that exit node and I'll add it right away and cut a new release. If that's not satisfactory could you describe the behavior you'd be looking for in a new issue so we can open the implementation discussion?
Regarding the financial donation, I'm pleased that you're getting value out of this script, but instead of donating to me I suggest sending the same amount to UNICEF an excellent, trustworthy charity that helps children across the world.


Optimization: Use precalculated IOContexts for withReadAdvice() to not create new instances all the time

Followup of #13242: This optimizes the IOContext#withReadAdvice() method to use precalculated instances of IOContext to not create new instances all the time.

I think last one is shortest. EnumMap would have been fine, but as it is all internal cache a simple array on enum's ordinal number is enough (same approach like switch statements on enums use).


Support for Agones Kubernetes controller for gaming servers

Agones is an Open source Kubernetes Controller with custom resource definitions and is used to create, run, manage and scale dedicated game server processes within Kubernetes clusters using standard Kubernetes tooling and APIs.
This model also allows any matchmaker to interact directly with Agones via the Kubernetes API to provision a dedicated game server.
Add Agones Helm Chart to this module allow the users to deploy to EKS Cluster
https://agones.dev/site/

Agones module is merged with the main branch now 👍🏼


Specify full authority for genesis accounts

For some Golos smart-contracts it's need to specify not only public key, but other fields in authority. Also it's need to specify authority with another name (not only owner and active).

implemented in #654


Not working on Windows

Describe the bug
When execute npm run dev, even if starting from cleanroom, an error occurs:

TypeError: loadTheme is not a function

To Reproduce
Steps to reproduce the behavior:
Just follow the startup guide:
> npm init slidev
Need to install the following packages:
  create-slidev
Ok to proceed? (y) y

  ●■▲
  Slidev Creator  v0.6.11

√ Project name: ... slidev
  Scaffolding project in slidev ...
  Done.

√ Install and start it now? ... yes
√ Choose the agent » npm

added 216 packages, and audited 217 packages in 11s

30 packages are looking for funding
  run `npm fund` for details

2 high severity vulnerabilities

To address all issues (including breaking changes), run:
  npm audit fix --force

Run `npm audit` for details.

> dev
> slidev --open

C:\Users\xxx\projects\slidev\node_modules\@slidev\theme-seriph\setup\shiki.ts:6
      dark: await loadTheme(require.resolve('theme-vitesse/themes/vitesse-dark.json')),
                  ^

TypeError: loadTheme is not a function
    at C:\Users\xxx\projects\slidev\node_modules\@slidev\theme-seriph\setup\shiki.ts:6:19
    at loadSetups (C:\Users\xxx\projects\slidev\node_modules\@slidev\cli\dist\chunk-T2VCIMLG.js:679:28)
    at createMarkdownPlugin (C:\Users\xxx\projects\slidev\node_modules\@slidev\cli\dist\chunk-T2VCIMLG.js:807:32)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async ViteSlidevPlugin (C:\Users\xxx\projects\slidev\node_modules\@slidev\cli\dist\chunk-T2VCIMLG.js:962:26)
    at async createServer (C:\Users\xxx\projects\slidev\node_modules\@slidev\cli\dist\chunk-HAH2CPJC.js:10:7)
    at async initServer (C:\Users\xxx\projects\slidev\node_modules\@slidev\cli\dist\cli.js:70:14)
Error: Command failed with exit code 1: npm run dev
    at makeError (C:\Users\xxx\scoop\persist\nodejs\cache\_npx\c00c242a51a5200e\node_modules\execa\lib\error.js:59:11)
    at handlePromise (C:\Users\xxx\scoop\persist\nodejs\cache\_npx\c00c242a51a5200e\node_modules\execa\index.js:114:26)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async init (C:\Users\xxx\scoop\persist\nodejs\cache\_npx\c00c242a51a5200e\node_modules\create-slidev\index.js:121:5) {
  shortMessage: 'Command failed with exit code 1: npm run dev',
  command: 'npm run dev',
  exitCode: 1,
  signal: undefined,
  signalDescription: undefined,
  stdout: undefined,
  stderr: undefined,
  failed: true,
  timedOut: false,
  isCanceled: false,
  killed: false
}

Desktop (please complete the following information):

OS: Windows
Browser: Microsoft Edge
Slidev version: 0.6.11

Have you tried the least version of Slidev?

Have you tried the least version of Slidev?

Well, after change current version to 0.20.0, it works. Hope the latest version can be the default version of npm init slidev.
By the way, the global version of slidev is also not working:
C:\Users\xxx\yyy> slidev .\talk.md

  ●■▲
  Slidev  v0.20.0

  theme   @slidev/theme-default
  entry   C:\Users\xxx\yyy\talk.md

  slide show      > http://localhost:3030/
  presenter mode  > http://localhost:3030/presenter
  remote control  > pass --remote to enable

  shortcuts       > restart | open | edit

node:events:371
      throw er; // Unhandled 'error' event
      ^

Error: spawn<EMAIL_ADDRESS>ENOENT
    at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
    at onErrorNT (node:internal/child_process:480:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
    at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
    at onErrorNT (node:internal/child_process:480:16)
    at processTicksAndRejections (node:internal/process/task_queues:83:21) {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn<EMAIL_ADDRESS>  path<EMAIL_ADDRESS>  spawnargs: [ '--service=0.12.8', '--ping' ]
}

Hope the latest version can be the default version of npm init slidev.

It's npm's cache, there is nothing I could do I think. You might need npm init slidev@latest

By the way, the global version of slidev is also not working

No idea on that. Looks like a esbuild issue


Expand LanguageModel to know two more things about every LLM: context size and if it supports tool function calling

I think the function calling can just be a boolean: supports_tools. Inside the ai_backend's we need to make sure that a really long conversation starts skipping older messages so that the submitted payload never exceeds the context size. Maybe this attribute is simply context_window, that's what OpenAI and Anthropic both seems to call it.

Did you see the pull request, @krschacht ?

Thanks for doing this, @stephan-buckmaster! I'm just about done giving it a review. It never hurts to give me an extra ping. :)


Further abstract libultra time types and functions.

Another PR for issue #65.
libultra time types and functions abstracted:

replaced OSTime with Time
replaced osGetTime with timeGetTime
replaced OS_CYCLES_TO_USEC with timeMicroseconds
replaced OS_CYCLES_TO_NSEC with timeNanoseconds

also:

lastReportStart of ProfileData was used to store both cycles and microseconds, now it stores only microseconds
fixed typo in profileTask: ns instead of us

Great, thanks! How do you feel about tackling something a bit larger?
I'm thinking the sound player (soundplayer.{h,c}). The interface is already pretty generic, but what would be most useful is creating a libultra-independent API to replace the al*() functions it uses internally.
Similar to https://github.com/mwpenny/portal64-still-alive/pull/60#discussion_r1578760989, this would mean abstracting system-level code allowing the game's functionality on top to remain reusable.
What do you think?


HA_Strava isn't loading in Home Assistant Core 2022.5.0b0

Updated this afternoon.  It was working this morning, and no longer after going to the Beta May release.

I'm now seeing an error in my log:
Logger: homeassistant.setup
Source: setup.py:162
First occurred: 11:32:55 PM (1 occurrences)
Last logged: 11:32:55 PM
Setup failed for custom integration ha_strava: Unable to import component: cannot import name 'EVENT_TIME_CHANGED' from 'homeassistant.const' (/usr/src/homeassistant/homeassistant/const.py)
I'm going to close this and investigate further.

This is still broken for me in Home Assistant 2022.5.0b6.

I don't run the HA beta at home - once I upgrade to 2022.5 I'll try and take a look at getting it working again.
https://developers.home-assistant.io/blog/2022/04/20/saying-goodbye-to-event_time_changed/ seems to be the reason.

Big thanks to @madmic1314 for maintaining this integration thus far. I couldn't get it working either :-( but if anyone's interested I created a much simpler  Appdaemon script to gather some of the basic stats (all time ride, YTD ride) I was interested in and create HA entities with them - It's here https://github.com/brewston/Home-Assistant---Strava

I have a working version of this for anyone who is interested. Can be installed via HACS
https://github.com/craibo/ha_strava

Thank you @craibo I will test it out later today! :)


Skip fetch only works when CPM_SOURCE_CACHE is defined

When the environment variable CPM_SOURCE_CACHE is set, re-running cmake does not cause a fetch and patch.
When unset, fetch and patch both occur.
The problem observed (see #572 for more discussion) is that the unset path fetch does not overwrite the source and so the patch command fails.
#572 suggests a fix that could ignore errors during patching. I think this could be an issue when a user is testing version updates; it would be nice if we just, say, updated package A to latest version and running CMake told us the patches were incompatible/not applied. I don't think -t reports that?
In my testing, I see that when the environment variable is set, we skip the fetch and patch steps. Maybe we can add a cache variable to indicate the initial fetch and patch skips were successful?
Recreation of this is relatively simple, see https://github.com/ScottBailey/cpm-cmake-test-577 for an automated working example.
@lemire

A simple solution seems to be to always enable the cache.
--- a/cmake/CPM.cmake
+++ b/cmake/CPM.cmake
@@ -154,7 +154,7 @@ set(CPM_DRY_RUN
 if(DEFINED ENV{CPM_SOURCE_CACHE})
   set(CPM_SOURCE_CACHE_DEFAULT $ENV{CPM_SOURCE_CACHE})
 else()
-  set(CPM_SOURCE_CACHE_DEFAULT OFF)
+  set(CPM_SOURCE_CACHE_DEFAULT ${CMAKE_CURRENT_BINARY_DIR}/.cpm-cache)
 endif()

 set(CPM_SOURCE_CACHE

Intriguing.

Would be nice to have some sort of fix for this.
One option would be to do a git checkout . before every patch, at least for the case where there CPM_SOURCE_CACHE_DEFAULT is not set.

Would be nice to have some sort of fix for this.
One option would be to do a git checkout . before every patch, at least for the case where there CPM_SOURCE_CACHE_DEFAULT is not set.

I'd love to see this fixed myself. I started working on it, but it's a significant time investment for me. I've done the leg work to easily, repeatable recreate the defect and was hoping someone else might lend a hand. I may have time over the holidays to look deeper into this, but I'm not gonna hold my breath.
If you dig into this, I think you'll find significant complexity around this problem. Enough that a quick fix isn't likely to happen. Still, I'd appreciate someone else taking a look and providing feedback.

@ScottBailey What do you think of @wolfpld's solution?

I feel like this is unexpected behavior?

Here is how I view things.
We have two code paths. One that were the cache location is set. This code path works.
We have another code path where the cache location is not set. This code path is broken.
The fix is to have just one code path. If the cache location is not set, we just set it. This drops the broken code path and solves the problem... further simplifying the logic.
That is, that the code is so complicated is part of the bug. Why is it so difficult to understand what is going on?

As a counter, the code path without a cache in fact works except when a patch is added. If we force a cache path we reduce functionality for others. And if we make a band-aid fix we increase technical debt. Like you, I am just a contributor, not a maintainer. But were I a maintainer I don't think I'd want to take a patch that increased technical debt.
Frankly, I've been hoping I'd done enough prep work to make this an easy fix for someone else. And I think it should be an easy fix, just a little time consuming to compare the traces.

(I also have no power here. I am just a user.)

If we force a cache path we reduce functionality for others.

Concretely, what would be lost?

But were I a maintainer I don't think I'd want to take a patch that increased technical debt

How does the patch proposed by @wolfpld increases the technical debt?
My point above is that it reduces the technical debt by reducing the number of code paths.

The workaround generates dead code, no? Unless one were to take it out. Personally, I wouldn't mind a default of "${CMAKE_BINARY_DIR}/CPM_cpm_cache" if it didn't already exists because I ALWAYS want to cache and a simplification of the code. :-) I imagine we might get that in. But that is also not a small change.
Very pedantically: the band-aid only reduces the number of code paths executed and does so by generating dead code. That's technical debt. The process of properly removing that code path should is, I'd wager, greater than the cost of fixing the code.
With the band-aid, one would lose the ability to NOT cache downloads. I am uncertain of the impact this might have on others. Furthermore, I'm in no position to hazard a guess. Which means I'm not comfortable supporting its removal. Does that make sense?

I think that the patch we are discussing is equivalent to making the cache be versioned by default.

With the band-aid, one would lose the ability to NOT cache downloads.

Can't one just set CPM_ARGS_NO_CACHE to avoid cache downloads? Wouldn't that be the proper way?

Very pedantically: the band-aid only reduces the number of code paths executed and does so by generating dead code. That's technical debt. The process of properly removing that code path should is, I'd wager, greater than the cost of fixing the code.

Can you point at the dead code that would result? Which lines of code are you thinking about?
What I see in the code is a handful of case where we check whether CPM_SOURCE_CACHE is truthy.
There is a code region from line 773 to 849 where we check several times that CPM_SOURCE_CACHE is truth (in redondant manners):
https://github.com/cpm-cmake/CPM.cmake/blob/0bc73f41cedb561efe5643826891dcb705c680de/cmake/CPM.cmake#L773-L849
Specifically, they occur at these lines:
https://github.com/cpm-cmake/CPM.cmake/blob/0bc73f41cedb561efe5643826891dcb705c680de/cmake/CPM.cmake#L773
https://github.com/cpm-cmake/CPM.cmake/blob/0bc73f41cedb561efe5643826891dcb705c680de/cmake/CPM.cmake#L792
https://github.com/cpm-cmake/CPM.cmake/blob/0bc73f41cedb561efe5643826891dcb705c680de/cmake/CPM.cmake#L797
There is one additional trivial check...
https://github.com/cpm-cmake/CPM.cmake/blob/0bc73f41cedb561efe5643826891dcb705c680de/cmake/CPM.cmake#L896-L897
Importably, I do not see any block of code that becomes dead when we add the assumption that CPM_SOURCE_CACHE is always truthy.

Shoot! Your halfway there, why not just fix the defect?

More usefully: when I did the trace between cache set vs cache not set the path was significantly different. At the time I didn't have the bandwidth to really dig in and follow what was going on. I'd have to rerun the trace to have a defensible opinion - I'm really working from memory/gut here. I might have time to go back and look at it during the year end holiday, but probably not before then.


Change extend to override in release.nix

override doesn't compose well with extend (https://github.com/NixOS/nixpkgs/issues/26561). This PR changes the use of extend to override (and simultaneously sneaks in a dontCheck wrapper for inline-r, is this ok?)

Thanks!

Is there a reason you didn't use the solution in the linked issue?
haskellPackages.override (old: {
  overrides = lib.composeExtensions (old.overrides or (_: _: {})) (self: super: {
    # ...
  });
})

@vaibhavsagar Good catch. No reason - it was an oversight! I see you have since fixed, thank you :)


go-zero 可以支持查询数组?can go-zero support querying arrays?

如图，我需要制作一个批量删除内容的接口，目前期望的地址是批量传递一些ids。如下图：

通过api的配置如下

如你所见，他报错了。请问我的做法正确嘛？
我自己在logic中处理是可以获取到的

请问有什么好的办法吗？我希望在api中自动生成以便使用

There is no need to use [] in the tag, only the type is defined as an array, and the incoming is separated by commas.
example:
articlesDelReq {
    ids []int `form:"ids,optional"`
}

english please :(

thanks for your help。but i try it doesn't work
you can see this feedback

this is ok but get value is null

this is my article.api

so，it is something wrong?
Looking forward to your help again
very thanks

There is no need to use [] in the tag, only the type is defined as an array, and the incoming is separated by commas. example:
articlesDelReq {
    ids []int `form:"ids,optional"`
}

thanks for your help。but i try it doesn't work
you can see this feedback

this is ok but get value is null

this is my article.api

so，it is something wrong?
Looking forward to your help again
very thanks

Sorry, I confirmed it, and it is determined that form passing arrays is not supported in zero. There are two ways to solve it, 1. Pass the string in the form and decode it in the business 2. Pass the body。

Sorry, I confirmed it, and it is determined that form passing arrays is not supported in zero. There are two ways to solve it.

Pass the string in the form and decode it in the business.
Pass the body.

Thanks for your help again. I know how to get it to work. The only thing left to do is wait for an official fix.

目前 go-zero 是支持form 数组的，参考写法如下：
api 文件
articlesDelReq {
    ids []int `form:"ids,optional"`
}

对于 GET 方法，你可以通过如下格式访问：
http://{baseURL}{path}?ids=[1,2,3]
对于 POST 方法，你可以通过如下格式访问：
http://{baseURL}{path}

key
value

ids
[1,2,3]

最终，你将获取到 ids 为1,2,3的数组

Currently go-zero supports form arrays, the reference is as follows:
Api file

articlesDelReq {
    ids []int `form:"ids,optional"`
}

For HttpMethodGet, you can write as follows:
http://{baseURL}{path}?ids=[1,2,3]
And for HttpMethodPost, you can write as follows:
http://{baseURL}{path}

key
value

ids
[1,2,3]

Finally, you will get an array with ids 1, 2, 3


Fix for file system case sensitivity in FileSystemResourceAccessor.list

TL;DR: Fixes a regression in databaseChangeLog includeAll behavior on Windows after upgrading from Liquibase 3.5.0 to 3.5.3.
Note: I currently can't log in to liquibase.jira.com for some reason, so I'm referring to related JIRA issues here: this should fix CORE-2851 (and CORE-2898).

This was tricky to track down so I'm not surprised it was initially noted as "unable to reproduce".

if Liquibase is run from the command prompt in the working directory it would succeed
however, if Liquibase is run via CreateProcess and the working directory is specified

it would fail if the case of the working directory name did not match what Liquibase expects

Indeed I hit this issue because my process "shells out" to Liquibase via CreateProcess. After trial and error I managed to guess it was due to file system case sensitivity and reproduced the issue with the following PowerShell script:
$processStartInfo = New-Object System.Diagnostics.ProcessStartInfo
$processStartInfo.UseShellExecute = $false
$processStartInfo.CreateNoWindow = $false
$processStartInfo.WorkingDirectory = 'C:\TempWorkingFolder\Test'
$processStartInfo.FileName = 'java'
$processStartInfo.Arguments = '-cp ".;c:\Liquibase\liquibase.jar;c:\Liquibase\lib\snakeyaml-1.17.jar;c:\Liquibase\lib\sqljdbc42.jar" liquibase.integration.commandline.Main --driver="com.microsoft.sqlserver.jdbc.SQLServerDriver" --changeLogFile="Test/main.xml" --url="jdbc:sqlserver://mssql:1433;databaseName=Test" --username="username" --password="password" --defaultSchemaName="tx00000001" --logLevel="debug" update'
$process = [System.Diagnostics.Process]::Start($processStartInfo)
$process.WaitForExit()

The above will succeed as is, but will fail when the working directory is specified with different case, e.g.:
$processStartInfo.WorkingDirectory = 'c:\TempWorkingFolder\Test'

I had a look at the source changes between 3.5.0 and 3.5.3 and it seemed to be a regression in FileSystemResourceAccessor. I based my change on its base class AbstractResourceAccessor, which takes into account file system case sensitivity when stripping root paths.

Any news about this PR?

Not that I know of; this repo doesn't seem to be very active. 😞
( ... and I still can't log in to liquibase.jira.com to try other channels.)


API Review: CSI Inline Volume

Requesting review for API changes to implement support for the ability to nest CSI volume declarations within pod specs

KEP - CSI Inline Volume
PR - https://github.com/kubernetes/kubernetes/pull/74086
Submitter @vladimirvivien

/assign @liggitt

/sig storage

thanks for following the documented process... we're actually reworking that to make it simpler and take advantage of artifacts people are already setting up.
Your inline volume PR is assigned for review in https://github.com/orgs/kubernetes/projects/13#card-17727405 and you can follow the status updates in your PR


Flink Delta Source PR 11 - Partition support using Delta Log Metadata

PR Plan:

PR 5 - Option support in Bounded Mode - DONE
PR 6 - Continuous mode without monitoring for changes - DONE
PR 6.1 - Package Refactoring - DONE
PR 7 - Monitoring for changes in Continuous mode - DONE
PR 7.1 - More tests for PR 7 including IT case tests for Continuous mode. - DONE
PR 9 - Builder - DONE
PR 10 - Builder refactoring to extract Schema from Delta Log. - DONE
PR 10.1 - Tests for SourceUtils::buildSourceSchema, DeltaSourceBuilderBase::getSourceSchema and SnapshotSupplier implementations. - DONE
- PR 11 - Partition Support using Delta log to identify partition columns.
PR 12 - Get BATCH_SIZE for Format builder from Source options - this value is currently hardcoded. Add validation for option names and values including using not applicable options for given mode via generic option method.
PR 13 - Use new DeltaLog API getVersionAtOrAfterTimestamp for continuous getChanges call when using starting timestamp. This uses the "streaming" semantics of timestamp -> version conversion.
PR 14 - Additional IT tests including all options and end to end tests using Source and Sink.
future - continuous from version 0, handling Metadata & Protocol actions.

-- All functionalities are in place up to this point. The following PRs are extra tests, eventual bug fixes and code/javadoc adjustments. --
PR 11 - Annotate with @deprecated  Sink's builder methods that names starts from "with". Add new ones without "with" prefix and overload partitions with List argument for Sink.
While @kristoffSC is on vacation
@tdas + @scottsand-db to review public API
Once Krzysztof is back
README / docs
QA
end-to-end integration tests - using Sink to write, Source to read, etc.
more examples / migrate examples from internal flink module to examples folder
TODOs and other improvements planed as next:

Use index for keeping track of already processed paths in SnapshotProcessor - needs new Delta API.
Do do not create snapshot when streaming only changes (startingVersion or startingTimestamp option used). - needs new Delta API since for startingTimestamp we still need to create a snapshot. There is no API like deltaLog.getChangesFromTimestamp(....)
Refactor Test util classes to make them common for sink and source.
Re-visit Delta Standalone APIs for when the source see's metadata/protocol actions. Update ActionProcessor class to handle MetaData and Protocol Actions
Enhanced DeltaLog.java with a new method similaiar todeltaLog.getSnapshotForVersionAsOf() but for streaming mode. Use it in Delta Source connector for startingTimestamp option. -> https://github.com/delta-io/connectors/pull/346

Moved to delta.io


[CWS] implement rename event on windows

What does this PR do?
This PR implements rename event for windows, modeled on the linux version, and using the newly added etw events rename and renamePath
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Issue with tokenization in NLP

Hello All,
I am facing an issue with tokenization method. I google the issue but got no results kind help me in resolving the bug.

if you are passing a data frame, try this:
nlp.tokenize(cleanX)

Please refer to this notebook: https://github.com/Muhammad4hmed/GML/blob/master/DEMO/AutoTextClassification.ipynb

It is again throwing error

can you show me snap of your cleanX?

[image: image.png]
On Wed, 2 Dec 2020 at 21:15, Muhammad Ahmed<EMAIL_ADDRESS>wrote:

can you show me snap of your cleanX?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Muhammad4hmed/GML/issues/9#issuecomment-737470074,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARIK2NAJKCADZJBC63TM43DSS2N6TANCNFSM4UK5XYVQ
.

--
Best,
Aadil Gani Ganie

can't see it

Hi, This issue is because the text in the dataset is exceeding MAX_LEN. so you have to truncate your text.
I have written a function for you
MAX_LEN = 200

def trunc(text):
    text = str(text)
    if len(text) > MAX_LEN:
        return text[:MAX_LEN]
    return text

dataset['Text'] = dataset['Text'].apply(lambda x: trunc(x))

and after that, you can apply tokenization
tokenized = nlp.tokenize(dataset['Text'])

Closing this issue, assuming the problem is solved. feel free to reopen if you face any difficulty.


Transaction queue

[x] Create transaction pool
[x] Create transaction queue
[x] Prepare for transaction validation

Currently blocked, as it depends on Trie


Update bug_report.md

add majuscule and bold

every time I report a github error and specify that I'm on linux
I'm systematically asked which kernel I'm on.
so I automatically add it.
it's not a standard ?
neofetch has been installed on all basic distribs for several years.
and allows a non-expert to quickly give system information whatever the distribution.
what do you think? i try to have a user-friendly approach

unrelated but normally I sent you an email


Warnings in Chromium

Thank you for the excellent mode! It was easy to setup and in many cases it can replace mozrepl off the shelf.
One small observation at Chromium console:
'window.webkitStorageInfo' is deprecated. Please use 'navigator.webkitTemporaryStorage' or 'navigator.webkitPersistentStorage' instead. skewer:496
'webkitIndexedDB' is deprecated. Please use 'indexedDB' instead. skewer:496

I don't know what would cause this, because Skewer doesn't touch any
storage. Line 496 is also beyond the end of the default script. Perhaps
you have hook function on skewer-js-hook that's injecting more code?

It seems that those warnings only occur when doing autocompletion with ac-js2 mode with ac-js2-evaluate-calls set to t. The following is a screenshot of the chromium debugger window:

Apologie for the confusion - browser reports those warnings as they were comming from skewer - thus I reported it here :)

I see the issue. In ac-js2, obj is bound to window (or more generally the global object) and, to discover completions, it's mechanically touching all its keys, setting off the warnings.

Apologies for the confusion - browser reports those warnings as they were coming from skewer - thus I reported it here :)

No problem. I'd rather get a mistaken bug report than no bug report for a real bug.


Deprecate our CLI

Acceptance

[x] CLI deprecated on npm
[x] recommendation for using our Obsidian plugin


Organisation creation

In GitLab by @jasonpagetas on Jul 24, 2024, 03:24
Creation of new organisation and default teams within organisation via AWX

moved to nofusscomputing/infrastructure/configuration-management/inventory-config#1

made the issue confidential


[SPARK-7654][SQL] Move insertInto into reader/writer interface.

This one continues the work of https://github.com/apache/spark/pull/6216.

Merged build triggered.

Merged build started.

Merged build triggered.

Merged build started.

Test build #33380 has started for   PR 6366 at commit c636e35.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33377/
Test FAILed.

Test build #33380 has finished for   PR 6366 at commit c636e35.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33380/
Test FAILed.

Merged build triggered.

Merged build started.

Test build #33390 has started for   PR 6366 at commit 56d2540.

LGTM. Let's merge this once tests pass.

Test build #33390 has finished for   PR 6366 at commit 56d2540.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33390/
Test FAILed.

Merged build finished. Test FAILed.

Eh damn. R.

Test build #855 has started for   PR 6366 at commit 56d2540.

Merged build triggered.

Merged build started.

Test build #33413 has started for   PR 6366 at commit 3d717fb.

Test build #855 has finished for   PR 6366 at commit 56d2540.

This patch fails SparkR unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #33413 has finished for   PR 6366 at commit 3d717fb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins/job/SparkPullRequestBuilder/33413/
Test PASSed.

I am merging it to master and branch 1.4.


Update index.mdx

changed "which exposes convenience methods" to "that exposes convenient methods".

Duplicate PR #7 and #4


03/29/2018 06:51 : Create Pull Request for branch master -> prTesting1_2018032906

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef1.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Fix ImportError inside create_agent

Proposed changes:

Include the missing import for Agent inside the create_agent method.

Status (please check what you already did):

[x] made PR ready for code review
[ ] added some tests for the functionality
[ ] updated the documentation
[ ] updated the changelog
[ ] reformat files using black (please check Readme for instructions)

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Amogh Mannekote seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Closed because my email was set wrongly for the commit


Rest API endpoint to purge history of a document

Documents can get huge, mostly because of the history. This can lead to difficulties to open documents.
User-Story: As a document owner, I would like to purge or reduce the size of the history of a document in order to ease the document opening or to shrink the disk / storage usage for this document.

NB: there is a companion tool to purge the history:
https://github.com/gristlabs/grist-core/blob/c0ce791e285f6153a38f030bdc98e04eeb3971c8/app/server/companion.ts#L55-L67
However:

it is only available to the administrator hosting the Grist instance;
it's unclear whether the tool can be used in the context of multi-worker instance, with S3 storage backend;

There is also a /states/remove endpoint, not documented. You can see it being exercised here:
https://github.com/gristlabs/grist-core/blob/91e0a62e9127c44bea394ee007b0def30e3e38f1/test/server/lib/DocApi.ts#L3217-L3241

Thanks @paulfitz!
To fix this issue, I tend to think we may just document this API as well as GET /states/.
There could also be an enhancement to offer an option which limits the history size in another issue (so the docs don't get huge). WDYT?


Add HTTP header version converter

This removes dependency for http2 form http3 by moving their common code into proxy/hdrs/.
The logic is basically unchanged. Only trick I added is a switch to create (reserve) pseudo header fields on HTTPHdr initialization. If you pass HTTP_2_0 or HTTP_3_0 to the init function, MIMEFields for pseudo header fields will be added automatically to ensure those fields will be placed at the beginning of the header field list.

@bneradt Thank you for your feedback. I updated the code and added oxygen comments.

@bneradt I rebased the branch on top of the latest master to resolve conflicts. PTAL.

Looks good.


DevSim plugin: using wurlitzer prevents working on Windows

I am trying to use the devsim plugin on Windows, but wurlitzer is not available for Windows platforms (which is a known issue https://github.com/minrk/wurlitzer/issues/12).
Since it seems like it is only used to reduce text output, I suggest getting rid of the wurlitzer use or at least having checks in case someone is using Windows.

Hi Marc,
thank you for your feedback
i removed the wurlitzer dependency
wurlitzer


create app namespace

Changes Unknown when pulling 953b1ff117577bfbb3e84dc6ca32833051c493ef on lepdou:0613_17 into ** on ctripcorp:master**.

[Current coverage][cc-pull] is 42.97%
[][cc-pull]

No coverage report found for master at 0db0658.

Powered by Codecov. Last updated by [0db0658...953b1ff][cc-compare]
[cc-base-branch]: https://codecov.io/gh/ctripcorp/apollo/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/ctripcorp/apollo/compare/0db065844f53e861b6e3bdb9e1e7fc9083b6ce7c...953b1ff117577bfbb3e84dc6ca32833051c493ef
[cc-pull]: https://codecov.io/gh/ctripcorp/apollo/pull/270?src=pr


Sdk improve

I don't see a point in this PR. Shall we close it?

Merging. Please add Lazy/Cache for token details in following PR.


Error with Singularity

Hi,
I was wondering if anyone has encountered the error Command error: FATAL:   resolved path $WORK/.singularity/nfcore-rnaseq-1.4.2.img doesn't match with opened path $WORK/.singularity/nfcore-rnaseq-1.4.2.img (deleted) when running "rnaseq" with Singularity on a cluster?
I don't get this error every time though, just sometimes (usually the second time I run the command), and I haven't been able to figure out what is the reason for that.
The image exists in $WORK/.singularity when I see the error.
I use the following modules and variables:
module load singularity
module load nextflow
export NXF_SINGULARITY_CACHEDIR=$WORK/.singularity
export NXF_HOME=$WORK
export SINGULARITY_CACHEDIR=$WORK/.singularity

and the commands I have tried are:
nextflow run nf-core/rnaseq -r 1.4.2 -profile singularity --genome 'UMD3.1' --singleEnd --reads '*.fq.gz' -resume --max_cpus 16 --max_memory '100.GB' --max_time '168.h' -c nextflow.config

and
nextflow run nf-core/rnaseq -r 1.4.2 -with-singularity $WORK/.singularity/nfcore-rnaseq-1.4.2.img --genome 'UMD3.1' --singleEnd --reads '../*.fq.gz' -resume --max_cpus 16 --max_memory '100.GB' --max_time '168.h' -c nextflow.config

Both of them worked the first time, and usually give the error the second time they are executed (not resumed).
Is this a caching issue, and should I remove the cache after every run, or I am missing some additional configuration?
Any suggestions and possible ideas are highly appreciated!
Thank you,
Natasha

Hi Natasha!
thanks for opening the issue and letting us know about this problem. The cache shouldn't be removed after every run, that should be just fine. Can you elaborate on which singularity version you are using as well? The error seems indeed a bit odd to me, might need to think a bit more.
@nf-core/core anyone else has an idea?

Hi @apeltzer ,
Thank you for your reply!
We are using Singularity 3.5.3 on EL6. I do agree that the error seems odd - especially that it doesn't happen every time.
This is more detailed log from the latest run:
[49/50e8a9] process > output_documentation           [100%] 1 of 1, failed: 1 ✘
Error executing process > 'output_documentation'
Caused by:
  Process `output_documentation` terminated with an error exit status (255)
Command executed:
  markdown_to_html.r output.md results_description.html
Command exit status:
  255
Command output:
  (empty)
Command error:
  FATAL:   resolved path $WORK/.singularity/cache/oci-tmp/683625354fdcdefaad1a2710e4ba0517ac5316e47dddd6148aa8d685282a857b/rnaseq_1.4.2.sif doesn't match with opened path $WORK/.singularity/cache/oci-tmp/683625354fdcdefaad1a2710e4ba0517ac5316e47dddd6148aa8d685282a857b/rnaseq_1.4.2.sif (deleted)

I switched to using conda as a profile, and multiple runs of the same data worked fine. While using conda is a feasible and working solution for me, I am really curious to understand the reason behind the Singularity issue I encountered.
Thank you,
Natasha

Thank you Natasha for providing more feedback on this!
Could you maybe test if its e.g. always failing on the same node? We have a debug profile that you could run alongside to trace back if e.g. the singularity installation is broken on a specific node. Sounds a bit like searching for the needle in the haystack, but I've seen this and it could explain what happens here (e.g. bind paths for Singularity on one node were not correct in one case I remember from a while ago).
Simply use your command and add debug to it:
nextflow run nf-core/rnaseq.... -profile foobar,singularity,debug (or similar)
I'd also be interested in finding out what caused this - glad you shared your experience here.

I did a little bit more searching, and I found this https://github.com/hpcng/singularity/issues/3249#issuecomment-594885112.
Looks like this is a known issue with Singularity 3.5.* on EL6 systems that should be fixed in the newest 3.6 release.
Although using -with-singularity should have worked in this case, I do think the combination of Singularity and OS versions is the reason for the error I have observed.
@apeltzer , I really appreciate you looking into this error with me, and please feel free to close this issue.
Thank you,
Natasha

Thank you (!) for pointing us towards this issue & thereby resolving another issue we never got fixed (and we know now why!) 🥇
Thank you!
Alex

(I've linked from the other issue to this thread ... -> thanks for that super helpful link to Singularity :-))

Hah, I was not aware of the other issue, but I am glad that all unintentionally worked out :)


Error on proxy: Failed to read full, 0 != 2: EOF

Got this after the authentication passed, then the connection failed.

The error message appears when client closes connection. Could you give me some more informations like error messages on client/server and config file?

The error message appears when client closes connection. Could you give me some more informations like error messages on client/server and config file?

I was using softether l2tp which produced an openvpn config file using a udp port, so I got your code to make a tcp proxy for the udp openvpn in order not to setup the server again and it's easy to use the GUI of the softether management on Windows.  Only to find the problem that after the authentication, the connection closed. And I see that  the client closed first, then the proxy closed.  Tunnelblick 3.5.3 (build 4270.4371) is the openvpn client. Thanks.

2015-08-10 22:27:01 Authenticate/Decrypt packet error: bad packet ID (may be a replay): [ #473 ] -- see the man page entry for --no-replay and --replay-window for more info or silence this warning with --mute-replay-warnings
2015-08-10 22:27:01 Fatal decryption error (process_incoming_link), restarting
2015-08-10 22:27:01 SIGUSR1[soft,decryption-error] received, process restarting
2015-08-10 22:27:01 MANAGEMENT: >STATE:1439216821,RECONNECTING,decryption-error,,
2015-08-10 22:27:02 *Tunnelblick: No 'reconnecting.sh' script to execute
2015-08-10 22:27:02 MANAGEMENT: CMD 'hold release'
2015-08-10 22:27:02 WARNING: No server certificate verification method has been enabled.  See http://openvpn.net/howto.html#mitm for more info.


Badge links to vercel app domain

Why not link the badge to the vercel app URL?
Nice job btw!!!

Why not link the badge to the vercel app URL?
Nice job btw!!!

You can link by youself like this:


Replace lua-lsp with luals

lua-lsp is not currently maintained, there is luals  which can be used as an alternative

Tasks:

[x] Add luals & installation instructions to LanguageServers.md
[ ] Add configuration for luals to config.lua
[ ] Check that all commands work as expected (or at least as well as with lua-lsp)

[ ] hover
[ ] format
[ ] autocomplete
[ ] goto-definition

[ ] Change the default language server for Lua in config.lua

Tasks:

[x] Add luals & installation instructions to LanguageServers.md
[ ] Add default configuration for luals to config.lua
[x] Check that all commands work as expected (or at least as well as with lua-lsp)

[x] hover
[x] format
[x] autocomplete
[x] goto-definition

goto-declaration it's not supported

[ ] Change the default language server for Lua in config.lua


Update the readme to list/link to the correct .NET Core SDK

Merging this will update the readme prerequisite list to specify and link to .NET Core SDK 3.1

Currently if following the project's readme, you cannot build since 3.0 is documented, while 3.1 is required in global.json
Given netcore3.0 reached end of support March 2020, while netcore3.1 is an LTS this seems like the preferable SDK
See alternative PR: "Revert (mistaken?) change to .NET Core SDK on global.json"
Tested by running dotnet build with only 3.1.404, 5.0.100, 5.0.101 SDKs installed (ls '\Program Files\dotnet\sdk\')
Requirement changed in commit d1028d8fab1c94cffb7db89f9746298d51c4c8ea/2020-09-15

Thank you!

Thank you!

Most welcome :)

Most welcome :)


Add page.Store (a page.Scratch variant)

We currently have a page.Scratch as a scratch pad for each page.
This gets reset on server rebuilds, and that's not something we can/want change.
This has the unfortunate side effect that scratch values written to page in, say, a shortcode, is not visible on server rebuilds (unless the content is also rebuilt).
I have thought a fair amount on the above, and have concluded that the easiest is just to add a new method:
type ScratchProvider interface {
	// Scratch returns a Scratch that can be used to store temporary state.
	// Note that this Scratch gets reset on server rebuilds. See Store() for a variant that survives.
	Scratch() *maps.Scratch

	// Store returns a Scratch that can be used to store temporary state.
	// In contrast to Scratch(), this Scratch is not reset on server rebuilds.
	Store() *maps.Scratch
}

/cc @jmooring @regisphilibert

It's an edge case for me, so I'm not sure I can really help other than with naming.
But I wonder if this new method could be safe to reuse throughout the build. This would allow user to safely attach some information to a page and rely on it from any templates and through the rest of the build... See it as a way to complement a page, before in a near future we are able to create a page from data.
This is an addition I'd be excited about, but I suppose it relies on one ability to store this data at the earliest time in the build...


API and Implementations for Entity API.

Spawning of them will now create the correct entity classes.
Adds missing FallingBlock and PrimedTNT interfaces.
Adds missing Painting#setOrientation(Orientation).
Blaze now correctly inherits Flying.
PigZombie now correctly inherits Ageable.
Neutral is now in org.pocketserver.api.entity.living.
PigZombie is now in org.pocketserver.api.entity.living.neutral, as it is neutral.

:+1:

Failing because credentials are missing -- code is fine.

@nickrobson, please read issue #56, you don't have to update this PR.

@Serializator This isn't an API PR: It's an implementation one. Please read.

@Fireflies pls

danke


Enhance Table of Contents component with modern UX features

Overview
Improve our TOC component using industry best practices, inspired by Josh Comeau's blog implementation How I Built My Blog.
Key Inspiration Points from Josh's Implementation

Animated smooth highlighting
Progress indicator integration
Intelligent scroll position management
Optimized rendering approach

Technical Implementation
1. Smart Scroll Management
interface ScrollManager {
  threshold: number;
  offsets: {
    top: number;
    bottom: number;
  };
}

// Inspired by Josh's scroll mechanics
function getElementOffset(element: HTMLElement): number {
  const rect = element.getBoundingClientRect();
  const scrollTop = window.pageYOffset || document.documentElement.scrollTop;
  return rect.top + scrollTop;
}

2. Progress Indicator Component
'use client';

interface ProgressProps {
  progress: number;
  variant?: 'slim' | 'prominent';
}

const ProgressIndicator = ({ progress, variant = 'slim' }: ProgressProps) => {
  return (
    <div
      className="fixed top-0 left-0 w-full h-1 bg-gradient-to-r from-blue-500 to-purple-500 transform origin-left"
      style={{
        transform: `scaleX(${progress})`,
        transition: 'transform 150ms ease-out'
      }}
    />
  );
};

3. Enhanced TOC Component Structure
interface TableOfContentsProps {
  headings: Array<HeadingInfo>;
  maxDepth?: number;
  className?: string;
}

interface HeadingInfo {
  id: string;
  title: string;
  level: number;
  subheadings?: HeadingInfo[];
}

const TableOfContents: React.FC<TableOfContentsProps> = ({
  headings,
  maxDepth = 3,
  className
}) => {
  const [activeIds, setActiveIds] = useState<Set<string>>(new Set());
  const [progress, setProgress] = useState(0);

  // Implementation details...
};

Visual Design Updates
Desktop Layout
const desktopStyles = {
  wrapper: `
    hidden lg:block
    sticky top-24
    w-64 xl:w-72
    max-h-[calc(100vh-6rem)]
    overflow-y-auto
    scrollbar-thin scrollbar-track-transparent
    pr-4
  `,
  heading: `
    text-sm font-medium
    text-gray-400 dark:text-gray-500
    mb-4
  `,
  list: `
    space-y-2.5
    text-sm
  `,
};

Mobile Layout
const mobileStyles = {
  trigger: `
    fixed bottom-4 right-4
    z-50 p-3
    rounded-full
    bg-gradient-to-r from-blue-500 to-purple-500
    shadow-lg
    transform transition-transform
    active:scale-95
  `,
  panel: `
    fixed inset-y-0 right-0
    w-4/5 max-w-sm
    bg-white dark:bg-gray-900
    shadow-xl
    transform transition-transform
    translate-x-0
    p-6
  `,
};

Animations (Josh Comeau Style)
const SPRING_CONFIG = {
  tension: 170,
  friction: 26,
};

const transitions = {
  heading: {
    active: {
      color: 'var(--colors-primary)',
      transform: 'translateX(8px)',
    },
    inactive: {
      color: 'var(--colors-text)',
      transform: 'translateX(0px)',
    },
  },
};

Accessibility Improvements

Proper ARIA labels and roles:

const a11yProps = {
  nav: {
    'aria-label': 'Table of contents',
    role: 'navigation',
  },
  button: {
    'aria-expanded': isOpen,
    'aria-controls': 'toc-content',
  },
};

Keyboard navigation support:

function handleKeyboardNav(event: KeyboardEvent) {
  const { key } = event;

  if (key === 'ArrowDown' || key === 'ArrowUp') {
    event.preventDefault();
    // Navigate between headings
  }
}

Performance Optimizations

Implement virtual scrolling for long TOCs
Use CSS containment
Debounce scroll handlers
Memoize heading calculations

Additional Features from Josh's Blog

Reading time indicator
Section progress visualization
Smooth collapse/expand animations
Mobile-optimized touch interactions

Testing Strategy

Unit tests for scroll calculations
Visual regression tests for animations
Cross-browser compatibility
Mobile gesture testing
Accessibility testing with screen readers

Resources

Josh Comeau's Blog Implementation
Current TOC Implementation

Acceptance Criteria

Matches the smooth UX of Josh's implementation
Maintains performance with large articles
Works across all modern browsers
Perfect Lighthouse accessibility score
Smooth animations on both desktop and mobile

Priority: High

Can I work on this issue?

Can I work on this issue?

Yes

Yes I am working on it, can you please share some social link where I can inform you about  my progress

@suvasis-patra your email pls - I'll add you in Slack

<EMAIL_ADDRESS>

@suvasis-patra any updates here?

@nirnejak - see if you can pick up this or any other issue?

@tyaga001 will take a look

@tyaga001 will start this once https://github.com/tyaga001/devtoolsacademy/pull/53 is merged


Not working under WSL2 (tcgetpgrp failed: Not a tty)

Hi, there!
I just found this plugin and installed it via lazy.nvim
When I tried this plugin under the Powershell environment, everything works well, however when I entered the :PasteImage command under the WSL environment, following error occured (I got no idea on why the error output is not selectable so I have to take screenshot. There are also some character displaying issue might due to my system language):

I have also checked this issue https://github.com/ekickx/clipboard-image.nvim/issues/34, but it seems like not related.
Thanks for your help!

Hi, just switched to another device and get the correct displaying error output like below, hope it helps

Thanks!

I just modified the powershell command in the utils file to the following, which is simpler and avoids as many special characters.
cmd_check = 'powershell.exe "(Get-Clipboard -Format Image)"'
cmd_paste = 'powershell.exe "(Get-Clipboard -Format Image).save(' .. "'%s'" .. ')"'

That might actually be a neovim bug.  os.executue('powershell.exe /?'), causes the same issue...  Weird.

So may be two bugs.

Neovim wigging out - have no clue, can reproduce with os.execute.  Trying to reproduce without plugins....
tcgetgrp failed.  - May be a powershell path issue with using powershell from within WSL.  See the scrapy issues.

https://github.com/scrapy/scrapy/issues/4589

Did some more testing.  I disabled this plugin, and was able to reproduce some issues.  So likely some neovim issues to resolve lol.
This definitely fixed it completely not working though:
cmd_check = 'powershell.exe "(Get-Clipboard -Format Image)"'
cmd_paste = 'powershell.exe "(Get-Clipboard -Format Image).save(' .. "'%s'" .. ')"'
But when we use the "os.execute" within WSL right now, it causes some issues with Neovim.

I fixed powershell command and create PR. #44
and also you can create a PR as your great work.


loaded all actions for s3, and ec2

Coverage remained the same at 70.0% when pulling 2171a079a5e4b981e4210c47b2ff0d09227c70c8 on swethanaretla:EC2_custom_policy into 56e3895e4c5515d6cac316c68d82faa51fd7426a on MicroPyramid:master.

Coverage remained the same at 70.0% when pulling 977ffde82e0c6ca82aabbc4ec769386258374cbf on swethanaretla:EC2_custom_policy into 56e3895e4c5515d6cac316c68d82faa51fd7426a on MicroPyramid:master.


Can you set the pricing for a product?

Is this option available with the API?

@IronBrotherz could you please elaborate a bit more on what exactly you are trying to accomplish ?
Just setting an arbitrary price is not available on the client side as this would allow your visitors to change product prices for whatever they desire.

Closing as I don't think this is a Cart.js issue.


Add support for pyqt6

🚀 Feature
This is a request to replace pyqt6_experimental with just pyqt6 in setup.cfg, and update the docs appropriately to metnion the option of using pyqt6 when installing napari. It looks like QT6 support was tracked in https://github.com/napari/napari/issues/3880, which is now closed. So I guess this issue can be used to track any outstanding items specifically related to PyQT6?
Motivation

Pitch

Alternatives

Additional context

👍 - I updated the title of the issue so this can be used to track PyQT6 support in general

It looks like the test suite includes one pyqt6 run:
https://github.com/napari/napari/blob/d8dd1d2f592618064d2b5ac0c770ac1eb4741e77/.github/workflows/test_pull_requests.yml#L90-L92
Do you have an idea of what more needs to be done to complete pyqt6 support?

Do you have an idea of what more needs to be done to complete pyqt6 support?

A person playing dev with Installed Qt6 backend and checking if something crashes.
We have plan to release 0.5.0 with qt6 marked as experimental. Call people for testing. Fix the bugs and release 0.5.1 as qt6 ready

If we do this I think we should say >6.5
to cover this issue: https://github.com/napari/napari/issues/5644


Impossible to reach the current comment in issue

Question
Response

Version?
current testing

Devices tested?
BlackBerry Passport

What Currently Happens?
Infinite scrolling in that issue:
https://github.com/golang/go/issues/21161
What Do You Expect To Happen?
To reach the bottom. So, the most fresh post.
My Reproduction Steps
Went into that issue, try to scale down.

Hi @ShalokShalom !
Your issue description is a bit cryptic.. is the issue that you can only see the first comments? (last visible one being from opennota 9 months ago)
If that's it, then this will be fixed soon as we're currently in the process of migrating to GraphQL, where will be able to show all the comments & events on the issue, even when there are tons of them.
I'm not really found of infinite scrolling for issues, as sometimes you just want to see how the discussions ended, without having to scroll pages of pages of comments.
I find the way github web deals with this really neat: https://github.com/npm/registry/issues/255
They show a few comments from the beggining, a few from the end, and the User needs to click to load more comments:

What would you think if we mimicked this UX?

To be honest, I think this approach from Github can get easily skipped.
If you do that, then much more visible.

I totally see what you mean, as I didn't see it twice while looking for it to take the screenshot 😆
We'll make sure it's way more visible.
Keeping this issue opened as the problem isn't solved yet.

Ah, I thought this is tracked anywhere else


AZ naming gotcha example

Adding example to explain AZ naming as it was confusing to understand :

the letters are assigned to physical AZs randomly per account

Thanks. I'm not convinced the AZ example is needed. It's a much longer way to say the same thing, and also it could be confusing as that region adds zones.
Closing for now but open to discuss if you think of a smaller change or explain what's unclear?


feat: Update Docker image to ubuntu:24.10

@yxxhero Why did you upgrade to a non-LTS version now?
https://ubuntu.com/about/release-cycle

@pathob because of the ci error.


fix typo

there position to their position

closing as it will be part of https://github.com/apache/cassandra/pull/2062


11436 Added Expandable Help component, story, test suite

Issue #: bcgov/entity#11436
Description of changes:

rebuilt main package-lock.json
added Expandable Help component, story, test suite
updated Storybook

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the business-filings-ui license (Apache 2.0).

In Storybook:


Bail early if --diff is not used with correct arguments of 2 existing files

VSCode Version: 0.10.12-alpha
OS Version: Windows 10

Steps to Reproduce:

code --diff file1 file2 where file2 doesn't exist

Code opens with the second file empty in a dirty buffer. I can't see any use case for this. I think a better behavior would be to show a dialog that the second file doesn't exist.

I decided to just open an empty workspace in this case. The issue with showing 2 dirty files should be fixed by that.


Fix constant request of omitted textures

If you omit a texture manually, the tool will keep asking about it regardless. Fix it.

Fixed in bd5b609.


[FLINK-1681] Remove Record API from jdbc module

LGTM

To be more precise, this addresses: FLINK-2005

Merging (with updated commit message)


Source code 1.50 beta 3b - Missing text

Hi,
I realized you used the latest PDFSharp source, and merged code from https://github.com/roceh/PdfSharp.Xamarin and https://github.com/groege/PdfSharpCore
which obviously is fine (though i think it would be nice to mention roceh in your project, since he did the bulk of the code changes needed for portability...), but in my repo "https://github.com/groege/PdfSharpCore" if found out, that when I try to print to a Kyocera printer from an Android phone, depending on how I try to print it, text might be missing or it won't print at all (the preview was fine though - it seems to be an issue with the print script...).
The same issue happened in older versions of the original PDFSharp as well.
Do you think this is fixed with your project? Do you have any time to try it out or send me a Pdf, created by your project, that I can try to print?

Hey @groege,
Thanks for reminding about the licenses! I'm pushing the license attribution fixes in a few minutes, still very much a work in progress as targeting .NET Standard 2.0 was more painful than I initially thought. :)
Could you create a separate issue for the printing part, so I can see if I can test it and get it working? Also is it only on Android & Kyocera, or just printing in general?
There seems to be quite a lot that's broken, including encryption support, but I'm fairly sure those are fixable on way or another. Right now I'm concentrating on getting the library working in both .NET Standard and Core projects, as well as writing unit tests for all core features of PDFSharp.

No problem ;)
I actually found a Solution for the printing part - it's not a bug of PdfSharp!
The the problem lies with printing drivers.
I implemented a printing function for UWP (works wonderfully on Windows Phone 10) which works on Kyocera.
For Android, if the printer driver doesn't work properly with your Pdf,  you can just install "Let's Print  Droid" and "Let's Print Pdf", which can be used in place of the Vendors drivers (those two apps actually try to find the proper protocol to send the data to the printer, in my case i think it converts the pdf to postscript which then can be printed properly instead of sending the pdf which isnt' fully supported on the printer. If you want a more specific description on how to make it work, you can always ask ;) )
So now I can print on Windows Phone as well as Android without issues - without changing the code.

Ahh, thanks, that'll come in handy later! :)


README: compiling and execution: add instructions for Windows

The current instructions work for Linux (and FreeBSD I reckon). Which would be the preferred path to do the same on Windows?

Using WSL2.
Using VMWare or VirtualBox.
Using just Windows tools and install Qemu on Windows.

WSL2 should work just fine.

Confirmed compiling and executing works on WSL2/Ubuntu.


Migrate OTEL contrib packages to separate plugins

Description of change

Move plugin/service -> plugin/common
Migrate OTEL contrib packages to separate plugins

Checklist

[ ] Tested in playground or other setup
[ ] Screenshot (Grafana) from playground added to PR for 15+ minute run
[ ] Documentation is changed or added
[ ] Tests and/or benchmarks are included
[ ] Breaking changes

This change is

Closing the PR because @krdln is looking into this task.


Docs: Update for certs

@VijayRod : Thanks for your contribution! The author, @rothja, has been notified to review your proposed change.

@VijayRod Thank you! #sign-off


space is required on new line in the repl

I was testing new lines in the REPL and found something worth mentioning. Maybe it is a  bug or room for improvement? At least I could not find the root cause without the awesome help of the slack channel - thank you ilias! https://elmlang.slack.com/team/ilias https://elmlang.slack.com/archives/beginners/p1488263240033090
> isNeg n = \
| n<0
-- SYNTAX PROBLEM -------------------------------------------- repl-temp-000.elm

The = operator is reserved for defining variables. Maybe you want == instead? Or

maybe you are defining a variable, but there is whitespace before it?

3|   isNeg n =
             ^
Maybe <http://elm-lang.org/docs/syntax> can help you figure it out.

I checked, sorry, nope
> isNeg n = \
|  n<0
<function> : number -> Bool

This works
All this was tested on elm 0.18, Windows cmd.exe started with elm-repl
I'm happy to assist in any kind for the triage of this bug!

Hi, I encountered this error too, and after some searching, I found that you need to add a space at your 2nd line for it to work.
Example:
isNeg n =
|(add space here) n < 0

Confirmed

One easy way to prevent people running into this would be to mention that you need to add a space to each new line in the getting started guide. In the Core Language section in the following paragraph:
"Using a backslash in the REPL lets us split things on to multiple lines. We use this in the definition of over9000 above. Furthermore, it is best practice to always bring the body of a function down a line. It makes things a lot more uniform and easy to read, so you want to do this with all the functions and values you define in normal code."


Add automated task retrying

 Issue by thieman
Thursday Jul 11, 2013 at 19:42 GMT
Originally opened as https://github.com/thieman/dagobah/issues/20

Some tasks have a tendency to break (I am thinking specifically of data processes reliant on shaky third party APIs) but it may be difficult to properly account for all of the potential errors ahead of time and make sure your task can survive it. In this situation, it can be helpful for Dagobah to automatically retry your job up to a certain number of times before giving up and declaring the task a failure.
I think we need to do three things:

Add a user-configurable maximum number of times to retry a Task, set at the Task level
Add a property on the Task object that tracks how many times the Task was retried during its last run. This will end up in the run log.
Patch the existing email templates to show task retries.

 Comment by Heinoman
Thursday Apr 19, 2018 at 09:23 GMT

Is there any progress on this issue yet?

 Comment by thieman
Thursday Apr 19, 2018 at 16:36 GMT

I am not aware of any work. I personally am no longer contributing to this project, any work is probably being done on forks.


[state sync] handle upstream peers in different networks and add fail…

…over logic
Summary
Before this PR, in state sync, upstream peers in different networks were treated equally in terms of requesting syncs.
This PR adds network preference logic for selecting the upstream peer to request syncs from:

select the peer from the highest-pref'ed network (defined by UpstreamConfig) with any live peers
selecting a peer from a set of active peers in the same network will be based on peer score

Notes:

before, each call to PeerManager::pick_peer was iterating through the entire peer set. This PR makes peer-picking more efficient by removing that extra iteration by persisting eligible_peers in PeerManager , which is only updated whenever a peer is added/lost or when a meaningful score change happens.

Test Plan
new/existing tests

@bors-libra r=zekun000

:pushpin: Commit 589d607 has been approved by zekun000

:hourglass: Testing commit 589d6071e11fe58cc40318796ab2b860eac6142f with merge 599db9a02c50ef4ca9adf9693284f7ce40b408e7...

:sunny: Test successful - checks-actions_land_blocking_test, checks-circle_commit_workflow
Approved by: zekun000
Pushing 599db9a02c50ef4ca9adf9693284f7ce40b408e7 to master...


Update flyway-core to 7.9.0

Updates org.flywaydb:flyway-core from 7.8.2 to 7.9.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.flywaydb", artifactId = "flyway-core" } ]

labels: library-update, semver-minor

Superseded by #137.


use dash flag with webm

Per Howler.js format recommendations, adding dash flag to WebM output configuration in order to encode WebM files with cues element for optimal seekability in Firefox.

Would love tests for this but I think this is fine for now. I might change this later.


Remove references to 14 on the typography scale from guidance

What
Review and remove references to 14 on the typography scale from guidance on the website. There are currently 2 references to 14 on the website:

The font size override classes
The typography section of how to translate govuk-frontend-toolkit mixins to govuk-frontend

Why
As part of https://github.com/alphagov/govuk-design-system/issues/2289, we should consider iterating our guidance to no longer recommend 14 on the font scale in anticipation of it's removal from govuk-frontend. We would need to do this anyway, but there's potentially an opportunity to do some of it sooner.
Who needs to work on this
The team?
Who needs to review this
Content designers
Done when

[ ] Assess if we should remove the above listed instances
[ ] Make changes to the website (if necessary)
[ ] Let the community know (if necessary)

The general feeling from the team at the moment:

The first instance seems very non-controversial to remove
The second instance is trickier as it means 4.X users moving a project off of frontend toolkit now don't have an alternative if they are trying to translate a project that used one of the 14px mixins. There's an unknown weighting here around how much grief this would cause given that we're removing compatibility mode in 5.0. A potential compromise is having a paragraph above the advising users that 14 isn't a recommended font size and to use 16 instead.


Update note permissions for Code Counselors

What issue is this solving?

Closes #125
Description

Remove old permission check inside of the addnote and notes commands
and update them to the new permission handler.
Remove old SU permission and replace with Code Counselor perms.

Any helpful knowledge/context for the reviewer?

Is a re-seeding of the database necessary? NO

Any new dependencies to install? NO

Any special requirements to test? YES

⚠ The best way to test this is to take away all your alt account's roles and then give it (one at a time) Forums Super User or Code Counselor roles.  Then have your alt try to add/view notes on your main account.
The Alt should not be able to do this when it has the FSU role (it will receive the message that it does not have the permissions)
The alt should be able to add/view notes as a Code Counselor, but it can't add notes to a staff member, so it will say that.  That's okay. So long as it doesn't give the permission error about using the command then it's working.

Please make sure you've attempted to meet the following coding standards

[x] Code has been tested and does not produce errors
[x] Code is readable and formatted
[x] There isn't any unnecessary commented-out code

@Vic-ST I think you should actually be able to get rid of your Admin role and still use Admin-only bot commands with the new permissions handler.  It checks that your highest role is higher than the minimum role needed, and Super Admin is higher than all of the others.
See https://github.com/CodecademyCommunity/codecademy-discord-bot/blob/dev/handlers/permissionHandlers.js for more details.

I just realized that we don't currently prevent notes from being added to Super Admins unless they have one of the other immune roles (Admin, Mod, CoCo, FSU), so that's something else we need to edit as well.


API call to cancel an ongoing execution

Currently, there is no way to cancel an ongoing execution. For example, if a step is taking too long, there is a long loop etc. the execution will continue at the background. The only viable option now is to restart SOARCA which is not the desirable behavior

Hi @antonatos, we have been busy from our side. However, I will discuss with the other Devs (@MaartendeKruijf, @lucamrgs ). How high this features is on our priority list.


Rename and relocate Draw Minimap editor property

This is more consistent with other properties, as per #31631.
Show Minimap is now in the Open Scripts tab as it is not technically related to line numbers.

There are quite a few other settings in the line_numbers category which don't have much to do with line numbers, this could be worth cleaning up.
Not sure the API should be changed, for the editor options "Show Minimap" makes sense and is consistent with other options, but from an API perspective, it's meaningful to make clear that it's not just about "showing" something at no cost, but enables drawing something that can impact performance.

Not sure the API should be changed, for the editor options "Show Minimap" makes sense and is consistent with other options, but from an API perspective, it's meaningful to make clear that it's not just about "showing" something at no cost, but enables drawing something that can impact performance.

Should I keep "draw" internally and only change the name to "Show" in the editor settings then?

There are quite a few other settings in the line_numbers category which don't have much to do with line numbers, this could be worth cleaning up.

I must say I'm not too sure which settings should be moved, gutters are not strictly related to line numbers but are displayed next to them, code folding and word wrap make sense as they can cause line numbers to change, and that leaves the line length guildeline, which is indeed unrelated to line numbers (unless it could automatically trigger word wrap, which it doesn't).

Should I keep "draw" internally and only change the name to "Show" in the editor settings then?

That sounds fine to me, for all intensive purposes the minimap implementation follows the exact same pattern as line numbers, breakpoints etc, they all use "draw" internally.
As for where it belongs, I think renaming the category to something more general then "Line Numbers" such as "Appearance" / "Display"? should be okay.

I reverted to simply renaming the editor option "Show Minimap", and had another look at the "Line Numbers" and "Open Scripts" categories. I would suggest that Open Scripts only contain settings about the open scripts list (which I believe is its original purpose), so settings related to scroll could go into the Appearance category, which would be the new name for the Line Numbers category.

"Appearance" seems consistent with what the Kate editor uses for some of those settings:

They also have "Editing Options" for some other settings which overlap with ours.

The current proposal is already a clear improvement so we could merge as is. I feel that there's still room for improvement though.
One idea could be to have a "Navigation" category for the scrolling and minimap settings.

"Open scripts" could maybe be renamed to "Script list" to reduce the confusion, and make clear that it's about the left-side panel listing scripts and optional bottom section with a list of member functions of the selected script?

I agree on both points, this makes things clearer.
I just have one problem, after making the changes, I have some leftovers: vertical scroll is still in the Appearance category, and all but one setting from the Open Scripts category is still visible in said category, even though I renamed the category to Script List (so I have duplicate entries). I manually removed these entries from my editor settings file, but I don't know how to handle these from code, any idea?

Looks good to me, could you squash commits together?

I just have one problem, after making the changes, I have some leftovers: vertical scroll is still in the Appearance category, and all but one setting from the Open Scripts category is still visible in said category, even though I renamed the category to Script List (so I have duplicate entries). I manually removed these entries from my editor settings file, but I don't know how to handle these from code, any idea?

That's normal, previous values are indeed kept for settings even if they are removed from older versions. This is mostly a legacy thing, but it also enables using the same editor config for different releases even if setting names changed.

Thanks!