How do you use these?

So how do you use these? As I mentioned in https://github.com/emacs-lsp/lsp-docker/issues/34 I've created a script that does a docker run that mounts in a root directory at the same location in the image, sets the effective user/group to the same as the current user (to avoid file permission issues, passes select env vars ($HOME, $USER, $USERNAME and $LOGNAME so far), sets the working directory to the same as the script was run in and ensures the entrypoint is the same command.
This means that lsp-mode, flycheck and for that matter the command line thinks they're just running the usual binary. Though, I've implemented a bit of hackery in order to support commands that open a TCP port.
This has been working well for me, with some fiddling with some oddballs.

So I've been using this by first building the elixir-ls image by running
$ docker build -t elixir-ls:1.10 -f Dockerfile.elixir-ls-1.10 .

and then I put this in my Emacs init:
;; Set up LSP Docker
(add-to-list 'load-path "~/src/elisp/lsp-docker")
(load-library "lsp-docker")

(with-eval-after-load "lsp-elixir"
  (lsp-docker-init-clients
   :path-mappings '(("/home/aidan/src" . "/projects"))
   :client-configs '((:server-id elixir-ls
                      :docker-server-id elixirls-docker:1-10
                      :docker-image-id "elixir-ls:1.10"
                      :docker-container-name "lsp-elixir-container"
                      :server-command "language_server.sh"))))

;; Specify which projects should use which LSP clients.
(dir-locals-set-class-variables 'elixirls-docker:1-10
  '((nil . ((lsp-enabled-clients . (elixirls-docker:1-10))
            (eval . (add-hook 'elixir-mode-hook #'lsp))))))

(dir-locals-set-directory-class
 "/home/aidan/src/blah" 'elixirls-docker:1-10)

I didn't get as far as setting the effective UID and GID to avoid permission issues, so the .elixir_ls directory in my project directory is owned by root:root, but that should be easy to fix.

Ah, right, defining a new server. Seems an awful lot of boilerplate to me. My script only needs two lines in the simplest case:
  docker-langserver:
    image: rcjsuen/docker-langserver:latest

But there's some overlap in the Dockerfiles used. Take this I made for css-language-server as an example:
FROM node:current-alpine

RUN npm install -g vscode-css-languageserver-bin

ENTRYPOINT ["/usr/local/bin/css-languageserver"]

The noteworthy part is that i set the entrypoint to be the server in question, so doing a docker run on the image runs the server. So basically it's a "plug in replacement" for the original command. I hope that lsp-docker could benefit from that pattern to?
I discovered a challenge: Language servers that listens on a port. Default lsp expects to be able to connect to localhost to connect to the port, but unless you tell docker otherwise it wont map the ports per default. I have some hackery to deal with this, but I don't know how lsp-docker deals with it?

I ran into trouble with elixir-ls, with stdio breaking when run under docker.  (This language server uses stdio instead of a socket.)  When I asked about this in the Emacs LSP discord server, lsp-docker was recommended to me instead of trying to get the language server working with just plain lsp.el.  I would much rather be able to use language servers transparently, by somehow making the dockerised language servers completely completely transparent to the client, which would also allow the effort put into this repo to be reused by other clients.

This morning I just added a Makefile for building the images.  I will try to write up a README soon, and then hopefully this repo will look more inviting to potential contributors.

So I am no longer using lsp-docker.

Maybe you'd be interested in my script then. I've just pushed it to https://github.com/xendk/rid. The README is sparse at the moment (as there's only been one user), and I still have some things planned (automatic building of images for instance), but I'm using it on a daily basis.
I have some images I should stick somewhere.

Cool!  I've added a README and mentioned rid in it.  You're welcome to submit a PR with your images if you think they're generic enough to use with any LSP client.

Oh, thanks.
I have a few images i could add (bash, css and typescript language servers), but how do you feel about versioning? My images just builds the latest version. I think for most language servers that makes sense.

I think just build the latest version unless there is a reason to build older versions is fine.  The elixir-ls images actually fetch the latest version of the language server, but with for two different versions of Elixir, because I have a project that's tied to Elixir 1.10 (the previous release), because of some dependencies that have not updated for Elixir 1.11.  I can't imagine this being an issue with either Bash or CSS, for example.

Sounds like an excellent plan.
How about moving the elixir related files into a elixir directory and renaming the dockerfiles Dockerfile.1.10 etc? I'd do a PR, but I don't think my Makefile-fu is strong enough for fixing the Makefile.

I've openend #4 to get the ball rolling, I have a few more language
servers lying around, but I need to get to bed early today (far too
long since that happenend).
Off topic: And so nice opening PRs entirely from inside Emacs.

Great!  I think further discussion can move there (and to new tickets).


Revise consolidated Code_of_Conduct document

After reviewing the CNCF code of conduct, I updated OpenEBS Code of conduct to link to CNCF doc


Wait for IPv6 default route to be configured

This polls for a default IPv6 route before it considers IPv6 "ready"

It also removes DAD, because "we" enforce DAD via our assignment scheme.


Config arbitrary_types_allowed=True not respected for numpy.ndarray in Pydantic dataclasses

Initial Checks

[X] I have searched GitHub for a duplicate issue and I'm sure this is something new
[X] I have searched Google & StackOverflow for a solution and couldn't find anything
[X] I have read and followed the docs and still think this is a bug
[X] I am confident that the issue is with pydantic  (not my code, or another library in the ecosystem like FastAPI or mypy)

Description
I am trying to use Pydantic's dataclass in my codebase.
I have one dataclass in which the datatype of one of the attributes is np.ndarray.
I am using arbitrary_types_allowed as True but still it is throwing error as
RuntimeError: no validator found for <class 'numpy.ndarray'>, see `arbitrary_types_allowed` in Config

The scope of my use case is limited to just validating that the type of this particular attribute is always np.ndarray only and not anything else.
Example Code
from pydantic.dataclasses import dataclass
from pydantic import Field
import numpy as np

@dataclass
class MyDataclass:
    my_array: np.ndarray = Field(default_factory=lambda: np.zeros([10, 10]))

    class Config:
        arbitrary_types_allowed = True

Python, Pydantic & OS Version
pydantic version: 1.9.0
pydantic compiled: True
install path: /opt/anaconda3/envs/llm-env/lib/python3.8/site-packages/pydantic
python version: 3.8.12 (default, Oct 12 2021, 06:23:56)  [Clang 10.0.0 ]
platform: macOS-10.16-x86_64-i386-64bit
optional deps. installed: ['typing-extensions']

Affected Components

[ ] Compatibility between releases
[ ] Data validation/parsing
[ ] Data serialization - .dict() and .json()
[ ] JSON Schema
[X] Dataclasses
[ ] Model Config
[x] Field Types - adding or changing a particular data type
[ ] Function validation decorator
[ ] Generic Models
[ ] Other Model behaviour - construct(), pickling, private attributes, ORM mode
[ ] Settings Management
[ ] Plugins and integration with other tools - mypy, FastAPI, python-devtools, Hypothesis, VS Code, PyCharm, etc.

Config is passed as kwarg for dataclasses

Thanks!
Apologies for missing this important detail.
Linking the reference for the same here: https://pydantic-docs.helpmanual.io/usage/model_config/


Added video tutorial

Salam,
I just added a video tutorial on how to use Appz📱, I hope I will add videos for all Kitz ..

This is great, thanks!

@Mazyod You are welcome.


Cannot run eWasm example on Burrow [EEI not supported]

Describe the Bug
When deploying the example contract foobar.sol on burrow using solang, which compiles the contract down to ewasm, we encounter the following problem of unknown EEI imports, specifically, the EEI of getCallValue. The error message is as follows:
executing deploy with command line:
burrow deploy --wasm --jobs=100 --chain=<IP_ADDRESS>:20997 --keys=<IP_ADDRESS>:20997    --address Full_0 --mempool-signing --set key2_addr=B45A407C2EBD15989DC8AB83284B31B0B6FB7C10 --set addr2_pub=860AD13F2223C22DDECEAD7C97191CC52B8F0A858527FA17FE5DC85D7F1520A8 --set key1=Full_0 --set key2=Participant_0 --proposal-create test-ewasm*/deploy.yaml
log_channel=Info message="Using chain" Chain=<IP_ADDRESS>:20997 Signer=<IP_ADDRESS>:20997
log_channel=Info message="Loading Playbook File."
log_channel=Info message="Loading playbook file" path=/Users/dshe/go/src/github.com/hyperledger/burrow/tests/jobs_fixtures/test-ewasm filename=/Users/dshe/go/src/github.com/hyperledger/burrow/tests/jobs_fixtures/test-ewasm/deploy.yaml
log_channel=Info message="*****Executing Job*****" JobName=defaultAddr Type=Account
log_channel=Info message="Setting Account" account=Full_0
log_channel=Info message="*****Executing Job*****" JobName=key2_addr Type=Set
log_channel=Info message="Setting Variable" result=B45A407C2EBD15989DC8AB83284B31B0B6FB7C10
log_channel=Info message="*****Executing Job*****" JobName=addr2_pub Type=Set
log_channel=Info message="Setting Variable" result=860AD13F2223C22DDECEAD7C97191CC52B8F0A858527FA17FE5DC85D7F1520A8
log_channel=Info message="*****Executing Job*****" JobName=key1 Type=Set
log_channel=Info message="Setting Variable" result=Full_0
log_channel=Info message="*****Executing Job*****" JobName=key2 Type=Set
log_channel=Info message="Setting Variable" result=Participant_0
log_channel=Info message="*****Executing Job*****" JobName=deployFoobar Type=Deploy
log_channel=Info message="Contract path" path=foobar.sol
log_channel=Info message="Warning during contract compilation" warning="foobar.sol:8:5-11:0: warning: function declared can be declared ‘view’"
log_channel=Info message="Saving Binary" contract=foobar
log_channel=Info message="Using keys server" server=<IP_ADDRESS>:20997
log_channel=Info message="Using mempool signing"
log_channel=Info message="There has been an error talking to your Burrow chain" defAddr=C9F239591C593CB8EE192B0009C6A0F2C9F8D768 rawErr="rpc error: code = Unknown desc = error 16 - Error 16: execution aborted: exception during transaction execution: call error: ewasm: unknown function getCallValue"
ERROR: Error finalizing contract deploy foobar.sol:
There has been an error talking to your Burrow chain using account C9F239591C593CB8EE192B0009C6A0F2C9F8D768.

rpc error: code = Unknown desc = error 16 - Error 16: execution aborted: exception during transaction execution: call error: ewasm: unknown function getCallValue

log_channel=Info message="JOBS THAT FAILED" count=1
log_channel=Info message="Playbook result" jobNo=0 file=test-ewasm/deploy.yaml error="Error finalizing contract deploy foobar.sol: \nThere has been an error talking to your Burrow chain using account C9F239591C593CB8EE192B0009C6A0F2C9F8D768.\n\nrpc error: code = Unknown desc = error 16 - Error 16: execution aborted: exception during transaction execution: call error: ewasm: unknown function getCallValue\n\n" time=570.143803ms
Cleaning up...
Killing burrow with PID 17351
Waiting for burrow to shutdown...

Tests complete. Tests are Red. :(
Failures in:
not supplied by test

To Reproduce

Make new test directory ewasm-test under tests/jobs_fixtures and add test files deploy.yaml and foobar.sol, which are examples obtainable from Burrow's official website for wasm support
Add --wasm in deploy_cmd in deploy.sh.
Run ./deploy.sh ewasm-test.

Expected Behavior
The example contract foobar should be deployable without bugs, and we should be able to interact with the contract using burrow.
Technical Details

[ 98458787aa8f92d2d4b7b4b431df985dde7bfa5c] Burrow Version (docker image tag or branch if built from source)
[1.14 ] Go Version (if applicable)
[ ] Docker Version (if applicable)
[ macOS Catalina 10.15.5] Operating System (osx/windows/linux)
[0.1.2] solang compiler

Additional Context
After discussion with @dshe-certik who ran the tests and discovered this bug, we think the crux of this bug is this excerpt of the error message below:
rpc error: code = Unknown desc = error 16 - Error 16: execution aborted: exception during transaction execution: call error: ewasm: unknown function getCallValue

which says that the getCallValue function is unknown, but in the eWasm specification it states that this function is a part of the Ethereum Environment Interface (EEI). And EEIs are supposed to be supported by the VM, which in this case would be burrow's VM. And if we inspect the decompiled WebAssembly text version of the contract foobar.sol, we notice the following:
(module
  (type (;0;) (func))
  (type (;1;) (func (param i32) (result i32)))
  (type (;2;) (func (param i32 i64 i64 i32)))
  (type (;3;) (func (param i32)))
  (type (;4;) (func (param i32 i32)))
  (type (;5;) (func (result i32)))
  (type (;6;) (func (param i32 i32 i32)))
  (import "ethereum" "getCallValue" (func (;0;) (type 3)))
  (import "ethereum" "revert" (func (;1;) (type 4)))
  (import "ethereum" "getCodeSize" (func (;2;) (type 5)))
  (import "ethereum" "codeCopy" (func (;3;) (type 6)))
  (import "ethereum" "finish" (func (;4;) (type 4)))
  (import "ethereum" "memory" (memory (;0;) 2 2))
 .....

that the function getCallValue is the first EEI to be imported. So is it that all the EEIs are not supported at the moment? Or the bug is with the way we run the tests?

Solang has implemented value transfers and needs to check whether value is sent to non-payable functions, and revert the transaction if its. functions are non-payable in Solidity unless marked with payable.

IOW use latest master


Is there a way how to get all markers on specific cluster click ?

This is an support issue that doesn't represent a bug or a concrete feature request, so I'm closing this issue. Feel free to chat below or use the official chat room on Gitter: https://gitter.im/SebastianM/angular2-google-maps


[$500] IOU-Markdown applied is displayed as text without markdown in IOU preview

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 1.4.14-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:

Go to https://staging.new.expensify.com/
Tap on a 1:1 chat
Tap request money--- manual
Enter an amount and tap next
Enter markdown text eg 456 in description
Tap request
Tap on IOU created

Expected Result:
Markdown applied must be displayed in IOU preview.
Actual Result:
Markdown applied is not displayed in IOU preview. The text with markdown applied in IOU description is shown in IOU preview as text without markdown applied.
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/Expensify/App/assets/115492554/486b4c37-f8bb-4ec7-9ec3-878305094888

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~018df7a4462e491a32
Upwork Job ID:<PHONE_NUMBER>338143232
Last Price Increase: 2023-12-20

Proposal
Please re-state the problem that we are trying to solve in this issue.
The issue is that when Markdown is applied, it appears as plain text in the IOU preview without rendering the Markdown formatting.
What is the root cause of that problem?
We are not checking either description is simple text or in Markdown format. We are displaying it as plain text for simple text and markdown format, that's why markdown format also shown as a plain text. As you can see here.
https://github.com/Expensify/App/blob/c09a3fead81512a4b01ccafff4c736301e0dbe89/src/components/ReportActionItem/MoneyRequestPreview.js#L331
What changes do you think we should make in order to solve the problem?
Here is the code which is responsible to display description in IOU Preview
https://github.com/Expensify/App/blob/c09a3fead81512a4b01ccafff4c736301e0dbe89/src/components/ReportActionItem/MoneyRequestPreview.js#L330-L332

Firstly, we need to check whether we should display the description or not.
If we have to display description then we have to check is it a plain text or markdown format
if markdown format then parse the markdown text and convert it into HTML then display as HTML.
Otherwise it is plain text

What alternative solutions did you explore? (Optional)
Instead of checking each component/page individually for whether it is in plain text or Markdown format, we can implement this logic inside the Text component. This way, it will automatically check if the input text is plain text and display it as is, or if it is in Markdown format, parse and display it as HTML. This approach eliminates the need to repeatedly write these conditions.

For reference sake, parsing description text was removed in this issue so that special characters like < aren't converted to &lt.

https://github.com/Expensify/App/issues/19386#issuecomment-1562946387

That was accomplished in this PR.

https://github.com/Expensify/App/pull/19868

Contributor details
Your Expensify account email<EMAIL_ADDRESS>Upwork Profile Link: https://www.upwork.com/freelancers/~01c39582606f6c1ae5

@Victor-Nyagudi thanks for this reference. I test my code on my local machine and eveything is working perfectly you can see this video.
Screencast from 2023-12-21 15-11-29.webm

Awaiting proposal review @rushatgabhane

@dukenv0307's proposal LGTM
🎀 👀 🎀

Next up is @youssef-lr to confirm contributor assignment https://github.com/Expensify/App/issues/33340#issuecomment-1874032107

c: @dukenv0307 - $500 - paid
c+: @rushatgabhane - $500
Rushat you can make a manual request, and then if you could complete the checklist we can close this out!

WIP ⚠

The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/19868

The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/19868#issuecomment-1912671316

A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: N.A. because this was intentionally removed.

Determine if we should create a regression test for this bug. No

If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again -N.A.

Thank you! manual request here https://staging.new.expensify.com/r/8963455257501785


new compile type causes errors

love the new compile api, super cool how thats able to be done with Proxy
its great to just be able to pass in a clean component, and get out a new compiled one that type wise is identical
however I ran into some strange type issues (errors in comment of gist)
This might be solved by explicitly passing a generic, but the dx is so much better when that isnt necessary
After messing around a bit I refactored the type for compile and ended up with this
type StringPropsOnly<P> = {
  [K in keyof P]: string;
};

declare function myCompiled<P extends StringPropsOnly<P>>(
  this: void,
  component: (props: P) => JSX.Element,
  strict?: boolean,
  separator?: string
): (props: P) => JSX.Element;

which resolved all of the issues I had

The existing type still supports passing a tuple or record of strings, which I am assuming is a remnant from the old API.
Curious to your thoughts on this, but I think we should drop support for that, and just rely on inference from the function

thanks!

Hey @ethanniser.
You can solve by using typeof fn as generics, like html.compile<typeof Component>(Component).
Yes, I kept the string[] props because it was from the older API, however we bumped to v2, which is by itself a breaking change.
Happy to merge a PR with your proposed new type.


white space is coming if I disabled the infinite scroll

hello team,
can anybody please help me here if I remove the infinite scroll than white space is coming in last card ,how can I handle this

@pratusha-dwivedi Getting the same, anything you get from your side?


Fixing package versioning

Fixes #214

@CommunityToolkit/aspire-contributors package versioning looks to be fixed with this if someone wants to review and merge then push this up to other branches. I'll clean up NuGet and Azure Pipelines tomorrow (manual task)


mem-ruby,configs: Add GLC Atomic Latency VIPER Parameter

Added a GLC atomic latency parameter (glc-atomic-latency) used when enqueueing response messages regarding atomics directly performed in the TCC. This latency is added in addition to the L2 response latency (TCC_latency). This represents the latency of performing an atomic within the L2.
With this change, the TCC response queue will receive enqueues with varying latencies as GLC atomic responses will have this added GLC atomic latency while data responses will not. To accommodate this in light of the queue having strict FIFO ordering (which would be violated here), this change also adds an optional parameter bypassStrictFIFO to the SLICC enqueue function which allows overriding strict FIFO requirements for individual messages on a case-by-case basis. This parameter is only being used in the TCC's atomic response enqueue call.
Change-Id: Iabd52cbd2c0cc385c1fb3fe7bcd0cc64bdb40aac

As far as I can tell, your commit message needs to be updated for two things:
1. Follow the 80 character per line limit

2. In the second paragraph, you should explain better why you added this parameter -- i.e., specifically because the GL2 now has data requests that take less time than atomic requests, and the ignoring of ordering is intended to only happen when they interact.

@DanKouch I see you are still pushing updates.  Just let us know when you want us to review.

To add to Matt's list:
3. As per the "Requirements for change descriptions" section in CONTRIBUTING.md, use imperative mood in the short description.  That is: "Add GLC Atomic Latency...", not "Added..."  This has been discussed many many times already.

@mattsinc @shingarov Thanks! I've made those changes and marked this as ready to review.

The code looks good. The commit message line lengths are too long though. I believe commit messages are still supposed to be <80 characters per line.

@abmerop I was confused about this too, but I think it's GitHub playing an optical illusion on us.  If you go here: https://github.com/gem5/gem5/pull/110/commits/7170ac8f3edc4685c9121a79fe3f20f9c17043f9, you can see the commit message lines are 80 characters or less.

@mattsinc @abmerop It looks like GitHub automatically reformats the message when creating the PR description per this article.

@mattsinc @abmerop It looks like GitHub automatically reformats the message when creating the PR description per this article.

Thanks @DanKouch !  It looks like there are some commits on develop now that weren't there when you pushed -- in theory it looks like GitHub will let you automatically update though via "Update branch"

@mattsinc Rebased to the head of develop.


theme does not support setting BackgroundSize

UnoCSS version
0.50.4
Describe the bug
hello！why unocss does not support setting BackgroundSize in theme？
I found it in windicss documentation. but unocss does not work. Is there any way to customize BackgroundSize?
looking forward to your reply~

Reproduction
export default {
  theme: {
    backgroundSize: {
      'auto': 'auto',
      'cover': 'cover',
      'contain': 'contain',
      '50%': '50%',
      '16': '4rem',
    },
  },
}

### System Info

_No response_

### Validations

- [X] Read the [Contributing Guidelines](https://github.com/unocss/unocss/blob/main/CONTRIBUTING.md).
- [X] Check that there isn't [already an issue](https://github.com/unocss/unocss/issues) that reports the same bug to avoid creating a duplicate.
- [X] Check that this is a concrete bug. For Q&A open a [GitHub Discussion](https://github.com/unocss/unocss/discussions) or join our [Discord Chat Server](https://chat.antfu.me).
- [X] The provided reproduction is a [minimal reproducible example](https://stackoverflow.com/help/minimal-reproducible-example) of the bug.

Try to use bg-[length:xxx], like bg-[length:50%_50%] bg-[length:50%_10rem]
Or you can write rules or shortcuts what you want.


Issue to enrich Window object

Hey there,
If i test this code, i got an error on  doesntwork which is not defined :
// => /types/window.ts
interface Window {
  something: () => void;
}

// => /index.ts
window.alert('its ok');  // works
window.something();      // works
window.doesntwork();     // don't works

But as soon as i try to import some types from node_modules in any way, i got an error Property 'something' does not exist on type 'Window'. not defined :
// => /types/window.ts
import * as LibTypes from 'lib-with-types';

interface Window {
  something: () => void;
  // whatIWant: LibTypes.type;   <= even without this, it does not work
}

// => /index.ts
window.alert('its ok');   // works
window.something();       // does not works 🤪
window.doesntwork();      // don't works

What i'm trying to do is setting the raven-js type to window.Raven but declare it globally, but it seems never work, because i'm unable to import this type.

If the file is a module you need to declare the type in global
declare global {
    interface Window {
        something: () => void;
        // whatIWant: LibTypes.type;   <= even without this, it does not work
    }
}
export {}

window.alert('its ok');   // works
window.something();       // ok
window.doesntwork();

Ow ! thanks for your answer, it actually does the trick. I cannot get why this export {} is enough to make it work.
It's not really for a sharable module, it's in my app code base. I now notice this two behaviors working :
declare global {
    interface Window {
        // anything
    }
}
export {}

or
import Raven from 'raven-js';

declare global {
    interface Window {
       Raven: Raven.RavenStatic;
    }
}

Since i import something it's automatically considered as module ? It wasn't very clear in the doc.

@DavidBabel  Yes anything that has an import or an export is automatically a module.

Looks like a world of exception. I did not make it work to add a "valid field" in React / Typescript.
I wanted to add the field "space" in svg tag, but i did never make it work :
declare global {
  interface SVGAttributes {
    space?: string;
  }
}
export {};

My guess here is that I try to override React.SVGAttributes, but it's not clear in the doc either.

@DavidBabel  It's sometimes a bit tricky. You have to find the exact interface you are extending and see where it is defined. In this case SVGAttributes is defined in the React global namespace. To augment it this should work:
declare global {
    namespace React {
        interface SVGAttributes<T> {
            space?: string;
        }
    }
}

It has to be generic because the interface defined in React is generic and we need to have the same number of type parameters to any augmented interfaces.
The topic of module augmentation is covered here

It' actually working. Thanks for the trick and all the help.
This doc really miss a search field :)
I close the issue.


Sample for amp-dynamic-css-classes

Related to #209

Resolved by #356, blocked by #355
Created https://github.com/ampproject/amphtml/issues/4953


Issues before 1st release

mentions #53

Style:

OpenSquare

mention filter

SubSquare

Style problems
Markdown

Mention popup location problem/popup items active style

Quill.js

mention enter key not work
Mention popup location problem
Other mention related problems

Roadmap:

Make sure OpenSquare editor can be released.
Make sure SubSquare markdown editor can work.
Make sure SubSquare markdown/quill.js editor can work.


mountPath behavior changed from docker to containerd on Windows

Description
now the following mountPath behavior changed from docker to containerd on Windows:
          volumeMounts:
          - mountPath: 'D:'
            name: azure

docker on Windows

mount as a D drive

containerd on Windows

mount as c:\D\ folder
question is how can I mount as a new drive with containerd on Windows? is this a regression?
Steps to reproduce the issue

n/a

Describe the results you received and expected
I could still mount hostPath as a new drive with containerd on Windows
What version of containerd are you using?
containerd://1.5.5+azure
Any other relevant information
No response
Show configuration if it is related to CRI plugin.
n/a

cc @kevpar

@ambarve was looking into this.

any progress here?

Looks like #6651 is the solution, and is progressing through review. The tests at https://github.com/containerd/containerd/pull/6651/files?diff=unified&w=0#diff-908e014f804871a6a2f00b97c0f88f378cfba56538f24cf0b8da4040d0d797e2 appear to cover this use-case.

Any status updates on this?

#6651 has merged into containerd and will be part of containerd 1.7. I guess that PR was supposed to close this ticket, but perhaps "Fixes" doesn't work in comments.

Hello,
do you know when this bugfix will be included in the official released version?
Thank you

the fix is also in Windows containerd v1.6.6

@andyzhangx You say it's fixed in 1.6.6 and @TBBle in https://github.com/containerd/containerd/issues/6589#issuecomment-1116270408 says it will be fixed in 1.7. Am I getting this right that we should actually wait for 1.7?
AFAICT, containerd v 1.6.14 is still not fixed and can not mount D: or Z: drives for me on AKS. Everything worked well with AKS on Kubernetes 1.22 (now EOL'ed) but it's been failing apart since I upgraded to 1.25.5. Unfortunately, there is no follow-up from @rnemeth90 to his https://github.com/kubernetes-sigs/azurefile-csi-driver/issues/923 if this issue has been resolved for him.

@mloskot If this was a regression, it was never resolved to my knowledge. We implemented a work-around by adjusting our applications to use the new path ( c:\d, etc. )

@rnemeth90 Well, from the higher level of AKS standpoint, it is a regression to me. I've upgraded my cluster and it's stopped working, and I'm locked as I can not go back, because Docker CRI is no longer supported, regardless if nodes are based on Windows Server 2019 or 2022.
Apologies for wandering off-topic here, but it's astonishing to me how such basic functionality could have slipped through AKS QA sieves.
Mounting volumes as non-C drives is an ubiquitous convention on containers I have to manage, so this issue turns a serious inconvenience.
As for the workaround, do you mean you've patched your containers to do something like subst D: C:\d, e.g. during entrypoint?
I'd be grateful for more details.

My comment predated the backport of that fix into containerd 1.6 (https://github.com/containerd/containerd/pull/6929), and it is listed in the 1.6.5 changelog: https://github.com/containerd/containerd/releases/tag/v1.6.5.
The backport included the tests I mentioned, and they're still there in the 1.6 release branch, so either I was incorrect in thinking those tests covered this problem, or something else is going wrong at a different level, perhaps in hcsshim or the HCS itself.
Is it possible to capture the hcsshim::CreateComputeSystem request in your setup? That should contain a MappedDirectories key which indicates what mapping request was sent down to the HCS by hcsshim, and will help narrow down the kind of bug happening here.

@TBBle

My comment predated the backport of that fix into containerd 1.6

I see, thanks for the confirmation. Great news!

either I was incorrect in thinking those tests covered this problem, or something else is going wrong at a different level, perhaps in hcsshim or the HCS itself.

In mounting-tests.zip I prepared two kubectl-based using vanilla mcr.microsoft.com/windows/servercore:ltsc2022 images tests which cover mounting in folder on C: and mounting as D:, and as you can see in the README.md there, they both succeeded on my AKS cluster (Kubernetes 1.25.5, Windows Server 2022).
Those results puzzled me as why on earth mounting on D: is failing for my custom images based on mcr.microsoft.com/windows/servercore:ltsc2022?  I moved to your suggestion on "something else is going wrong" and I found out that Dockerfile-s of my custom images contain this seemingly benign declaration:
# Document volume mount points typically mounted from Azure file shares.
VOLUME ["D:", "Z:"]

Now, after removing this VOLUME line and rebuilding my images, everything seems to be getting back to order!

Is it possible to capture the hcsshim::CreateComputeSystem request in your setup?

Well, I'm not sure how to do it (too much of a rookie here), but I looked at Kubernetes events generated for my images using the troublesome VOLUME ["D:", "Z:"] and here is the sample which suggests the  containerd is tripping over the Dockerfile directive VOLUME:
Error: failed to create containerd container: rootpath on mountPath C:\Windows\TEMP\ctd-volume3950197485\377, volume Z:: CreateFile C:\Windows\TEMP\ctd-volume3950197485\377\Z:: The filename, directory name, or volume label syntax is incorrect.
Error: failed to create containerd container: rootpath on mountPath C:\Windows\TEMP\ctd-volume427796215\376, volume D:: CreateFile C:\Windows\TEMP\ctd-volume427796215\376\D:: The filename, directory name, or volume label syntax is incorrect.
Error: failed to create containerd container: rootpath on mountPath C:\Windows\TEMP\ctd-volume2161075262\375, volume Z:: CreateFile C:\Windows\TEMP\ctd-volume2161075262\375\Z:: The filename, directory name, or volume label syntax is incorrect.
Error: failed to create containerd container: rootpath on mountPath C:\Windows\TEMP\ctd-volume554088254\374, volume Z:: CreateFile C:\Windows\TEMP\ctd-volume554088254\374\Z:: The filename, directory name, or volume label syntax is incorrect.

The VOLUME ["D:", "Z:"] used to work or rather had not caused any trouble on my previous AKS based on Docker CRI.
Was that behaviour on my previous AKS anything Docker-specific and my use of VOLUME directive was erroneous or is this something containerd is lacking about?
However, it looks like it's turned out an embarrassing way as the issue is with my custom images. So, I'd like to sincerely apologies for my earlier rant in https://github.com/containerd/containerd/issues/6589#issuecomment-1427157883

Interesting. That might be a separate containerd bug to file then, as by my reading of the docs your usage there looks valid.
Tracking down the error message, rootpath on mountPath C:\Windows\TEMP\ctd-volume3950197485\377, volume Z: is coming from thie code block, and I'm pretty sure that first line is the bug. fs.rootPath is going to try to return C:\Windows\TEMP\ctd-volume3950197485\377 + \ + Z:, but that's not a valid path on Windows. The error we're seeing is part of fs.rootPath's symlink-protection checks trying to open that file, but otherwise it would have failed with stat volume in rootfs when that code block tried to check if the target existed in order to copy stuff into it.
I suspect this code block should simply skip drive-letter volumes other than C:, since I don't believe (but could be wrong) that you can store non-C: volumes in a WCOW container image; the fs (rootfs here) is assumed to be mounted at C:, other drive letters are runtime-only. (I also suspect that VOLUME ["D:", "Z:"] also won't guarantee those drive letters exist, as they would for non-drive-letter paths, but I haven't checked that, don't know if Docker does the same thing, and that would be a different bug (or feature request...) either way. #5671 went more into this area.)
I suspect the repro commands from #5671 or similar, but with a trivial Dockerfile with a VOLUME ["D:", "Z:"] line (which doesn't apply to Linux) would reproduce this issue with only containerd and crictl, if it helps, since that avoids the need for k8s in the repro.

@TBBle Thank you for looking into that. I wish I could help more, but the only way I can think of is testing any fixes happening in future. I will watch that #5671 space.

#5671 is an already-resolved issue. If you don't create a new issue for what you're seeing with VOLUME ["D:", "Z:"], it won't get addressed. No one else seems to have logged it nor fixed it in the last few years that the bug has existed, so we could be waiting years more for a fix to appear organically, or for someone else to have the same problem, correctly identify the relevant factor (as you did above) and log a bug for it so it's visible to people who aren't watching specific resolved issues. ^_^

FYI, I have verified that the original fix is containerd 1.6.14, mountPath: 'D:' works now.
# k get no -o wide
NAME                                STATUS   ROLES   AGE     VERSION   INTERNAL-IP    EXTERNAL-IP   OS-IMAGE                         KERNEL-VERSION      CONTAINER-RUNTIME
akswin000000                        Ready    agent   4m42s   v1.26.3   <IP_ADDRESS>    <none>        Windows Server 2022 Datacenter   10.0.20348.1726     containerd://1.6.14+azure

---
apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: statefulset-azurefile-win
  labels:
    app: busybox
spec:
  serviceName: statefulset-azurefile-win
  replicas: 1
  template:
    metadata:
      labels:
        app: busybox
    spec:
      nodeSelector:
        "kubernetes.io/os": windows
      containers:
        - name: statefulset-azurefile
          image: mcr.microsoft.com/windows/servercore:ltsc2022
          command:
            - "powershell.exe"
            - "-Command"
            - "while (1) { Add-Content -Encoding Ascii D:\\data.txt $(Get-Date -Format u); sleep 1 }"
          volumeMounts:
            - name: persistent-storage
              mountPath: 'D:'
  updateStrategy:
    type: RollingUpdate
  selector:
    matchLabels:
      app: busybox
  volumeClaimTemplates:
    - metadata:
        name: persistent-storage
      spec:
        storageClassName: azurefile-csi
        accessModes: ["ReadWriteMany"]
        resources:
          requests:
            storage: 100Gi


When I query node object in Operation Audit, the result shows some nodegroup object.

In GitLab by @luotian-github on Sep 19, 2018, 16:48
When building image by dockfile, I couldn't find a button to start building.

In GitLab by @sokril on Nov 8, 2019, 07:59
fix with #1704

In GitLab by @luotian-github on Nov 8, 2019, 07:59
No problem yet.

In GitLab by @sokril on Nov 8, 2019, 08:27
closed

In GitLab by @sokril on Nov 8, 2019, 08:27
assigned to @luotian-github

In GitLab by @sokril on Nov 13, 2019, 05:06
mentioned in merge request !899

In GitLab by @sokril on Nov 13, 2019, 11:23
mentioned in merge request !1045


[RFC] Jigsaw integration

Jigsaw integration OpenSearch
This proposal addresses following problems related to OpenSearch codebase and its plugins framework -

Strong encapsulation: the server module in OpenSearch is weakly encapsulated and all packages are exported both for direct access and through reflections.
Lack of separation of concern and monolith module: The server modules needs to be split down into components depending on the use-case they are solving in the system. Also, the plugin developer or consumer of these modules shouldn’t be concerned about the business logic or changes in unrelated modules. For e.g. AnalyzerPlugin should only depend on modules of its concern, maybe - analyzer-module, search-module, index-module etc.

Note: this proposal assumes breaking changes are allowed in OpenSearch 2.0 and that’s when these changes can go in all at once.
Solving above two problems using Java 9 modules will inherently address other problems such as -

OpenSearch version agnostic of individual plugins versions - Plugins will depend on the versions of modules on which they depend on and not the OpenSearch version. If some module doesn’t have any major version bump in OpenSearch release, the dependent plugin should continue to run as it is.
Code hygiene and better maintainability: modular codebase is more maintainable and easy to contribute to as it will have better visualization and dependency graph, which would make more sense to the opensource contributors who want to focus on specific part.
Unblock customers using Jigsaw modular architecture: Customers who have already migrated to Java 9 modules are currently blocked as OpenSearch rest client doesn’t supports Java 9 modules. More details here - https://github.com/elastic/elasticsearch/issues/38299

Benefits of  Java 9 modules?

Strong encapsulation: Java 9 modules enables strong encapsulation of internal classes of modules if the modules are properly configured. By default, all public types are not exported and needs to be explicitly exported by exporting corresponding packages.
Reliable configuration: The dependencies missing can be found at compile or launch time instead of delaying it to the runtime of application.
Security: Strong encapsulation ensures hiding internal packages not meant to be exposed to consumers.
Better migration support: Concepts like automatic, named, unnamed modules are designed to make it possible for large codebases such as OpenSearch to migrate to modular architecture incrementally. More details in following sections. All modules are backward compatible with JDK-8 as Java runtime environment, so applications running on JDK-8, will not break.
Better start-up performance: Since the packages exported and required types are known ahead of time, the JVM classloading for modular system is more optimized. Earlier, classloader had to perform a linear scan of all jars on the classpath to find out origin of a class at the time of loading.

Tradeoffs of Java 9 modules:

No support for module versions: Java 9 modules doesn’t support version. And for this usual build tools like gradle can be used just like they are used now to support versioning and specify dependency of a modular jar on any specific version.

Split packages: same packages cannot span across multiple jars and will result in split packages in JPMS. This was not the case before.

Cyclic dependencies are not allowed between module and dependency inversion using ServiceProvider is promoted in JPMS. This implies more refactoring work to split modules out of a gigantic module with circular dependencies among its packages.

Additional effort to maintain dependencies and export rules

Module configurations are immutable, so updating the modules at run time will not be supported out of the box.

There is a nice blog on concerns regarding Jigsaw - https://developer.jboss.org/blogs/scott.stark/2017/04/14/critical-deficiencies-in-jigsawjsr-376-java-platform-module-system-ec-member-concerns
Before jumping into integration, if you’re new to JPMS, below are some of its concepts which will be used throughout the document -
Module descriptor file: This files defines all the rules like dependencies and exports of a module as is named as module-info.java. It is placed at java source root. This is what differentiates a modular jar from non-modular.
Module path: Just like classpath for plain jars, module paths are for modular jar. It is not mandatory though to load all modular jars on module path, if its loaded onto classpath, then they would behave like a plain jar. JPMS has special rules for readability between module path and classpath which would become clear in following sections.
Unnamed module: All plain jars, not containing the module descriptor files and on classpath, will be all be categorized as unnamed module and will all be placed in unnamed module group. These non-modular jars are just like plain jars in non-jpms system, they export everything and can depend on classes of any jars present on the classpath. So any plain jar can depend on other plain jars. Also, unnamed modules have access to all modular jars and they don’t have to specify any dependency rules to depend on them. So, in a way, if we place all jars (both modular and non-modular) in classpath, everything would run in a same way as it is now.
Named module: Modules containing module-descriptor file placed on module path, will automatically be treated as modular jars. Named modules can only depend on other named modules and cannot directly depend on unnamed modules. This is way too strict, isn’t it? JPMS provides 2 ways to access plain jars not yet modularized or unnamed modules on classpath - by specifying readability edge between source module and all unnamed modules OR using automatic modules as described in next section. Adding readability edge isn’t a pleasant idea because of 2 reasons -

using readability edge, we cannot control jars or packages in a fine grained manner, so all plains jars on the classpath will be accessible to the source module irrespective of whether they are using them or not. It is an example of weak encapsulation which we are trying to address here.
If there is some type exposed by this source modular jar to its consumer which is defined in an unnamed module, then consumer of this jar will need to add readability edge as well to all unnamed modules. Think about the case where all lucene jars, which are not yet modularized, are placed on classpath as unnamed modules and source module is exposing some type of lucene to its consumer. Now consumer is also required to add readability edge to all unnamed modules, which will not just expose all lucene jars to the consumer, but all other plain jars which are not yet modularized (like server jar) on classpath.

Automatic module: jars without module-descriptor files, but placed on module path will be treated as automatic modules. Automatic modules have access to all named modules as well as unnamed modules on the classpath. They export all their packages. Also, both modular and non-modular jars have access to everything in automatic modules. They act as a bridge between named and unnamed modules and is a great way to create a link between modular jars on modulepath to use non-modular jar on classpath. Modular jars can refer them by the automatic name given by JPMS to these jars, which is derived from the jar name, more details here. Its a great way to progressively migrate packages to non-modular jars to its modular version.
They come with a tradeoff, since they export everything, so when a jar is modularized, it may stop exporting some of the packages used by its consumer, and that could be a breaking change for its consumer. For e.g. if we put lucene jars on module path and treat them as automatic modules, they will export all their packages. So as an OpenSearch plugin developer or one of its module, if it has dependency on this lucene automatic modules, their code might break when lucene actually modularize their jars and stop exporting some of the packages used by its consumer.
Split packages: when one package is present in multiple jars, they cannot be loaded as separate modules on module path. They all can reside on classpath though like the way it supports them today. OpenSearch codebase is full of split packages between server module and other modules like opensearch-core, opensearch-x-content, opensearch-cli etc. It also have split packages with lucene jars as it contains org.apache.lucene package. Not just OpenSearch, lucene also have packages spread across multiple modules, more details here - https://lucene.apache.org/core/7_3_0/MIGRATE.html and https://issues.apache.org/jira/browse/LUCENE-9623
There are other important concepts such as open modules for reflection access, patch module to avoid split packages and accessing services using ServiceLoader APIs etc,  which one can explore on their own and are important to enumerate all possible scenarios and workarounds.
Lets visualize existing non-JPMS modules in OpenSearch and dependency graph -

Strategy to modularize
From everything on the classpath, modularize and move everything to the module path incrementally -

Note: The new modules in diagram above are hypothetical names used to explain the strategy.
Rules:
Below rules are just proposal and there might be better alternative available depending on what tradeoffs are acceptable and we are willing to take.
From unnamed to automatic module -
Automatic modules are work in progress modules where classes and packages are not yet final. So, packages can move from unnamed module to an automatic module over the time. The constraints are -

any packages in automatic module should not have cyclic dependency on any other module (both named and unnamed) in the system. OpenSearch codebase is full of them, so lot of refactoring like dependency inversion or moving common utilities into a separate module would be required.
Split package: Two modules on modulepath cannot have package with same name. So either the new automatic module should rename those packages if same package is present in unnamed/other named module OR move all of the packages into one module. Patch module should only be used for exceptions and with careful considerations.

From automatic to named module -
Module should only be treated as a named module when all its dependencies either are modularized or are present in one of the automatic module. This rules should be enforced for most of the cases and readability edge from named to unnamed module should be avoided. There could be exceptions though for readability edge from named to all-unnamed modules only if that dependency cannot be immediately modularized and its an internal dependency of that named module and not something exposed and published to the external consumers. This is to prevent external consumers to not to depend on unnamed modules. Also, export rules needs to be defined before declaring a module named.
Open Questions:
How to prioritize initial use-cases to migrate to modules?
Should it be rest client or analyzers or geo.
how to define base modules for initial use cases which would fit in overall modularization strategy?
A good way is to analyze all packages in server modules and try to look at their dependency graph. There are cyclic dependency among almost all packages. Number of edges of dependency between 2 packages do help in finding if that dependency is really needed or not. Thereafter, we can use the role and concern of each package in the system which we want modularize and see if the dependency makes sense or not. If not, we need to refactor the code and remove those cycles.
Renaming package while modularization?
This is required to avoid split packages. With lack of better solution so far, the only way out is to rename packages while migrating. There are 2 problems with this approach -

It will for certain break all consumers of the package since its renamed.
If the type was package private and the package is partially moved to module, then those types will no more be accessible in old package not yet migrated and we may have to do some dirty refactoring in codebase to make them accessible.

Modularizing libraries like lucene which are not yet modularized and have split packages among their jars
Lucene recommends creating Uber jar for all modules and then use it as a dependency. We can make use of patch module to create one Uber-lucene jar for all lucene plain jars, and then add it to the module path and treat it as automatic module.
https://lucene.apache.org/core/7_3_0/MIGRATE.html & https://issues.apache.org/jira/browse/LUCENE-9623
Libraries getting modularized later will break consumers using them, is it something acceptable?
It can potentially break the plugins again using these dependencies.
Challenges:
Some of the perceivable challenges in implementing these changes -

Resolving cyclic dependencies among packages in server modules is going to be labor intensive and time taking work.
Resolving split packages among modules will require lot of refactoring throughout the codebase.
Defining module configuration and what to export.
Java 8 runtime compatibility and multi-release jar
Gradle and IDE support incorporating module descriptor files rules
Test coverage for all refactored changes
Special configuration for testing the modular jar
Migration tool for existing plugins - a tool capable of detecting breaking changes in existing plugin and possible proposing a fix.
Time and labor intensive work with a constraint to release all migrated modules at once
Keeping the feature branch in sync with main.

Related requests and open issues in elasticsearch - https://github.com/elastic/elasticsearch/issues/38299 & https://github.com/elastic/elasticsearch/issues/28984
Looking for feedbacks here.

This is pretty ambitious and would be a significant improvement to the codebase, so I 👍 .

@rishabhmaurya @anasalkouz @dblock  can you please confirm if this change can be included in 2.x without breaking existing API? Basically can this change be added in a backward compatible manner in 2.x line?
We are evaluating if this change warrants a 3.0 release or can be included in 2.x line so need your inputs.

@bbarani I'm quite sure this change will have breaking changes so we shouldn't consider it for 2.x.


Null Point Expetion to server join

http://pastebin.com/hc1vpyiz

this also happened to me, it's a bug with lastest sportbukkit, it forces a locale change event on player login.

fixed in 279f100


[APIView] Error in AppInsights

Name property is null, add null check.
https://apiview.dev/Assemblies/Revisions/d529fed9d2bc48918af58327fe8379a2?handler=Upload
https://github.com/Azure/azure-sdk-tools/blob/19ca6ea1647e7bebfe1a7583ddcd8bc5c3087bb8/src/dotnet/APIView/APIViewWeb/Models/ReviewRevisionModel.cs#L56

Code causing this has been rewritten.


A statefulwidget to show the student info on the page and to support the signaturePad

issue #12

closed with #17


Create opengraphiti storage interface

Create an opengraphiti storage interface.  It might look good for a demo during the presentation.

Could alternately visualize it in http://ubietylab.net/ubigraph/


Compile Errors With Windows Native EOL

Thanks for this great tool! There was really a need for an up-to-date Glulx assembler.
On Windows, when I try to assemble the source files from the demos folder I get the following errors (due to native EOL being CRLF):
basic.ga:61:4 unexpected character; \ only permitted at end of line
basic.ga:61:22 unexpected character; \ only permitted at end of line
basic.ga:61:27 unexpected character; \ only permitted at end of line
basic.ga:61:1 expected identifier
Errors occured during parse & build.

minimal.ga:13:1 unknown mnemonic in
Errors occured during parse & build.

glk.ga:267:33 unterminated string
Errors occured during preprocessing.

But if I convert the sources' EOL to Linux style (LF) these errors dissapear.
Any chance you could add support for CRLF too on the Windows version?
Or, should the .ga source files always employ LF?
In this case, it might be worthy adding a .gitattributes setting to enforce Unix style EOLs in the demo files, as well as a notice about EOLs enforcement. The current project setting, when cloning the project locally on a Windows machine, will make Git normalize EOLs of .ga files to CRLF.
Thanks

Definitely a bug - I don't use Windows much so it just never came up. I'll see about adding support for Windows line endings in a little bit.

I think I've got a fix in place for it; let me know if it works for you.

Thanks.
I still get some errors, although slightly different:
basic.ga:61:1 unknown mnemonic odules
Errors occured during parse & build.

glk.ulx missing .end_header directive
glk.ulx missing start label
Errors occured during parse & build.

minimal.ga:13:5 unexpected character; \ only permitted at end of line
minimal.ga:13:1 unknown mnemonic y25
Errors occured during parse & build.

glk.ga:267:33 unterminated string
Errors occured during preprocessing.

The line numbers mentioned in the errors seems out of synch with the source (in some cases they are beyond the actual source lenght), it seems that CRLF line endins are affecting the internals position tracking. Also, some of the above errors don't seem to be in the source file:

basic.ga:
  basic.ga:61:1 unknown mnemonic odules

The source doesn't contain "odules".

minimal.ga:
  minimal.ga:13:5 unexpected character; \ only permitted at end of line
  minimal.ga:13:1 unknown mnemonic y25

Line 13 is the last line in the source and it's empty. In the source there is no reference to y25 (or 25).

You could just enforce usage of LF EOLs in .ga sources, but chances are that Windows users would end up inadvertently creating source files with native CRLF EOLs, and be confused by the error messages.

By the way, if you convert the EOLs in the .ga sources from LF to CRLF under Linux, do you get the same errors?
I've peeked at the changes in your last commit, and it looks like it should also add CRLF support under other OSs.
I'm compiling using MinGW-W64's gcc 6.3.0:
gcc (x86_64-win32-seh-rev1, Built by MinGW-W64 project) 6.3.0

And, apart from some errors with the demo folder, the glulx-assemble is working fine when I change the sources EOLs to LF:
D:\glulx-assemble>mingw32-make
gcc assemble.o lexer.o parse_core.o parse_main.o parse_preprocess.o tokens.o labels.o opcodes.o utility.o strings.o -o glulx-assemble
gcc tests/test.o tests/utility.o utility.o -o test_utility
./test_utility
utility.c: RAN 10 TESTS; 0 FAILED
gcc tests/test.o tests/parse_core.o parse_core.o tokens.o utility.o -o test_parse_core
./test_parse_core
parse_core.c: RAN 5 TESTS; 0 FAILED
gcc tests/test.o tests/tokens.o tokens.o utility.o -o test_tokens
./test_tokens
tokens.c: RAN 16 TESTS; 0 FAILED
cd demos && mingw32-make
mingw32-make[1]: Entering directory 'D:/glulx-assemble/demos'
mingw32-make[1]: *** No rule to make target '../glulx-assemble', needed by 'minimal.ulx'.  Stop.
mingw32-make[1]: Leaving directory 'D:/glulx-assemble/demos'
makefile:13: recipe for target 'demos

When you originally reported the issue I was able to duplicate it by changing the line endings to CRLF, but the latest changes completely fixed the issue for me on Linux.
That said, the errors you're seeing are quite interesting and suggest something has gone massively wrong with the build process. There shouldn't be any attempt to build "glk.ulx" at all - that's just an include file containing GLK-related .defines. Likewise for the unterminated string message - there shouldn't be any strings in glk.ga
I can look more into It on the weekend, but for the moment the only thing I can suggest would be to delete and reclone the project, unfortunately.

I've rewritten the file loading code so it'll hopefully work better (along with a number of other updates while I was there). I'll probably see about setting up a Windows development environment as well to try and dig up any other issues that might be lying in wait as well.

Wonderful! Now I don't get any errors, regardless of the EOL in the source.
Thanks, this is a great project and a much needed one too!


Regression in "validation passed" output message

Previous versions of the jsonschema would validate a json file, and if there were no errors, would print out a timestamp and the message "Passed validation".
However, the current system no longer prints a message when validation is passed. It would be nice to obtain some form of notification that the schema was validated and actually passed, versus assuming that no output is a good thing.
Current behavior when validation passed:
Previous behavior when validation passed:
"HMIschemavalidator 2019/11/27 13:57:22 Passed validation"

this is a library. and does not print any thing to console even in previous versions.
if you are sure that is the case, provide details of version and sample code to reproduce the issue

I honestly have no idea what version it was nor how to obtain it. But I do
have snippets of the output where this string is seen.
On Thu, Nov 28, 2019, 1:43 AM Santhosh Kumar Tekuri <
<EMAIL_ADDRESS>wrote:

this is a library. and does not print any thing to console even in
previous versions.
if you are sure that is the case, provide details of version and sample
code to reproduce the issue
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/santhosh-tekuri/jsonschema/issues/34?email_source=notifications&email_token=AGUUUPVVLXEOWRJCBUIC6FTQV5SBFA5CNFSM4JSKYCOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEFLTLWQ#issuecomment-559363546,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGUUUPUGFTJMQFLKB7WXO7LQV5SBFANCNFSM4JSKYCOA
.

"Passed validation" such string is never used in this library. it must be getting printed from your library.


Want to add PhoneHub - Sell/Buy Phone Website

Describe the project
I Want to add PhoneHub - Sell/Buy Phone Website.
Issue Type:

[ ] Bug Report
[ ] Feature Request
[ ] Documentation
[x] New Project

Additional context
Pls assign this issue to me under SSOC23
Screenshots

Pls assign this issue to me under SSOC23


Maintain official docker container

We should bundle an official Dockerfile in the repo and host docker builds on dockerhub.

@jchodera
Do we have a docker hub account for the lab?
Is this it?
https://hub.docker.com/u/choderalab
Could you give me access? My docker hub account is mmh42
Thanks!

Done!


Add blog post about NIST PubID

Metanorma PR checklist

[ ] Breaking changes (list related PRs)
[ ] Documentation update required (create task for this)
[ ] External dependency introduced (documentation update need)
[ ] Gem with native library introduced

Ping @mico for additional content.


Tune speed to complete on the convnet benchmark

HI Daniel,
May I access to marvin's benchmarks for alexnet, googlenet, vgg ...?
Thank you.


Is there anything I can do?

gollm What is the essential difference between ollam and LangChain, and what are the advantages of existing projects? I think we need to find some differentiation，Otherwise, we're just copying functions that others already have.

You're absolutely right that it's crucial to have a clear differentiation and purpose. Let me explain how I've positioned gollm:
LangChain is built as a tool to build chatbots, while gollm is built as a tool for prompt engineering, focusing solely on the interaction with the LLM output (the response to a prompt).
You can see LangChain as a Swiss Army knife that can handle chat completion, but also RAG building, etc. You can basically do almost anything with a minimum for each tool. To me, LangChain's goal is to make it do a lot of things.
gollm, on the other hand, is like a commando knife that can handle prompt optimization, easy comparison of multiple LLM outputs, and mix of agents. You can get structured output with validation (even for open source models). The goal is to make that knife cut almost anything - the sharper, the better.
My Experience and Encouragement
I want to be clear: LangChain is an excellent tool, and I encourage you to use it. I used LangChain extensively for over a year, and it's incredibly powerful and versatile. However, my frustrations with certain aspects of it led me to build gollm as a specialized tool to address my specific needs.
Development Approach
My approach to developing gollm is strictly needs-based and organic. We don't add features simply because they exist in other packages like LangChain. Instead, we add functionality when there's a genuine need for it in our workflow or when community members identify a gap that gollm can uniquely fill.
For example:

I needed a prompt optimization tool, so I added it to gollm.
I needed structured output with validation that would work with whatever models I used, so I added it.
When sammcj needed a Mix of Agents feature, he contributed it to the project.

This approach ensures that every feature in gollm serves a real, practical purpose and aligns with our focus on prompt engineering and LLM output handling.
If you want to help gollm grow and don't know where to start:

Build something using gollm. Start simple – this could lead to great examples for the community.
Add support for new LLM providers. This is always needed, and I'm planning to create a guide to make this process even easier.
Explore the existing examples and try to extend them or create new ones based on your specific use cases.

Your real-world experiences and needs are what will drive gollm's evolution.
Our Goal
I'm not aiming to replicate everything that LangChain or other libraries do. Instead, I'm building a highly specialized tool that excels at prompt engineering and LLM output handling. To use the knife analogy: I'm crafting an exceptionally sharp blade for cutting, not trying to add screwdrivers or scissors to our toolkit.
But remember, we are building a good knife, not a screwdriver or scissors or anything else.

I understand your ideas and goals, so where should we start now, or what are the high-priority needs currently? I look forward to this project bringing great convenience to all developers and having stars like ollam and LangChain!

Build with gollm - this is our highest priority!

What problem are you trying to solve?
Create a simple example using gollm features
Iterate and improve your project

Share your work:

Add docs explaining what you did
Post about your project on r/gollm
Write a quick article or make a short video
Tweet or share on dev forums

If you can create something that will help newcomers, that would be fantastic. Consider a beginner-friendly project or tutorial that showcases gollm's key features.
As you work, you'll likely come up with feature ideas or find bugs to report.


How to get positioned lines in flutter while dragging?

Please see this question https://stackoverflow.com/questions/68112202/how-can-we-achieve-the-positioned-lines-while-dragging-widget-in-flutter

@jazzbpn
I see that you've already asked this question on StackOverflow, but since this is more of a how to question rather than a bug or feature request for which this repo is for, I'd suggest you to keep following on other support channels as well to get help.  Please see https://flutter.dev/community for resources and if you need help with your code, please see https://www.reddit.com/r/flutterhelp/
Closing, as this isn't an issue with Flutter itself. If you disagree, please write in the comments and I will reopen it.
Thank you


chore: cache pnpm store

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

This should shave a few minutes off CI, but we shall see.

actions/setup-node uses actions/cache under the hood: https://github.com/actions/setup-node#caching-global-packages-data
You can see that the cache is used here: https://github.com/freeCodeCamp/freeCodeCamp/actions/runs/4373459886/jobs/7651900278
It's a bit variable, but it looks like we're saving about a minute on each install step.

Right, but the process of building all the symlinks (i.e. populating node_modules) is pretty fast.  Setting up the store takes a little longer and that's where we get the savings.
It's not much, granted, but it is faster with caching.

It's not much, granted, but it is faster with caching.

What I am getting at is It would be faster if we used the underlying actions/cache for caching both the pnpm store and the node_modules.

Oh, right. That should be possible.


Announcement RESTful API for getting all the announcements in a site

Currently we may only see public announcements; need to find a way to see all the announcements of a site to be able to get a list of messages and migrate to other system.

Done. Deployed


iam unable to load model

i have 55gb ram and 3060gpu

3060 may require sequence CPU offloading, 55GB should be sufficient

 i have 55gb ram and 3060gpu

the same goes for 3090 ... strange... the predict_i2v.py is extremely slow when loading the model into gpu and when I run 'watch nvidia-smi' i cannot even see the model loading inside memory, I haven't experience something like this before...
Is this normal behavior? the files nor the model aren't that big...

Did you use qfloat8 before?

Yes.  apart from Everything it even not loading model right

 i have 55gb ram and 3060gpu

the same goes for 3090 ... strange... the predict_i2v.py is extremely slow when loading the model into gpu and when I run 'watch nvidia-smi' i cannot even see the model loading inside memory, I haven't experience something like this before...
Is this normal behavior? the files nor the model aren't that big...

Did you use qfloat8 before?

Yes.  apart from Everything it even not loading model right

model_cpu_offload_and_qfloat8

Sorry, the 3090 needs to use model_cpu_offload_and_qfloat8 due to insufficient VRAM.

We are currently trying to develop a smaller model to meet the low memory limit (30GB)

30GB RAM will be support in https://github.com/aigc-apps/EasyAnimate/pull/154


Division by zero should display "Division by zero" text in operation result field

Division by zero should display "Division by zero" text in operation result field
Reproduction:

Insert first number
Insert division sign "/"
Insert zero "0"
Click "="
In operation result text "DIV/0" shows.  {INCORRECT]
Only button "C "clears this operation. No operation can be started before clearing old one [CORRECT]
All buttons are enabled (are clickable) {INCORRECT]

What should happen:
5. In operation result rext "Division by zero" shows
7. Only "C" button is enabled. All other buttons are disabled until "C" is clicked and old opeartion is cleared
Why these changes
5. In this step text "DIV/0" looks like programming language error and not like handled error, displaying human reading text is better
7. If application steps in state in which there is only one possible way out (clicking "C") then the application itself should tell us "hey, I blocked all other buttons so you know that there was some error and you need to click this specific button to exit that error state"

This issue is related to #6


Running rake db:migrate also runs it on Heroku

When I run rake db:migrate, it is also running it on Heroku
FATAL:  permission denied for database "postgres"
DETAIL:  User does not have CONNECT privilege.

Everytime I run rake, I have to purge the Heroku staging database or I get:
rake aborted!
PG::ConnectionBad: FATAL:  permission denied for database "postgres"
DETAIL:  User does not have CONNECT privilege.
-e:1:in `<main>'
Tasks: TOP => db:test:load => db:test:purge
(See full trace by running task with --trace)
/Users/andrewcharleskelley/.rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/activerecord-4.2.0/lib/active_record/migration.rb:393:in `check_pending!':  (ActiveRecord::PendingMigrationError)

Migrations are pending. To resolve this issue, run:

  bin/rake db:migrate RAILS_ENV=test

Was a .env issue.


turn off auth for simple integration test

For future reference, we decided the staging environment tests this pass well enough.

Yes, also worth pointing out that there is less branching between authenticated and non-authenticated API calls since we introduced the metadata repository


[r2.13-rocm-enhanced] Update to 2.13-rc2; ROCm 5.6

retest gpu-pycpp please

retest gpu-non-pip-multi please

retest cpu-non-pip please

retest code-check please


[Bug]: Listing image in UI fails with DynamoDB and multiple tags for the same digest

zot version
v2.0.4
Describe the bug
If multiple tags refer to the same digest, trying to view the image details in the UI fails and redirects back to the image overview.
The log contains the message "error":"operation error DynamoDB: BatchGetItem and ValidationException: Provided list of item keys contains duplicates.
To reproduce

Configure zot to use DynamoDB as remote cache
Push an image and create a second tag for the same digest
Try to view image details in UI
User is redirected to image list instead of detail view

Expected behavior
Image details are shown in the UI even if multiple tags refer to the same digest
Screenshots
No response
Additional context
No response

@fabianmp thanks for trying out zot. We will look at this.


Cannot finish super Glyphs mode against AI

If I play against the AI, the last turn in Super Glyphs mode does not get registered in the main grid. The mini grid shows as if there was one last field free, but when I zoom in, the field is taken by me.
I'm on a Fairphone FP1, running Android 4.2.2, on a MT 6589 chip.

Thanks for this feedback.


METRON-1381: Add Apache license to MD files and remove the Rat exclusion

Added an HTML comment license header to all the MD files.  Removed the RAT exclusion for MD files, so we make sure to do it going forward.
It can be tested by looking at the GitHub rendering, along with building the site-book and making sure no Apache headers show up.  You can also create a .md file without a header and run the rat check to ensure that it catches the problem.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

+1 (pending Travis) Looks good.  Ran through some tests as you described and everything worked.  Validated both Github and site-book rendering.

+1

@ottobackwards @JonZeolla Merged in master and added header to new markdown file (the deb deployment one).  Once you two are satisfied with the new commit, and I've run through the outstanding PRs for potentially problematic ones, I'm good with merging this in.

Did you mean to tag @nickwallen in that last comment?  I took a quick look and it all looks good to me but didn't do any verification that you got all of the md files (depending on Travis), and didn't spin up the site-book.

@JonZeolla Yes, I did. No idea what I was thinking, in all honesty.
@nickwallen You're the actual person I wanted here.


Setting top_k to 0 does not disable top_k sampling and forces it to return a single highest logit candidate

Discussed in https://github.com/abetlen/llama-cpp-python/discussions/210

Originally posted by EdgarasSk May 15, 2023
Edit:
After some investigation I've identified the problem.
When sampling top_k value it is not being evaluated before passed into function
https://github.com/abetlen/llama-cpp-python/blob/1a13d76c487df1c8560132d10bda62d6e2f4fa93/llama_cpp/llama.py#LL367C1-L367C1
The value is passed as is and is not changed to n_vocab if top_k=0.
Why is that a problem?
In the source code of llama.cpp we can see that when k=0 and min_keep=1 it will always default to a maximum of a single candidate, ensuring we only receive the candidate with the highest logit.
void llama_sample_top_k(struct llama_context * ctx, llama_token_data_array * candidates, int k, size_t min_keep) {
    const int64_t t_start_sample_us = ggml_time_us();

    k = std::max(k, (int) min_keep);
    k = std::min(k, (int) candidates->size);

    // Sort scores in descending order
    if (!candidates->sorted) {
        auto comp = [](const llama_token_data & a, const llama_token_data & b) {
            return a.logit > b.logit;
        };
        if (k == (int) candidates->size) {
            std::sort(candidates->data, candidates->data + candidates->size, comp);
        } else {
            std::partial_sort(candidates->data, candidates->data + k, candidates->data + candidates->size, comp);
        }
        candidates->sorted = true;
    }
    candidates->size = k;

    if (ctx) {
        ctx->t_sample_us += ggml_time_us() - t_start_sample_us;
    }
}

This is not an expected functionality, because value of k=0 is meant to mark that top_k sampling is disabled, according to llama.cpp source code:
    fprintf(stderr, "  --top-k N             top-k sampling (default: %d, 0 = disabled)\n", params.top_k);
    ...
    const int32_t top_k           = params.top_k <= 0 ? llama_n_vocab(ctx) : params.top_k;

Hello.
I've noticed a strange occurrence when  trying to generate output. Based on context the bindgins API will always return the same output. Additionally it seems that top_p and temp values are being completely ignored.
This is not the case when running llama.cpp itself.
I am using the latest version (v0.1.50) of llama-cpp-python. I've installed it with cuBLAS support over pip as well as tried compiling it myself, both instances produce the same results.
My example script:
from llama_cpp import Llama
llm = Llama(model_path="models/ggml-vic13b-uncensored-q5_1.bin", n_gpu_layers=40)
tokens = llm.tokenize(b"I am driving down a busy street and notice a plane crashing down. What can I do?")

output = b""
count = 0
for token in llm.generate(tokens, top_k=0, top_p=0.73, temp=0.72, repeat_penalty=1.1):
     text = llm.detokenize([token])
     output += text

     count +=1
     if count >= 200 or (token == llm.token_eos()):
         break

print(output.decode())

Output example (always the same, regardless of top_p and temp):
$ python test.py
llama.cpp: loading model from models/ggml-vic13b-uncensored-q5_1.bin
llama_model_load_internal: format     = ggjt v2 (latest)
llama_model_load_internal: n_vocab    = 32000
llama_model_load_internal: n_ctx      = 512
llama_model_load_internal: n_embd     = 5120
llama_model_load_internal: n_mult     = 256
llama_model_load_internal: n_head     = 40
llama_model_load_internal: n_layer    = 40
llama_model_load_internal: n_rot      = 128
llama_model_load_internal: ftype      = 9 (mostly Q5_1)
llama_model_load_internal: n_ff       = 13824
llama_model_load_internal: n_parts    = 1
llama_model_load_internal: model size = 13B
llama_model_load_internal: ggml ctx size =  90.75 KB
llama_model_load_internal: mem required  = 11359.05 MB (+ 1608.00 MB per state)
llama_model_load_internal: [cublas] offloading 40 layers to GPU
llama_model_load_internal: [cublas] total VRAM used: 9075 MB
llama_init_from_file: kv self size  =  400.00 MB
AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 1 | VSX = 0 |

I am in a car, driving down a busy street when I see a plane flying low overhead. Suddenly, it starts to wobble and lose altitude before plummeting towards the ground. I realize that if I don't do something quickly, the plane is going to crash into the side of a building just ahead of me.

I slam on my brakes and swerve my car into an empty parking lot. As I come to a stop, I see the plane hurtling towards the ground, but it looks like it's going to miss the building by just a few feet.

What can I do? Is there anything I can do to help prevent this crash or minimize its impact?

Now, using llama.cpp I always get a different result:
$ ./build/bin/main -m ../models/ggml-vic13b-uncensored-q5_1.bin --top-k 0 --top-p 0.73 --temp 0.72 --repeat-penalty 1.1 -p "I am driving down a busy street and notice a plane crashing down. What can I do?" --gpu-layers 40
main: build = 553 (63d2046)
main: seed  =<PHONE_NUMBER>
llama.cpp: loading model from ../models/ggml-vic13b-uncensored-q5_1.bin
llama_model_load_internal: format     = ggjt v2 (latest)
llama_model_load_internal: n_vocab    = 32000
llama_model_load_internal: n_ctx      = 512
llama_model_load_internal: n_embd     = 5120
llama_model_load_internal: n_mult     = 256
llama_model_load_internal: n_head     = 40
llama_model_load_internal: n_layer    = 40
llama_model_load_internal: n_rot      = 128
llama_model_load_internal: ftype      = 9 (mostly Q5_1)
llama_model_load_internal: n_ff       = 13824
llama_model_load_internal: n_parts    = 1
llama_model_load_internal: model size = 13B
llama_model_load_internal: ggml ctx size =  90.75 KB
llama_model_load_internal: mem required  = 11359.05 MB (+ 1608.00 MB per state)
llama_model_load_internal: [cublas] offloading 40 layers to GPU
llama_model_load_internal: [cublas] total VRAM used: 9075 MB
llama_init_from_file: kv self size  =  400.00 MB

system_info: n_threads = 12 / 24 | AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 1 | VSX = 0 |
sampling: repeat_last_n = 64, repeat_penalty = 1.100000, presence_penalty = 0.000000, frequency_penalty = 0.000000, top_k = 0, tfs_z = 1.000000, top_p = 0.730000, typical_p = 1.000000, temp = 0.720000, mirostat = 0, mirostat_lr = 0.100000, mirostat_ent = 5.000000
generate: n_ctx = 512, n_batch = 512, n_predict = -1, n_keep = 0

 I am driving down a busy street and notice a plane crashing down. What can I do?

I have been trained in CPR, but not in emergency vehicle operation or emergency response. I have my phone with me and I know the location of the nearest hospital. What should I do? [end of text]

llama_print_timings:        load time =  2668.27 ms
llama_print_timings:      sample time =    72.33 ms /    44 runs   (    1.64 ms per token)
llama_print_timings: prompt eval time =   266.67 ms /    21 tokens (   12.70 ms per token)
llama_print_timings:        eval time =  3027.72 ms /    43 runs   (   70.41 ms per token)
llama_print_timings:       total time =  5772.50 ms

$ ./build/bin/main -m ../models/ggml-vic13b-uncensored-q5_1.bin --top-k 0 --top-p 0.73 --temp 0.72 --repeat-penalty 1.1 -p "I am driving down a busy street and notice a plane crashing down. What can I do?" --gpu-layers 40
main: build = 553 (63d2046)
main: seed  =<PHONE_NUMBER>
llama.cpp: loading model from ../models/ggml-vic13b-uncensored-q5_1.bin
llama_model_load_internal: format     = ggjt v2 (latest)
llama_model_load_internal: n_vocab    = 32000
llama_model_load_internal: n_ctx      = 512
llama_model_load_internal: n_embd     = 5120
llama_model_load_internal: n_mult     = 256
llama_model_load_internal: n_head     = 40
llama_model_load_internal: n_layer    = 40
llama_model_load_internal: n_rot      = 128
llama_model_load_internal: ftype      = 9 (mostly Q5_1)
llama_model_load_internal: n_ff       = 13824
llama_model_load_internal: n_parts    = 1
llama_model_load_internal: model size = 13B
llama_model_load_internal: ggml ctx size =  90.75 KB
llama_model_load_internal: mem required  = 11359.05 MB (+ 1608.00 MB per state)
llama_model_load_internal: [cublas] offloading 40 layers to GPU
llama_model_load_internal: [cublas] total VRAM used: 9075 MB
llama_init_from_file: kv self size  =  400.00 MB

system_info: n_threads = 12 / 24 | AVX = 1 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | FMA = 1 | NEON = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | WASM_SIMD = 0 | BLAS = 1 | SSE3 = 1 | VSX = 0 |
sampling: repeat_last_n = 64, repeat_penalty = 1.100000, presence_penalty = 0.000000, frequency_penalty = 0.000000, top_k = 0, tfs_z = 1.000000, top_p = 0.730000, typical_p = 1.000000, temp = 0.720000, mirostat = 0, mirostat_lr = 0.100000, mirostat_ent = 5.000000
generate: n_ctx = 512, n_batch = 512, n_predict = -1, n_keep = 0

 I am driving down a busy street and notice a plane crashing down. What can I do?

This is a scenario that you may have seen in movies or read about in books, but it's not something that happens every day in real life. If you were to find yourself in this situation, what would you do? Here are some steps you can take to help yourself and others:

1. Stop your car as quickly and safely as possible. Do not try to swerve or brake suddenly, as this could cause a collision with other vehicles on the road. Instead, carefully pull over to the side of the road and turn off the engine.
2. Call 911 immediately. Tell the operator that you have witnessed a plane crash and provide your location. Do not hang up until the operator tells you to do so.
3. Look for anyone who may have been on the plane or anyone who has been injured as a result of the crash. If there are any survivors, try to assist them by providing first aid or comforting them until help arrives.
4. Avoid touching or moving anything that may be hazardous, such as debris from the crash or fuel leaks. Do not try to remove anyone from the wreckage unless they are in imminent danger of being further injured.
5. Stay away from the crash site and do not attempt to take any photos or videos.
6. If you have a camera or phone with you, take pictures of the crash scene from a safe distance. This can help emergency responders and investigators piece together what happened.
7. If you are able to, try to remember as much information as possible about the plane crash, such as the location, time, weather conditions, and any other details that may be relevant.
8. After the incident, contact your loved ones to let them know that you are safe. If you were involved in the crash or witnessed it, seek medical attention if necessary.

Remember, in a situation like this, it's essential to stay calm and focused on helping those who have been affected by the plane crash. Your quick thinking and actions could make a difference in saving lives. [end of text]

llama_print_timings:        load time =  2636.17 ms
llama_print_timings:      sample time =   756.80 ms /   464 runs   (    1.63 ms per token)
llama_print_timings: prompt eval time =   280.92 ms /    21 tokens (   13.38 ms per token)
llama_print_timings:        eval time = 34963.14 ms /   463 runs   (   75.51 ms per token)
llama_print_timings:       total time = 38397.73 ms

Sorry if this is an incorrect place to post something like this, this is my first time posting.

@EdgarasSk thanks for reporting this and the thorough explanation, yes it looks like I missed this line https://github.com/ggerganov/llama.cpp/blob/master/examples/main/main.cpp#LL383C99-L383C99
Should have this fixed in the next release.


onPress doesn't trigger on button pseudo-element area

🐛 Bug Report
onPress doesn't trigger on button pseudo-element area, though onClick does.
I've seen this issue discussed for touch devices, but not for desktop/mouse.
https://github.com/adobe/react-spectrum/issues/1061
🤔 Expected Behavior
I'd expect onPress to trigger when button pseudo-element is pressed, like onClick.
😯 Current Behavior
onPress does not trigger when button pseudo-element area is pressed.
🔦 Context
Pseudo-elements can be useful appendages to tappable elements because they allow for a larger tappable area that won't affect the layout of other elements. They can enable you, for example, to enforce that any button or link's minimum clickable dimension be at least 44px (Apple's recommended minimum tap size).
https://ishadeed.com/article/clickable-area/#using-pseudo-elements-to-increase-the-clickable-area
💻 Code Sample
Below, clicking the core of the button triggers onPress and onClick, but clicking in the pseudo-element area (inside the frame but outside the core of the button) only triggers onClick.
https://codesandbox.io/s/intelligent-cdn-t6iu9?file=/src/App.js
🌍 Your Environment
react-aria 3.10.0
Chrome 94.0.4606.81 (Official Build) (x86_64), Firefox 93.0, Safari 14.1.1
MacOS 11.4

This sounds like a problem with how we do our own hit testing in usePress but eventually we'd like to remove that hit testing entirely from usePress in the future (https://github.com/adobe/react-spectrum/issues/1720) which may rectify the issue. For now, perhaps we could use document.elementFromPoint with the press coordinates, that seems to return the button element when provided x,y coords of a click within the pseudo element area. I'd be curious what would be returned if there were overlapping pseudo elements

@LFDanLu yeah, it looks like it would...
https://codesandbox.io/s/modest-allen-6vxo0?file=/src/App.js

Is this issue still active? it looks like this is still an issue

I think this applies to not only pseudo element but also any absolutely positioned element that expand the tap area. Hope this gets addressed soon.

Event onPressUp is not working on pseudo element, either.
Do a quick review on source code and guess it does not get into this code execution
if (e.button === 0 && isOverTarget(e, e.currentTarget)) {
  triggerPressUp(e, state.pointerType || e.pointerType);
}

https://github.com/adobe/react-spectrum/blob/main/packages/%40react-aria/interactions/src/usePress.ts#L472

Should have been fixed by #7427.

Should have been fixed by #7427.

hi. clicking the button on the pseudo element area does not trigger the onPress event handler. onHoverStart works as expected.
https://stackblitz.com/edit/vitejs-vite-3j7p5edf?file=src%2Findex.css

This is not yet released. You could try a nightly version though


An option to enable preview via remote server

Describe the bug
I enabled the preview on host <IP_ADDRESS>. However, the client only reads from ws://<IP_ADDRESS>:23625/
To Reproduce
./typst-preview --host <IP_ADDRESS>:23627 ./resume.typ
Expected behavior
The host and port logic are compatible between server and client
Package/Software version:
typst-preview extension version: v0.7.5
Logs:
typst-preview server log(Output Panel -> typst-preview):
[2023-09-15T06:49:55Z INFO  typst_preview] Arguments: CliArguments {
        font_paths: [],
        root: None,
        data_plane_host: "<IP_ADDRESS>:23625",
        control_plane_host: "<IP_ADDRESS>:23626",
        static_file_host: "<IP_ADDRESS>:23627",
        dont_open_in_browser: false,
        enable_partial_rendering: false,
        input: "./resume.typ",
    }
[2023-09-15T06:49:56Z INFO  typst_preview] Data plane server listening on: <IP_ADDRESS>:23625
[2023-09-15T06:49:56Z INFO  typst_preview] Control plane server listening on: <IP_ADDRESS>:23626
[2023-09-15T06:49:56Z INFO  typst_ts_compiler::service::diag] /resume.typ: compiling ...
[2023-09-15T06:49:56Z INFO  typst_preview] Static file server listening on: <IP_ADDRESS>:23627
[2023-09-15T06:49:56Z INFO  typst_ts_compiler::service::diag] /resume.typ: Compilation succeeded in 42.533155ms
[2023-09-15T06:49:56Z DEBUG typst_preview::actor::typst] TypstActor: waiting for message

typst-preview client log(Help -> Toggle Developer Tools -> Console):
(index):4938 WebSocket Error:  Event {isTrusted: true, type: 'error', target: WebSocket, currentTarget: WebSocket, eventPhase: 2, …}
(anonymous) @ (index):4938
error (async)
setupSocket @ (index):4937
(anonymous) @ (index):4899
setTimeout (async)
(anonymous) @ (index):4899
(index):4935 WebSocket connection closed

Additional context
Add any other context about the problem here.

are you using the vscode extension or the binary itself? VSCode remote should work without extra config. (If it doesnt, it's a bug)

are you using the vscode extension or the binary itself? VSCode remote should work without extra config. (If it doesnt, it's a bug)

I am using the binary itself on the remote server over ssh, and I want to access the result in the browser.

Could you try the following command? It might not need to expose preview service to the public network interface.
./typst-preview --host <IP_ADDRESS>:23627 ./resume.typ
ssh -CNL <IP_ADDRESS>:23627:<IP_ADDRESS>:23627 your-host

looks like typst-preview is not ready to customize service's host to this time. It use <IP_ADDRESS> everywhere.

We may add even more cli args to specify the port and host the client should connect to 😇 . But that sounds strange to me.

Similar issue when using typst-preview via coda-server, my local browser tried to access ws://<IP_ADDRESS>:{port} (of course it failed) and the preview panel is blank.

I think it's very useful and can be used to remotely access the slide


No data folder and no chapters in docker container can be found

After pulling docker image and running the container, I can verify that the container does not contain any /data folder or any chapter (e.g. ch02). Please investigate this as it isfundamental.
Thanks.

@vitali87 You must download the chapters, as the online book chapter 2 indicates.


Added Link in Dontation.html NavBar

In Donation.html there is an issue  due to which we can not return to our homepage directly and anywhere.

Hello @anuragverma108,
I am actively participating in Hacktoberfest 2024. I came across your repository, and I am very interested in contributing to it. I would love to work on this repo or any other task where you feel I can provide value. So Please assign me this repo.


execute_mdx_dataframe changes NA element to NaN in dataframe

Describe the bug
We have an element named NA, when we get this element with execute_mdx_dataframe function, it is shown as NaN in the dataframe. But, when we use execute_mdx function, we can get it like [Region].[Region].[NA]. So, I thought that it converts NA to NaN in dataframe.

Expected behavior
I just want to get NA element as NA in dataframe.
Version
TM1py : 1.9.1
TM1 Server Version: <IP_ADDRESS>

Good finding! Thanks for reporting.
I wil look into this

Hi @MaaYuu,
we will push a fix for this soon.
for now, you can execute the function with additional keyword arguments like this:

import pandas as pd

from TM1py import TM1Service, NativeView

with TM1Service(address="", port=12297, ssl=True, user="admin", password="apple") as tm1:
    mdx = """
    SELECT
    {[d1].[NA]} on 0,
    tm1subsetall([d2]) on 1
    FROM [c1]
    """
    df = tm1.cells.execute_mdx_dataframe(mdx, skip_zeros=False, na_values=["", None], keep_default_na=False)

    print(df)


Resharding

This is a big change, I couldn't figure out how to split it, sorry. In short:

adding a streaming RPC to queryservice to get the tablet health. See Liang's doc for details.
removing the old tabletserver streaming RPC call, that used to do a similar but different thing. Only vtctld was using it to build its health cache, and nobody is using that.
plumbing a bunch more of the 'target' support in sqlquery. Now if the query service has a valid target, and the client sends a valid target too, and they match, we won't look at sessionId. (not this is not plumbed all the way yet).
note I use the proto3 structures extensively, even on bson rpc. Cleaner.

This is not used by anyone yet, so we can fix forward for incompatible changes if necessary.
Upon import, I'll add the stubby and stubbyp3 versions.
@enisoc @guoliang100 (Liang is on vacation for a few more days, so Anthony, you're it :) ).

LGTM


golangci-lint: switch to be buit with go1.18

Description of changes
The only difference is the go version used to compile the binary thus the risk is low. See #166700 for reasoning (also upstream issue). Since go1.18 is not yet used by default there shouldn't be any need to update release notes and other similar stuff but I may be wrong.
Things done

Built on platform(s)

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

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

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 166801 run on aarch64-darwin 1

1 package failed to build:

vimPlugins.vim-go

1 package built:

golangci-lint


Bump array-api submodule and utilise its all-versions setup

Resolves #187, uses work from #208 :slightly_smiling_face: WIP

Looks good. Trying the JAX update here: https://github.com/google/jax/pull/18684
I'm getting a bunch of warnings about cases not being machine readable, but once I silence thouse everything seems to work.


Receive Action Points when joining at state 3

When joining in 'action points' state you should already get the full room with all the notes ?

I see a current-state event with a room which notes map has keys but arrays are empty. Maybe I mutate by mistake but it doesn't seem so at first glance.

In terms of the UI, it’d be cool to have all the notes in place when adding action items. Context and what not.
By the way, awesome project! I love that it works on my phone!

I see a current-state event with a room which notes map has keys but arrays are empty. Maybe I mutate by mistake but it doesn't seem so at first glance.

Hmm maybe this is broken on the backend side then :sweat_smile: I have a branch with some unit tests for the retro class which I'll push soon, I'll make sure this case is covered there.

Fixed in f9433011c3934f21b12e35e257a30638d8492ff1