lsp: loadError, fail to precompile CSTParser, DocumentFormat,LanguageServer

When running LSP in emacs,  it always tells me it's starting and after a while, it exists.
I've checked the files, the LanguageServer package has been downloaded to .emacs.d/.local/straight/build/lsp-julia/languageserver foleder, however there is another version in .julia folder.  Although I've precompiled LanguageSever in julia REPL, it's  calling LanguageServer in .julia folder.
Here is the log
lsp-log
Command "julia --project=/Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver --startup-file=no --history-file=no -e using LanguageServer, Sockets, SymbolServer; server = LanguageServer.LanguageServerInstance( stdin, stdout, false, "/Users/jchen/.julia/environments/v1.4", ""); server.runlinter = true; run(server);" is present on the path.
Found the following clients for /Users/....../green.jl: (server-id julia-ls, priority 0)
The following clients were selected based on priority: (server-id julia-ls, priority 0)

julia-ls::stderr output
ERROR: LoadError: could not open file /Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver/CSTParser/src/precompile.jl
Stacktrace:
 [1] include(::Module, ::String) at ./Base.jl:377
 [2] include(::String) at /Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver/CSTParser/src/CSTParser.jl:1
 [3] top-level scope at /Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver/CSTParser/src/CSTParser.jl:292
 [4] include(::Module, ::String) at ./Base.jl:377
 [5] top-level scope at none:2
 [6] eval at ./boot.jl:331 [inlined]
 [7] eval(::Expr) at ./client.jl:449
 [8] top-level scope at ./none:3
in expression starting at /Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver/CSTParser/src/CSTParser.jl:292
ERROR: LoadError: Failed to precompile CSTParser [00ebfdb7-1f24-5e51-bd34-a7502290713f] to /Users/jchen/.julia/compiled/v1.4/CSTParser/R4aS6_dWBQj.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1272
 [3] _require(::Base.PkgId) at ./loading.jl:1029
 [4] require(::Base.PkgId) at ./loading.jl:927
 [5] require(::Module, ::Symbol) at ./loading.jl:922
 [6] include(::Module, ::String) at ./Base.jl:377
 [7] top-level scope at none:2
 [8] eval at ./boot.jl:331 [inlined]
 [9] eval(::Expr) at ./client.jl:449
 [10] top-level scope at ./none:3
in expression starting at /Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver/DocumentFormat/src/DocumentFormat.jl:2
ERROR: LoadError: Failed to precompile DocumentFormat [ffa9a821-9c82-50df-894e-fbcef3ed31cd] to /Users/jchen/.julia/compiled/v1.4/DocumentFormat/JgtLh_dWBQj.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1272
 [3] _require(::Base.PkgId) at ./loading.jl:1029
 [4] require(::Base.PkgId) at ./loading.jl:927
 [5] require(::Module, ::Symbol) at ./loading.jl:922
 [6] include(::Module, ::String) at ./Base.jl:377
 [7] top-level scope at none:2
 [8] eval at ./boot.jl:331 [inlined]
 [9] eval(::Expr) at ./client.jl:449
 [10] top-level scope at ./none:3
in expression starting at /Users/jchen/.emacs.d/.local/straight/build/lsp-julia/languageserver/LanguageServer/src/LanguageServer.jl:5
ERROR: Failed to precompile LanguageServer [2b0e0bc5-e4fd-59b4-8912-456d1b03d8d7] to /Users/jchen/.julia/compiled/v1.4/LanguageServer/ite7n_dWBQj.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] compilecache(::Base.PkgId, ::String) at ./loading.jl:1272
 [3] _require(::Base.PkgId) at ./loading.jl:1029
 [4] require(::Base.PkgId) at ./loading.jl:927
 [5] require(::Module, ::Symbol) at ./loading.jl:922

Process julia-ls stderr finished

and Package
(@v1.4) pkg> st
Status `~/.julia/environments/v1.4/Project.toml`
  [7d9fca2a] Arpack v0.4.0
  [336ed68f] CSV v0.6.2
  [a93c6f00] DataFrames v0.21.2
  [31a5f54b] Debugger v0.6.4
  [7806a523] DecisionTree v0.10.3
  [31c24e10] Distributions v0.23.4
  [f67ccb44] HDF5 v0.13.2
  [7073ff75] IJulia v1.21.2
  [d0351b0e] InspectDR v0.3.7
  [033835bb] JLD2 v0.1.13
  [2b0e0bc5] LanguageServer v1.0.0
  [ee78f7c6] Makie v0.9.5
  [5fb14364] OhMyREPL v0.5.5
  [9b87118b] PackageCompiler v1.1.1
  [eadc2687] Pandas v1.4.0
  [91a5bcdd] Plots v0.27.1
  [438e738f] PyCall v1.91.4
  [ce6b1742] RDatasets v0.6.9
  [ee283ea6] Rebugger v0.3.3
  [295af30f] Revise v2.7.2
  [f3b207a7] StatsPlots v0.12.0
  [cf896787] SymbolServer v1.0.1 #julia-14-fixes (https://github.com/ashiklom/SymbolServer.jl)
  [6aa20fa7] TensorOperations v3.0.0
  [b8865327] UnicodePlots v1.2.0
  [7774df62] VT100 v0.3.2
  [37e2e46d] LinearAlgebra
  [10745b16] Statistics

versioninfo()
Julia Version 1.4.1
Commit 381693d3df* (2020-04-14 17:20 UTC)
Platform Info:
  OS: macOS (x86_64-apple-darwin18.7.0)
  CPU: Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-8.0.1 (ORCJIT, skylake)
Environment:
  JULIA_NUM_THREADS = 4

Any updtae on this

@prassee I'm waiting for feedbacks.

Is this fixed now with https://github.com/non-Jedi/lsp-julia/issues/20#issuecomment-682031361?

I assume that this is fixed


godotengine.org/qa/ email confirmation appears to be broken

Discord told me to drop the report here.
When trying to create a new account by linking github, it still requires an email + confirmation to post, but the form rejects my definitely-valid gmail account as invalid.
When trying to create an account the normal way, the email gets stored and is displayed in the correct form field, but "send confirmation link" does not appear to do anything.

Seems like this option is not available anymore.


Add hlint for Haskell

https://github.com/ndmitchell/hlint

@anaynayak Thank you! 👍

Hi, @anaynayak! We merged your PR to reviewdog! 🐶
Thank you for your contribution! ✨
We just invited you to join the @reviewdog organization on GitHub.
Accept the invite by visiting https://github.com/orgs/reviewdog/invitation.
By joining the team, you'll be a part of reviewdog community and can help the maintainance of reviewdog.
Thanks again!


Errrrr

@rowanc1 I've already just made a myst demonstrator https://executablebooks.github.io/myst-react/ which (in my biased opinion) is basically a better version of this 😬 so we should make sure we are not duplicating effort

I mean I can see how it could be useful, if you want to embed it in some where, but hmmm 🤔

Yeah - this is a small component to go in docs to have a quick interactive experience. Not a full page app.

Circling back up on this this morning.
I was aiming to have a very simple component that allows for fiddling/interacting in documentation - which I really think is helpful in a lot of good docs that I have seen around the place (i.e. in-context demos). It is also helping in my testing as I am writing the docs out for markdown-it-myst.
I think some of the confusion might have come out of the name of the repo, which is probably good for a web-component <myst-demo> but maybe confusing from the repo name, as it gave the impression of overlap with the recent myst-react repo. Happy to change the name, and open to suggestions. myst-demo-web-component wc-myst-demo?
I don't think that there is much overlap in the actual goals of having a super-solid demo page for myst (which this is not), and the scope of this repo is largely complete.


Support other issue or bug tracker when parsing problem list

In Adoptium we also we also exclude test by openjdk bug tracker in Adoptium/aqa-tests. Probably azure devops also has its bug trackers or other vendors may have their own bug trackers.
To support that we need to update GIT_ISSUE to ISSUE_TRACKER when generating problem list.
Those following lines need to update GIT_ISSUE to ISSUE_TRACKER

https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/generateDisabledTestListJson.py#L80
https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/ProblemList.json#L6
https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/ProblemList.json#L13

The following line needs to update GIT_ISSUE_STATUS to ISSUE_TRACKER_STATUS

https://github.com/adoptium/aqa-tests/blob/master/disabledTestParser/issue_status.py#L30

I can work on this

I can work on this

Hello, Shelley!
Is it okay for me to work on this?

hi @smlambert here is a PR for this issue https://github.com/adoptium/aqa-tests/pull/3030


Use pinax-starter-app as a repo template

pinax-starter-app could be a good candidate to be used as a GitHub repo template: https://github.blog/2019-06-06-generate-new-repositories-with-repository-templates/

Closing issue. Not practical at this time.


hello,where to  download  faster_rcnn_200_14_18895. faster_rcnn_300_100_175.pth

downloading the data and unzipping the data,you will find the  faster_rcnn_200_14_18895. faster_rcnn_300_100_175.pth

Thank you @yanganlan0310 for answering!


Wiki needs creating

Could do with a Wiki putting together.

I didn't understand what you are trying to do . Explain it so that i can do it .

HI @jpk3lly, how are you doing?
Can you please let me know about this documentation issue and the sentence you have written "Could do with a Wiki putting together." ? after that can I start working on this?

Hey, I'm well thanks hope you are too, apologies for the delay in coming back to you I've had limited access to my account in last week or so.
So the Wiki is already there and there is a link to the guide on how to make a pull request, so I think we just need to add some documentation on there with maybe some coding standards etc.

Pardon me but I'm not getting the point where is the Wiki?


Optimize Malaysia observed holidays

Coverage: 100.0%. Remained the same when pulling a803803022928f131bea2f6b7d8c0a3bfd1da905 on KJhellico:opt-malaysia-obs into 4ac382f94d77cbabeeb34f72085955df1da53216 on dr-prodigy:beta.

Just the same naming comments as in AZ PR.

Done.

The holidays observation rules code drives me crazy sometimes 🤪. The tests look much readable now, thank you!

First, I rewrote the entire code without cycle at the end (as for Kazakhstan, with exceptions for individual years for each holiday).  It looked really crazy. :)

First, I rewrote the entire code without cycle at the end (as for Kazakhstan, with exceptions for individual years for each holiday). It looked really crazy. :)

I know, I viewed the diff :)

I know, I viewed the diff :)

Look at this ;)


Upgrade to new API

Upgrade:

matrix support
deepset
accessor support ( check for object arrays to determine whether callback has to be applied )
function now allows inputs such as add( 2, [1,2,3] )
new README.md

Update according to Todo-list:

LICENSE
Makefile
dotfiles

Should be ready for review now.

Typed arrays are now handled more efficiently.


Default System Menu Font

Hello,
Newbie here:)
How do I select the system font used for the PDF.js menus? I have it running on two different Mac OS. Maverick and Yosemite.
I'm trying to force PDF.js to use a san serif font.
Any help would be appreciated.
Thanks

It should be enough to add your desired font-family in https://github.com/mozilla/pdf.js/blob/master/web/viewer.css#L18-L21. The viewer uses font: message-box by default, see also the CSS file for that. Since this is just CSS work and no bug in PDF.js, I'm closing this as answered.


[Windows] Minor documentation improvements

Description
Included changes:

Change report title to be Windows Server 2022
Improve .NET Core sections
Some other tiny improvements

Related issue:
Check list

[ ] Related issue / work item is attached
[ ] Tests are written (if applicable)
[ ] Documentation is updated (if applicable)
[ ] Changes are tested and related VM images are successfully generated

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022

/azp run windows2019, windows2022


[NEW] Llama3.2 weight converters 🦙

Hi!
In this branch I reintroduce & update to the current main branch the Llama model & conversion scripts to support Llama3.1 and Llama3.2 1B&3B models.
The main changes are the following:

Deleted Flash Attention RoPEs as they don't support rope scaling of Llama3
Copied + Cleaning transformers LlamaRotaryEmbedding layer. Now this will be the only class in llama.py. I think it shouldn't break generations for the inference case WITHOUT LlamaConfig.rope_interleaved = True in CausalSelfAttention.forward, are there any tests?
Added @eliebak fixes (#253) to just load weights from a checkpoint. I would suggest adding a config.optimizer.finetuning flag in order to (True) just load the weights or (False) Load weights, optimizer & LR Scheduler instead of config.checkpoints.load_optimizer & config.checkpoints.load_lr_scheduler
Switched from flash_attn_varlen_func to flash_attn_func as the later achieves greater performance. Keep in mind that we aren't using any feature of the varlen funct so it's recommended to stick with flash_attn_func
Should we depreciate LlamaConfig.rope_interleaved ? It was useful for training when using FlashAttention RoPEs and now seems to be used also in the inference code. IMO we should unify all 3 cases (Training, inference with rope_interleaved & inference without rope interleaved) within a single RoPE

Results
You can run the conversions & generations tests using the scripts in tools/converters. As I already mentioned in the previous PR (#174), despite we need at least 1 GPU (To init the ParallelContext) we are running the conversion with the CPU.

Generate HF predictions with the HF Hub model

torchrun --nproc-per-node 1 tools/converters/delete/generate_hf_predictions.py --pretrained-model-name-or-path meta-llama/Llama-3.2-3B

Convert the HF model to Nanotron

torchrun --nproc-per-node 1 tools/converters/convert_hf_to_nanotron.py --nanotron-checkpoint-path checkpoints/nanotron_pretrained_checkpoints/Nanotron-Llama-3.2-3B --pretrained-model-name-or-path meta-llama/Llama-3.2-3B

Generate predictions with the nanotron converted model

torchrun --nproc-per-node 1 tools/converters/delete/generate_nanotron_predictions.py --tp 1 --nanotron-checkpoint-path checkpoints/nanotron_pretrained_checkpoints/Nanotron-Llama-3.2-3B

Convert the model back to HF

torchrun --nproc-per-node 1 tools/converters/convert_nanotron_to_hf.py --nanotron-checkpoint-path checkpoints/nanotron_pretrained_checkpoints/Nanotron-Llama-3.2-3B --hugging-face-checkpoint-path checkpoints/huggingface_converted/Converted-Nanotron-Llama-3.2-3B

Generate predictions using the converted back HF model

torchrun --nproc-per-node 1 tools/converters/delete/generate_hf_predictions.py --pretrained-model-name-or-path checkpoints/huggingface_converted/Converted-Nanotron-Llama-3.2-3B

As can be seen from the following table, we observe slightly differences between the 2 backends. Those differences are produced by the QKV projections in the CausalSelfAttention layer (Nanotron computes them in a single GEMM vs 3 different GEMMs in HF) and the LayerNorm layer is different (Nanotron is using a optimized one from FlashAttention vs Basic PyTorch LayerNorm in HF). Also note that the differences increase if we use TP which is totally expected as the sizes of the GEMMs are different, triggering different GEMM algorithms.

Experiment
Backend
Size
TP
Accuracy

OG HF
HF
3
1
0.73046875

OG HF --> Nanotron
Nanotron
3
1
0.7265625

OG HF --> Nanotron --> HF
HF
3
1
0.73046875

OG HF --> Nanotron
Nanotron
3
2
0.703125

OG HF --> Nanotron
Nanotron
3
4
0.65234375

To run the Nanotron generations with different TP sizes:
torchrun --nproc-per-node 2 tools/converters/delete/generate_nanotron_predictions.py --tp 2 --nanotron-checkpoint-path checkpoints/nanotron_pretrained_checkpoints/Nanotron-Llama-3.2-3B
torchrun --nproc-per-node 4 tools/converters/delete/generate_nanotron_predictions.py --tp 4 --nanotron-checkpoint-path checkpoints/nanotron_pretrained_checkpoints/Nanotron-Llama-3.2-3B

TODO (Preferably in other PRs):

[ ] Add docs
[ ] Edit examples/config_llama3.2-3B.yaml data_stages.data.dataset.dataset_folder
[ ] Remove nanotron/tools/converters/delete/generate_hf_predictions.py & nanotron/tools/converters/delete/generate_nanotron_predictions.py scripts
[ ] Integrate Liger kernels for apply_rotary_pos_emb
[ ] Switch to SDPA instead of FA2
[ ] Reduce number of transposes in CausalSelfAttention.forward

Have you managed to train with tp=4 after converting llama 3.2 from HF to Nanotron? From your earlier Llama3 PR you wrote the conversion could be done with tp=dp=pp=1, and that Nanotron was TP agnostic.
When using your conversion script above for Llama 3.2 3B model it works fine for tp=2, but runs into tensor size mismatch trying to train with tp= 4:
[3236:3]:RuntimeError: The expanded size of the tensor (32128) must match the existing size (31872) at non-singleton dimension 0.  Target sizes: [32128, 3072].  Tensor sizes: [31872, 3072]


Add minimap, terminal and indentation guide colors

Hey there!
I added some colors to different elements that you haven't styled yet. Of course these additions are kind of opinionated and you may have left them unstyled on purpose, which would be totally fine.
Here's just what I have done:

Added minimap selection, warning and error hightlight colors as well as minimap gutter added, deleted and modified colors to match the editor colors:

Added indentation guide colors with active state matching the other border and line number colors:

Added terminal cursor, selection and foreground colors to match the editor colors:

There's still more elements that are unstyled (e.g. current line highlight in editor and minimap, Git conflicts, etc.), but like I said, maybe you left them unstyled on purpose or just haven't gotten around to style them yet.

I'll let you know when I release the new version with these changes. Just gotta update the example photo. Should be done in an hour or so.

No need to and glad you like it! I'll definitely check back later.


Make weather banner smarter

For example, instead of showing:

Yay! It's snowing in Tahoe!

we can do:

Yay! It's snowing at Sierra-At-Tahoe, Squaw and 2 other resorts.

Single resort:

Snowing at Squaw Valley! Keep up the snow dance until it spreads to the rest of the mountains around.

2 resorts:

That snow dance of yours! Heavenly just joined Kirkwood with reports of pow and more to come.

3 resorts:

Snow vibes! It’s getting white all over Sierra at Tahoe, Squaw Valley and Heavenly.

3 or more:

Wowza! Everyone’s abuzz with reports of snow. It’s now dumping at Sierra at Tahoe and Squaw Valley and 8 other resorts.


Examples of "initiate" with react-redux connect

Greetings.
I have the following pattern inside my app:
export const StorageConnectedView = connect(
  (state: MainState): StorageViewData => {
    const apiState = api.endpoints.getStorages.select()(state);

    const { data: storages = [] } = apiState;
    const status = extractStatus(apiState);

    const { selectedStorage } = getStorageViewState(state);
    return { status, storages, selectedStorage };
  },
  (dispatch: MainDispatch): StorageViewActions => ({
    onStorageCreation(storage) {
      dispatch(api.endpoints.createStorage.initiate(storage));
    },
    onStorageRefresh() {
      const { refetch } = dispatch(api.endpoints.getStorages.initiate());
      refetch();
    },
    onStorageClick(storage) {
      dispatch(selectStorage(storage));
    },
  })
)(StorageView);

Here the docs says the following:

When dispatching an action creator, you're responsible for storing a reference to the promise it returns in the event that you want to update that specific subscription. Also, you have to manually unsubscribe once your component unmounts. To get an idea of what that entails, see the Svelte Example or the React Class Components Example

I took a look at the React Class Component Example and found a similar pattern here but I fail to see the "unsubscription" as pointed by out at the docs.
Am I using refetchcorrectly? or do I need to keep the Promise returned by dispatch somewhere? is it possible to make a simple redux-react connect example like select has?
Thanks in advance, this library is truly a blessing.
Edit: Forgot to mention, the code works as intended, I am just afraid that I might be misusing the lib in some way, like subscribing again on each refresh/creation without unsubscribing (leaking resources)

Yeah, essentially it would be more complete like this:

  currentPromise?: ReturnType<ReturnType<typeof endpoints['getPost']['initiate']>>;

  componentDidMount() {
    const { id, getPost } = this.props;
    this.currentPromise = getPost(id);
  }

  componentDidUpdate(prevProps: PostDetailProps) {
    const { id, getPost } = this.props;
    if (id !== prevProps.id) {
      this.currentPromise?.unsubscribe()
      getPost(id);
    }
  }

  componentWillUnmount(){
    this.currentPromise?.unsubscribe()
  }

Perfect. Thank you very much @phryneas .
One last question: So, because these promises have a kind of "lifecycle" (initiate, use, unsubscribe, replace) they cannot be used inside a connect function, as in "plug and play", without further modifying the "Inner" component, right?
The code base I have has a lot of connected components, but the "Inner" components themselves are reusable FunctionComponents.
I am not against rewriting this "connect logic" where it fits, but before I do that I wanted to know if there is some alternative or pattern I could use.

I am closing this.
The better approach that I found is wrapping a connected component in a component that uses hooks or just not using a connected component. Anything other than that is possibly over engineering or edge cases.
My point on the codesandboxes is mentioned at https://github.com/rtk-incubator/rtk-query/issues/175#issuecomment-803011183
Thanks for the help

Yeah, or using something like https://www.npmjs.com/package/hook2hoc :)
Exposing the actions is super useful for use in other frameworks, but it's more to build abstractions on top than to really "day to day" use it by hand.


improve SubscribeForCancellation - trailing the oplog

Follow up to #84:
A few more tests:

Log before machine-job restart after running for a day - 8 ongoing COLLSCAN's that were not cancelled.  After restarting machine-job, the 8 subscriptions cleared - myfile.txt
Every active "SubscribeForCancellation" appears to be using 0.02 of a CPU - which I believe is the 8 filters trailing the oplog.  Is there any way to put less things on the oplog?  There appear to be thousands all the time...

Proposal - have one subscription on all translation engines.  When one changes, it looks for any cancellation  Or, by contrast, we could make one "cancellation subscription" that could also hold a list of all CancellationTokenSources of running jobs - and cancel if if it needs to, or drop the cancellation source if the job is no longer active.

This issue my be killed before it begins - Hangfire should be able to send a cancellation token without subscription.  This hack solution should be removed.


Assassin's Creed Odyssey: wrong aspect ratio and incorrect rendering

Assassin's Creed Odyssey seems to incorrectly assume that the display has an 4:3 aspect ratio and will display black bar at the top and bottom of the screen, no matter how much i fiddle with the settings.
Also there are rendering issues when running the benchmark mode on lowest settings like distorted npc's.
The apitrace i recorded goes only up until the main menu, where the game crashes, and thus will likely only be useful to debug the aspect ratio issue. I will also attach screenshots of the rendering issues, however useless they may be. Sadly i had to record the apitrace under dxvk as the game would not load with wined3d and i have no access to windows at the moment.
Another thing to note is that the performance is pretty poor, on lowest settings it struggles to even hold 30 fps; esync on/off doesn't seem to make a difference.
Software information
Assassin's Creed Odyssey all settings low.
System information

GPU: RX580
Driver: 18.2.1 (LLVM 7)
Wine version: 3.17 / 3.15-esync
DXVK version: v0.81-1-g87f1cd2

Apitrace file(s)
apitrace.xz
screenshots of incorrect rendering
Log files
d3d11.log
dxgi.log

Can't test on windows; I just got the game with my GPU and thought i might as well test it out.
FWIW i also tried spoofing an nvidia card, as the game seems to use amd_ags, but it has no effect.

Actually it doesn't even replay for some reason

Don't know what's wrong there, i just redownloaded the trace and it replays fine on my end.

Update:

The aspect ratio issue is a wine bug, not a DXVK bug. This doesn't happen on Windows.
The rendering issues are exclusive to Mesa 18.2, it renders fine with Mesa 18.3-git and LLVM 8.0.

Thanks for the feedback. I guess for the aspect ratio issue it might be worth filing a wine bug.
For me, the game first started with 640x480 resolution, and while it allows me to change the resolution correctly, it has the same black bars as it does on your end. On Windows with DXVK, it detects 1920x1080 correctly and has no black bars.

How did you get it to start? My installation seems to crash after the intro videos have played, any hints?

What's your wine version?
It's working for me pretty much out of the box with wine-staging 3.16 (+esync) and a fresh prefix that has only Uplay and DXVK in it.

Pretty much the same, tried a bunch of different versions, including 3.16 staging. Installed via lutris winesteam.
Would you mind sharing your ACOdyssey.ini from drive_c/users/you/My\ Documents/?

Pretty much the same, tried a bunch of different versions, including 3.16 staging. Installed via lutris winesteam.
Would you mind sharing your ACOdyssey.ini from drive_c/users/you/My\ Documents/?

Here you go (thank Github for being annoying and blocking certain file extensions):
ACOdyssey.ini.txt
FWIW I'm running the Uplay version of the game, not the Steam one. Maybe there are issues with that.

Great, thanks! With a few tweaks to my resolution settings it runs now :)
FullscreenWidth=1920
FullscreenHeight=1080
WindowedWidth=1920
WindowedHeight=955
WindowMaximised=0
RefreshRate=60
WindowMode=2

It seems like something around resolution detection is broken, i had a wonky refresh rate in there, and way to small widths/heights. Still have some rendering issues, but I that seems to be expected since I'm running mesa 18.2 and llvm 7.

Yes, resolution detection is broken, the only way to fix it currently is to run the game (but not uplay) in an appropriately-sized virtual desktop. But as mentioned in this thread, this is not a DXVK bug.

Great, thanks! With a few tweaks to my resolution settings it runs now :)
FullscreenWidth=1920
FullscreenHeight=1080
WindowedWidth=1920
WindowedHeight=955
WindowMaximised=0
RefreshRate=60
WindowMode=2

It seems like something around resolution detection is broken, i had a wonky refresh rate in there, and way to small widths/heights. Still have some rendering issues, but I that seems to be expected since I'm running mesa 18.2 and llvm 7. I've got the steam version, so at least DRM doesn't seem to be an issue.

hey, didn't that cause your FPS to decrease?


Icon in Add/Remove programs

Testing #33272
Add remove programs is a little ugly:

It's probably by design - but you can define a background color e.g. white it looks like.
Sean

"by design"

no, "by lack of design"

@chrisdias @weinand this is not "by design", we should pick the same background color as VS does. We are simply getting the blue default from windows it seems. Duplicate of https://github.com/Microsoft/vscode/issues/33362

A good designed icon would not use so many transparent areas that makes it dependent on background colours that are out of our control.
If I would configure my Windows to use an orange background colour, the VS Code icon would vanish completely...


ng update to v9-rc.5 removes dependency on @angular/pwa

🐞 Bug report
Command (mark with an x)

[ ] new
[ ] build
[ ] serve
[ ] test
[ ] e2e
[ ] generate
[ ] add
[x] update
[ ] lint
[ ] xi18n
[ ] run
[ ] config
[ ] help
[ ] version
[ ] doc

Description
Hi, this issue is another problem I had during ng update to the RC of v9. First is here: https://github.com/angular/angular-cli/issues/16392 – maybe it is related to each other.
We are using a PWA package and after ng update it gets missing. Ng update does not finish successfully, though (see issue mentioned above), so maybe this issue would be fixed at the later stage of the update command, but I feel better to create the issue to make awareness of this possible problem.

The removal of the @angular/pwa package is intended behavior.  Outside of ng add support, the package contains no other functionality and can safely be removed.  The new version of the package will also no longer save itself into the project when used with ng add.


How to use chronograf ? How to visit it after installed?

@sunguide this is not a feature request or bug report. Closing the issue as a result.
Once Chronograf has been installed, it runs on port 10000.

Please contact the mailing list<EMAIL_ADDRESS>for general support inquiries like this


feat(Icon): export call-missed-line-filled icon in Teams theme

Exported call-missed-line-filled icon

Please update the changelog's feature section with the message:

Export call-missed-line  icon in Teams theme @96andrei (#1203)

Warnings

:warning:
There are no updates provided to CHANGELOG. Ensure there are no publicly visible changes introduced by this PR.

  Generated by :no_entry_sign: dangerJS


Updated README.md

-Added a Reddit Bot
-Source: https://github.com/parshnt/covid-19-bot
-Relevant Thread: http://reddit.com/comments/g1zi21/_/fq8srgb

Nice!


Codebase reorganization step 1 - renaming

Renamed "WGS-HGT" as "Horizomer".
Created directory "horizomer" and moved old directories into it.

Looks good to me


ionicModal performance issue after a collection-repeat

A collection repeat listens for a resize event and does a heavy recalculation when it is fired. When a modal is shown, it triggers this resize event:
ionic.trigger('resize');

Because this is a heavy operation, it has performance impacts. The modal is not shown right away because each collection-repeat in the app has to go through it's resize recalculation.
I was able to temporarily fix this by commenting out that line in ionicModal.show(). It did not seem to have any negative side effects.
A possible improvement could be to only have the collection-repeat listen for this event when its view is currently active. That way a modal on another view will not be affected by it (and every other collection-repeat that has been shown in the app).

Greetings, @rickyk586!
We are now requiring all issues to be submitted through our custom issue form so that we have all of the information necessary to fix them as quickly as possible.
Your progress on this issue has been saved at the following url:
link to Ionic issue form
This issue will be closed if not resubmitted through the form. Please fill out the rest of the form so that we may assist you.
Thank you for allowing me to assist you.

@rickyk586 can you please share a codepen?

https://github.com/driftyco/ionic/issues/1912#issuecomment-70322365

I can confirm that the issue of the freezing/stuck of the Modal is related to collection-repeat and 'resize' event.
Commenting out the line from $ionicModal.show that trigger 'resize' event, fixes the problem.

The same issue related to performance for collection-repeat is occurring also each time the keyboard is shown on Android, causing the app freezing for several seconds. (I have about 500 items in the collection-repeat model).

I guess this problem was introduced with the cached views in beta 14. Moving the binding of the resize event listener in collection-repeat to enter and leave events, should probably fix this. No reason for a collection-repeat to listen for resize events when it's not visible, right?

@stianjensen yes, you are right.
I have fixed that in this way, inside the collection-repeat directive, but I'm not sure if this can affect some other behaviors. Anyway, I had some great improvements in terms of performances. But the problem related to this issue is that the ionicModal triggers the resize event when showing, causing the collection-repeat to re-render the list, so it's not related to the caching system.
  // panurge
  var requiresRerender, pauseRender = false;
  function rerenderOnResize() {
    // panurge
    if (pauseRender){
      return;
    }
    rerender(listExprParsed($scope));
    requiresRerender = (!scrollViewContent.clientWidth && !scrollViewContent.clientHeight);
  }

  function viewEnter() {
    if (requiresRerender) {
      rerenderOnResize();
      pauseRender = false;
    }
  }

  // panurge
  function viewLeave() {
    pauseRender = true;
  }

  scrollCtrl.$element.on('scroll.resize', rerenderOnResize);
  ionic.on('resize', rerenderOnResize, window);
  var deregisterViewListener;
  var deregisterViewListenerLeave;
  if (navViewCtrl) {
    deregisterViewListener = navViewCtrl.scope.$on('$ionicView.afterEnter', viewEnter);
    // panurge
    deregisterViewListenerLeave = navViewCtrl.scope.$on('$ionicView.afterLeave', viewLeave);
  }

  $scope.$on('$destroy', function() {
    collectionRepeatManager.destroy();
    dataSource.destroy();
    ionic.off('resize', rerenderOnResize, window);
    (deregisterViewListener || angular.noop)();
    // panurge
    (deregisterViewListenerLeave || angular.noop)();
  });

That's it, my app is REALLY slow because of it, when I open a modal it's just like hell!
Please, consider this issue <3

Checking this out.

Nice! I want to test it, does Ionitron has some delay to apply the last commit to ionic-bower?

It should be up now.

I can confirm that the issues #2890 is completely fixed in v1.0.0-beta.14-nightly-1011 :ok_hand:
Much better now, congratulations @ajoslin :smile:

Is it possible to know what was the fix exactly?
Thanks

With current nightly, it's not solved when the collection repeat is in a tab different from the one that opens the modal.
http://codepen.io/anon/pen/vERyVx
Switch to tab "Modal" click the button, the first time you open the modal, it's very slow.
Switch to ng-repeat and the first time the show transition is smooth.
If you cmment the ionic.trigger('resize') in the $ionicModal factory, also with the colleciton-repeat the show action is smooth.


[FEATURE] New Component For Remote Custom Model with Inference Endpoint, Schema (input & Output) and Target Field

Describe the feature you'd like
Let's say I have my custom model hosted at some remote server having an inference API endpoint. The inference API endpoint takes an input in a particular JSON format and output back in a particular JSON format. I should have a "Generic/Universal" component which I can drag & drop and specify the below:

Inference endpoint of the custom model (hosted in some remote server) to trigger.
Specify the schema of the input payload to the inference point and have the ability to map the input from the user to the field(s) in the schema.
Specify headers (in some cases for API keys).
Specify the output schema and have the ability to map field to choose for the output to the user.

Additional context
The idea here is to have a generic component having the ability to get inference from any server hosting custom model instead of limiting to Open AI, Hugging Face, Azure, Replicate, etc.

and of course being able to use whatever model, local or remote.

Yes I would like this feature too. Thank you


[Request]: Create new event by dragging / clicking inside the calendar

What feature would you like to add?
Is it possible to add a feature to trigger a Filament Action by doing the following:

click on specific hour inside a specific day
drag from one hour to another hour inside a specific day

Notes
No response

You can open a context menu on date click or date select.
There you can have any Action you want.

Merged in #22


Server Design should be like Local Design

Pictures should be orderd by date and album

blocked by imeji REST


Add MRArticleViewController by @mrigdon to UI section

Project URL
https://github.com/mrigdon/MRArticleViewController
Description
Add MRArticleViewController by @mrigdon to UI section
Checklist

[x] Only one project/change is in this pull request
[x] Addition in chronological order (bottom of category)
[x] Supports iOS 8 or later
[x] Supports Swift 3
[x] Has a commit from less than 2 years ago
[x] Has a clear README in English

          1 Error

  :no_entry_sign:
  Found 2 link issues

Link issues by awesome_bot

Line
Status
Link

1765
301
https://github.com/wtmoose/TLLayoutTransitioning redirects tohttps://github.com/SwiftKickMobile/TLLayoutTransitioning

1768
301
https://github.com/wtmoose/TLIndexPathTools redirects tohttps://github.com/SwiftKickMobile/TLIndexPathTools

  Generated by :no_entry_sign: danger

Is this danger a me problem?

Don't worry about that

Thanks for contributing! 🎉


appdef: States and Intents for commands and queries

IQuery must implement States(func(storage QName, names QNames)) (+builder)
ICommand must implement States(func(storage QName, names QNames)) and Intents(func(storage QName, names QNames)) (+builder)

To avoid escaping to the heap when using iterators, I also suggest adding the StatesMap()map[QName]QNames and IntentsMap()map[QName]QNames methods.

Question: Is it necessary to validate storage names passed to builder, what should be known?
  type IStoragesBuilder interface {
    // # Panics:
    //   + if storage name empty
    //   + if storage name is invalid
    //   + if storage names contains invalid name(s)
    //   ? if storage names contains unknown type name(s)
    Add(storage QName, names ...QName)
  }

As a result of the meeting with @michael-say
Interface members IState() and IIntents() should be moved to ancestor type IExtension.
All final types (ICommand, IQuery and IProjectors) should inherit these members.


Unable to query JWT right after user login using async / await and SwiftUI

Describe the bug
When I try and obtain JWT credentials immediately after login I get an error. Here is some code that can reproduce the issue.
class AuthCoordinatorBug: ObservableObject {

    //MARK: Published Properties
    @Published var userState: AppUserState = .notDetermined

    @Published var authSession: AuthCognitoTokens?

    @Published var authError: Error?

    //MARK: Other properties
    /// Get the current user user from the Amplify Framework.
    public var currentUser: AuthUser? {
        return Amplify.Auth.getCurrentUser()
    }

    init() {

    }

    @MainActor
    func signIn(username: String, password: String) async throws -> AuthSignInResult {
        return try await withCheckedThrowingContinuation { continuation in
            Amplify.Auth.signIn(username: username, password: password, options: nil) { result in
                switch result {
                case .failure(let authError):
                    continuation.resume(throwing: authError)
                case .success(let signInResult):
                    continuation.resume(returning: signInResult)
                }
            }
        }
    }

    @MainActor
    func fetchAuthSession() async throws -> AuthCognitoTokens {
        return try await withCheckedThrowingContinuation({continuation in
            Amplify.Auth.fetchAuthSession(options: nil) { result in
                do {
                    let session = try result.get()
                    guard session.isSignedIn == true else {
                        continuation.resume(throwing: AppSetupError.notSignedIn)
                        return
                    }
                    guard let cognitoTokenProvider = session as? AuthCognitoTokensProvider else {
                        continuation.resume(throwing: NSError(domain: "Auth Error", code: 400, userInfo: nil))
                        return
                    }
                    do {
                        let tokens = try cognitoTokenProvider.getCognitoTokens().get()
                        continuation.resume(returning: tokens)
                    }catch {
                        continuation.resume(throwing: error)
                    }
                }catch {
                    continuation.resume(throwing: error)
                }
            }
        })
    }
}

Here is some toned down SwiftUI code that Calls this.
import SwiftUI

/// Insert some documentation here
struct SimpleLogin: View {
    //MARK: Environment and State objects
    @StateObject var authCoordinator: AuthCoordinatorBug = AuthCoordinatorBug()
    //MARK: State and Binding objects
    @State var username: String = ""
    @State var password: String = ""
    @State var error: Error?
    //MARK: Other properties

    //MARK: View Body
    var body: some View {
        VStack(spacing: 20) {
            TextField("Username", text: $username)
            TextField("Password", text: $username)
            if let error = error {
                Text(error.localizedDescription)
            }
            Button(action: {
                login()
            }) {
                Text("Login").underline()
            }
        }
    }

    //MARK: Init if needed

    //MARK: Functions

    func login() {
        Task {
            do {
                let loginResults = try await authCoordinator.signIn(username: username, password: password)
                authCoordinator.authSession = try await authCoordinator.fetchAuthSession()
                authCoordinator.userState = .loggedIn
            }catch {
                self.error = error
            }
        }
    }

}

Steps To Reproduce
When this code is run in a project the
authCoordinator.authSession = try await authCoordinator.fetchAuthSession()

Line always fails with the error output described in the "Relevant log output" section below.
Expected behavior
I expect to be able to access the JWT Token information right after successful login.
Amplify Framework Version
1.25.0
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.0
CLI version
7.6.12
Xcode version
Version 13.4 (13F17a)
Relevant log output
AuthError: Unexpected error occurred with message: An unknown error occurred
Recovery suggestion: This should not happen. There is a possibility that there is a bug if this error persists. Please take a look at https://github.com/aws-amplify/amplify-ios/issues to see if there are any existing issues that match your scenario, and file an issue with the details of the bug if there isn't. Issue encountered at:
file: /Users/aviationresources/Library/Developer/Xcode/DerivedData/Aviation_Resources-ayyvwwaeeazntfdmyeemdjfefsem/SourcePackages/checkouts/amplify-ios/Amplify/Categories/Auth/Error/AuthError.swift
function: recoverySuggestion
line: 80
Caused by:
Error Domain=com.amazonaws.service.cognitoidentity.AWSCognitoCredentialsProviderHelper Code=0 "Obtaining an identity id in another thread failed or didn't complete within 5 seconds." UserInfo={NSLocalizedDescription=Obtaining an identity id in another thread failed or didn't complete within 5 seconds.}
2022-05-22 12:00:21.506776-0700 Aviation Resources[8999:2126921] [tcp] tcp_input [C3.1:3] flags=[R] seq=3334377424, ack=0, win=0 state=LAST_ACK rcv_nxt=3334377424, snd_una=2877796100

Is this a regression?
No
Regression additional context
No response
Device
All devices and simulators
iOS Version
15 +
Specific to simulators
No response
Additional context
No response

Note that if I sleep the thread like this:
let loginResults = try await authCoordinator.signIn(username: username, password: password)
Thread.sleep(forTimeInterval: 2.0)
authCoordinator.authSession = try await authCoordinator.fetchAuthSession()

I don't get the error. This is a hack though and I don't want to rely on it.

Thanks for opening this issue @joninsky.
In the code snippet sample, the binding for the password TextField should be $password, correct?
TextField("Username", text: $username)
TextField("Password", text: $password)

I presume that was just a typo in the issue, because it wouldn't cause the behavior you saw. I just want to make sure.
I was unfortunately not able to reproduce this issue with the example and information you provided. You mentioned that authCoordinator.authSession = try await authCoordinator.fetchAuthSession() always throws that error. Does it really happen every time you try, or does it succeed sometimes?
If you run your example with the Thread Sanitizer enabled, do you see any relevant output? If so, please paste them in your response here.
One thing you could try is moving the @MainActor attribute from the methods to the properties. This is a long shot, but it's worth trying in this case.
@MainActor @Published var userState: AppUserState = .notDetermined
@MainActor @Published var authSession: AuthCognitoTokens?
@MainActor @Published var authError: Error?

func signIn(username: String, password: String) async throws -> AuthSignInResult { ... }
func fetchAuthSession() async throws -> AuthCognitoTokens { ... }

Moving the @MainActor attribute resulted in more compile time errors about mutating that value from other threads. Yeah, the password was a typo. The error happens every time. I found a related issue.

Thanks for the follow up. Were you able to run with Thread Sanitizer turned on and was there any output? I'll spend some more time trying to reproduce it, but the TSan output from your case could be helpful.

Hello, I got the same error here, not only after login, it also happens after sign up. The fetchAuthSession  after login/signup just fails, unless I sleep the thread a little while.

Not sure if this helps, but in our case, this issue happens when we use the wrong user pool id and app client id on the identity pool. After we correct those configurations from the Federated Identities, everything works fine.

I am working on this draft PR that would potentially fix the issue.

We have released a fix for the issue with this PR - https://github.com/aws-amplify/aws-sdk-ios/pull/4202
Could you please try the new version of AWS iOS SDK to see if the issue still exists?


completion-nvim type window hidden by types in autocomplete list

I'm using nvim-lua/completion-nvim with neovim/nvim-lspconfig and ocaml-lsp.
For whatever reason, I get type info for completion items inside the autocomplete box, as well as the completion-nvim box.  Sadly, because completion-nvim tries to position itself to the right of the completion box, it winds up being partially or totally occluded by the latter
You can see that in this image, where I've circled the partially-hidden type-info box that completion-nvim provides.

Is there a way to disable the type info from being shown in the completion box?

I've found a way to remove the "kind" and "details" elements from the completion list:
local orig = vim.lsp.util.extract_completion_items
vim.lsp.util.extract_completion_items = function (...)
  local modified = orig(unpack({...}))
  for _, v in pairs(modified) do
      v.detail = ""
      v.kind = nil
  end
  return modified
end

A nice idea might be to truncate the detail entry to a certain string length. Deoplete does this as well for it's source, so it could make sense here.

A nice idea might be to truncate the detail entry to a certain string length. Deoplete does this as well for it's source, so it could make sense here.

Is there any point in showing details at all? Isn't that what we have completeopt=preview for?

@lithammer agreed, it seems like duplicated info


Map LDAP account attributes to labels such as groups #63

Updated:
I am proposing a configurable structure to leverage ldap account attributes as labels for access control. Let me know what you think.
I have added a labels mapping to the configuration, for example:
ldap_auth:
  ...
  filter: (&(|(userPrincipalName=${account})(userPrincipalName=${account}@example.com)(mail=${account}))(objectClass=person))
  labels:
    groups:
      attribute: memberOf
      parse_cn: true
    title:
      attribute: title

Can then be used with the current labels implementation like so:
 acl:
  - match: {labels: {"title": "Developer"}}
    actions: ["*"]
    comment: "If you call yourself a developer you can do anything."
  - match: {labels: {"groups": "Admin"}}
    actions: ["push"]
    comment: "If you are part of the admin group you can push."

Using title for an acl is probably a really dumb idea. But it proves you can map arbitary attributes to arbitary labels.
There is one special option, parse_cn which extracts the common name from a fully qualified value as found in memberOf.
Original:
I know little about LDAP and even less GO but I've taken the labels approach in #139 and populated groups to address #63.
  - match: {name: "docker_auth", labels: {"groups": "Admin"}}
    actions: ["*"]
    comment: "Admin users can do anything to docker_auth."

I'm simply looking through the account response for memberOf details. The alternative approach for ldap would be to look up groups and find member accounts.
A similar approach might be useful for #117

This change is

@kcd83 thanks for the contribution! this looks very reasonable to me, but then again - i know very little about LDAP too.
have you actually used it yourself? if not, i'd like someone who actually uses LDAP to confirm that this works.
maybe @summerQLin can comment

Apparently modern AD installations/ configurations don't necessarily expose memberof and/or may prefer impersonation... anyone with ldap experience able to comment?

Is there any chance to merge this soon and split the AD part into a separate issue?

Hi,
I checked this on top of master and I can confirm it is working!
It is usable as-is so please merge it.
The problem with this approach is that the memberOf resolution does not support recursive groups. However, even with immediate groups there is a value.
Validated with AD.
I do need recursive groups so I ended up with the following filter instead of using this patch:
    (&(sAMAccountName=${account})(objectClass=person)(memberOf:1.2.840.1135<IP_ADDRESS>1:=CN=XXX,OU=YYY,DC=X))

This is not flexible as I wish it to be... as I can use only single recursive group.
It is hard for me to imagine how in this generic attribute -> label approach a recursive solution may be built without code change. For active directory a list of filters to check recursive each group provides a resolution, for example the following will set in_group1 to "group1" if user is recursively in group1.
  filters:
    base:
      filter: <this is the base filter as currently implemented
    group1:
      filter: (&(sAMAccountName=${account})(objectClass=person)(memberOf:1.2.840.1135<IP_ADDRESS>1:=CN=group1,OU=YYY,DC=X))
      labels:
        in_group1:
          attribute: cn

In other directories it is hard to perform this without recursion. As groups are so important, maybe a special behaviour is needed.
Thanks!

@kcd83 any chance to update it to @alonbl's comments so it could be merged? :)

@mrueg @alonbl I have added the example configuration to reference.yml
I agree that additional queries of groups would be great but it isn't something I'll be able to look at. Mostly because this is all the Go I've ever written and I could barely remember how to build it :)

Thanks @kcd83! As I wrote, this patch is helpful as-is, the group thing can be added later.

please address @alonbl 's comments about examples and docs and this can be merged. thanks!

Whoops i was supposed to call that group not groups to match the existing acls. Would it be worth saying "see the group acls below" or similar also?
 - match: {labels: {"group": "VIP"}}
    actions: ["push"]
    comment: "Users assigned to group 'VIP' is able to push"
  - match: {labels: {"group": "/trainee|dev/"}}
    actions: ["push", "pull"]
    comment: "Users assigned to group 'trainee' and 'dev' is able to push and pull"

You gave a great example in your comment#0 :)
I tested based on that...
acl:
  - match: {labels: {"title": "Developer"}}
    actions: ["*"]
    comment: "If you call yourself a developer you can do anything."
  - match: {labels: {"groups": "Admin"}}
    actions: ["push"]
    comment: "If you are part of the admin group you can push."

yes, a nice comment will be helpful as well.

@kcd83 Thank you for this nice feature!
Are there any estimates on when this could be good to merge and released?
My use case is to authenticate and authorize users with JumpCloud LDAP, the Jenkins Integration Guide has some examples to filter by user groups

I think I addressed all the suggestions.
I don't think this is the place for an LDAP tutorial however, particularly because it is a very limited implementation. The examples can be used and someone with more ldap knowledge could improve this in time.
Ok to merge?

Hi,
This probably has no support for RFC 2307 style where group membership has members listed on the group object rather than using groups listed on user object?

@kcd83 Thanks for you hard work! Can't wait to have this changes in a release. Would you have some time to rebase your branch onto current master so that there will be no conflicts and to make it easier for @rojer to merge it by just pressing the merge button?
@rojer do you think this PR is good to be merged?

@kcd83 can you update this PR to remove the file conflicts?
@rojer I've been using this patch for quite a while, it works well. Can we get it merged?


Initial structure for datasets

Description
Provides a dataset implementation that can be used for most of the QM Datasets provided generated from the QCArchive and provided as HDF5file.
For a specific dataset (e.g. QM9) generating a dataset is as easy as:
factory = DatasetFactory()
prop = QM9Dataset()
dataset = factory.create_dataset(prop)

and the dataset provides Pytorch Dataloader for a default data split (random split, 80:10:10).
The split can be stored and reproduced using dataset.store_split(filename) and dataset.restore_split(filename.
The DatasetFactory() will first check if there the dataset is already  cached on disk, if not it will download the dataset specified in prop and generate a local cache. The local cache is a npy file. Padding is performed by the  PadTensors class.
Currently only the   RandomSplittingStrategy is implemented, and will be used by default in the factory.create_dataset call, but other splitting strategies (e.g. TimeSplit) can be implemented.
Todos

[x] implement DatasetFactory that generates a dataset with a specified splitting and dataloader that are ready for use
[x] implement Caching class
[x] implement Download class
[x] implement utility functions such as :  PadTensors, SplittingStrategy, decompress_gziped_file
[x] implement QM9Dataset
[ ]  all tests are passing
[ ] pass custom list of properties that are retrieved from hdf5 file

Status

[ ] Ready to go

I think for the HDF5dataset we need to have an abstract class for download, to ensure any derived classes define where to retrieve the data.   I think in a future PR we need to workout how exactly we want to control the ability of a user to define the source of the dataset (e.g., from zenodo, google drive, local source).  Depending on what is passed to the constructor, the behavior of download() would be adjusted accordingly.

The good news is test are passing, but they seem to be taking way too long, considering we aren't doing too much.
I timed (locally) the tests and these are the top 8 (I'm only reporting things that took more than a minute):
test_different_scenarios_of_file_availability -- 159.45s
test_file_cache_methods -- 159.23s
test_numpy_dataset_assignment -- 83.81s
test_dataset_dataloaders -- 82.80s
test_data_item_format -- 82.56s
test_dataset_splitting -- 82.52s
test_dataset_generation -- 81.30s
test_file_existence_after_initialization — 80.22s
Not surprisingly, these all include dealing with the dataset in some fashion.

A quick test did shave some time off the test by using a local copy of the datafile.  Obviously for functions where we want to test downloading records this makes sense to use the remote copies, but I feel as though we should include one of the small dataset files in a data folder under tests to remove this overhead (but I think we should hold off until I upload new datafiles with the different unit system we decided on).

The most significant savings was by using a smaller dataset file. Switching to the 100 records file instead of 1000 cut the test_numpy_dataset_assignment down to a few seconds.  I uploaded this dataset to the google drive and there was no difference between local and remote copy.  I couldn't figure out how to profile download speed easily in pytest, but I wouldn't be surprised if download speed is higher for smaller files than larger files on the CI nodes.   The n100 dataset for testing is below.  Obviously subbing this in would require changing the test/train/val split numbers by a factor of 10 (as that was based on 1000).
  self.test_id = "17oZ07UOxv2fkEmu-d5mLk6aGIuhV0mJ7"

Let's merge this PR and address all open suggestions in separate PRs

Did you forget to add in transform.py?

ModuleNotFoundError: No module named 'modelforge.dataset.transformation'
31


Adjust maximumByteSize for a POST request based on event latency

See: https://github.com/snowplow/snowplow-android-tracker/issues/244

Closing because it has been with no activity for a long time.
Please, feel free to reopen or comment this issue, whether it's of your interest or you want to contribute on this.


Why can't ansible module complete automatically?

Describe the bug
Vscode installed ansible language, unable to complete automatically

Closing as this will be sorted as part of #135


[rpc] Unable to use next.js cache

What version of Effect is running?
3.10.19
What steps can reproduce the bug?
export class UserByEmail extends S.TaggedRequest<UserByEmail>()('UserByEmail', {
  failure: S.Union(
    S.instanceOf(UnknownDatabaseError),
    S.instanceOf(UserNotFoundError),
  ),
  success: selectUserSchema,
  payload: { email: userEmailSchema },
}) {}

export const userRouter = RpcRouter.make(
  Rpc.effect(UserByEmail, async ({ email }) => {
    'use cache';

    const res = Effect.gen(function* (_) {
      const db = yield* DBClient;

      const user = yield* _(
        Effect.tryPromise({
          try: () =>
            db.query.users.findFirst({
              where: (users, { eq }) => eq(users.email, email),
            }),
          catch: (error) =>
            new UnknownDatabaseError({
              message: `${error}`,
            }),
        }),
        Effect.filterOrElse(
          (user) => !!user,
          () => new UserNotFoundError(),
        ),
      );

      return yield* Effect.succeed(user);
    }).pipe(Effect.provideService(DBClient, db));

    return res;
  }),
);

export type UserRouter = typeof userRouter;

const handler = RpcRouter.toHandler(userRouter);
const resolver = RpcResolver.make(handler)<typeof userRouter>();
export const client = RpcResolver.toClient(resolver);

To try to cache this function and figure out what:

Need an asynchronous function (No rpc documentation, so I'm using Rpc.effect because I don't know what else I can do)
Understand that the returned result is Effect or Exit, which cannot be another value (otherwise ts error), and such a value cannot be cached because it is not serializable, and you cannot return an encoded value because you need an effect

What is the expected behavior?
without error
What do you see instead?

Additional information
No response

I don't know enough about the internal mechanism involved, but I can tell you that the "use cache" is in an invalid location. Nextjs does not understand this kind of execution strategy, it would expect something like this
const foo = async () => {
 "use cache";
  const res = await runPromise(doFoo)

  return res
}

rather than something like this:
const foo = async () => {
  const doFoo = async () => {
   "use cache";
    // ...
  }

  const res = await doFoo()

  return res
}

There are too many variables involved, I cannot narrow down a useful answer I'm afraid

I don't know enough about the internal mechanism involved, but I can tell you that the "use cache" is in an invalid location. Nextjs does not understand this kind of execution strategy, it would expect something like this

Yes, indeed, I can't cache because the function used inside Rpc.effect is not asynchronous.
Moreover, even if it is asynchronous, I can't cache anyway because it returns effect which is not a serializable value. If I make it Exit, then exit can return but it is also not a serializable value. When I try to code Exit, I'm already getting complained by ts that the return type is not appropriate

RPC is not really meant to be used with next.js "use cache", that's a specific directive to apply to next.js functions

Reference in new

Well, yes, I don't argue that @effect/rpc was not specifically intended for next.js, but it's strange that it doesn't work. Code comes in different forms as do libraries/frameworks too. It's weird to hope that package.json will only have effect and nothing else.

Reference in new

Well, yes, I don't argue that @effect/rpc was not specifically intended for next.js, but it's strange that it doesn't work. Code comes in different forms as do libraries/frameworks too. It's weird to hope that package.json will only have effect and nothing else.

that is not the hope, Effect is written in plain JS so we don't make any assumption. The issue here is that next.js uses custom directives that are outside of the JS specification so the behaviour is specific to the patterns they want to support. In this case the pattern they want to support is caching single functions.

Reference in new

Well, yes, I don't argue that @effect/rpc was not specifically intended for next.js, but it's strange that it doesn't work. Code comes in different forms as do libraries/frameworks too. It's weird to hope that package.json will only have effect and nothing else.

Also we've kept answering but your way of saying things is really demotivating and entitled, unless you change and be positive in engaging we're simply going to stop providing help.

Also we've kept answering but your way of saying things is really demotivating and entitled, unless you change and be positive in engaging we're simply going to stop providing help.

I do not put any negativity into my posts. If I did, I wouldn't care and I just wouldn't use effect, and so, you see, I leave feedback and try to help develop it. Because let me remind you, the lib is really hard to understand and present itself to other people.
I don't want to demotivate you because I like the library and there are some really cool solutions and combinations, like the built-in ‘pattern matching’, the pipe function which I like, the use of generator functions to make it look like normal code and that's great, the built-in validation.
For you as a developer of this library, or maybe not a developer but a long time user of this library, you understand everything in effect. But I think most people just don't like the way the library is made and its design. This is proved by the stars on github, because it is not clear how a library that has 1,5 million downloads on npm has 10k, while trpc of the same library has 2 times less downloads and 2 times more stars.
Rather demotivating is your attitude towards that same library and its use, because all the response I get is ‘well that's the way it's done, that's the way we came up with it, we're not going to change anything’.
‘Your library doesn't mix with major frameworks?’ - ‘well, not our problem. Next.js doesn't fit the js specification’. Although as far as I know, user directives will be as a separate feature soon, if it's not already contributed and it will be part of the js spec.
‘Why write boilerplate code and repeat the same expected errors?’ - ‘Well, if you don't care so much, use S.Any.’
‘Your library is inconvenient to use’ - “Well, that's the way we designed it”.
Half of the objects in rpc/platform I don't understand what they do and find examples from github -> test file, their api is on another site. Yes, you can say about it that they don't have a major version there, but I think a lot of libraries don't have a major version, and popular ones at that, such as drizzle orm, but I haven't had so many issues or inconsistencies there.
Certainly, my words are not a panacea, and some points - this is a taste, but still, I think that something should be changed, and it looks like I'm not the only one who thinks so.

Given that even this interaction turned out to be negative I have no choice but to prevent you from interacting in the repo.

Also we've kept answering but your way of saying things is really demotivating and entitled, unless you change and be positive in engaging we're simply going to stop providing help.

I do not put any negativity into my posts. If I did, I wouldn't care and I just wouldn't use effect, and so, you see, I leave feedback and try to help develop it. Because let me remind you, the lib is really hard to understand and present itself to other people.
I don't want to demotivate you because I like the library and there are some really cool solutions and combinations, like the built-in ‘pattern matching’, the pipe function which I like, the use of generator functions to make it look like normal code and that's great, the built-in validation.
For you as a developer of this library, or maybe not a developer but a long time user of this library, you understand everything in effect. But I think most people just don't like the way the library is made and its design. This is proved by the stars on github, because it is not clear how a library that has 1,5 million downloads on npm has 10k, while trpc of the same library has 2 times less downloads and 2 times more stars.
Rather demotivating is your attitude towards that same library and its use, because all the response I get is ‘well that's the way it's done, that's the way we came up with it, we're not going to change anything’.
‘Your library doesn't mix with major frameworks?’ - ‘well, not our problem. Next.js doesn't fit the js specification’. Although as far as I know, user directives will be as a separate feature soon, if it's not already contributed and it will be part of the js spec.
‘Why write boilerplate code and repeat the same expected errors?’ - ‘Well, if you don't care so much, use S.Any.’
‘Your library is inconvenient to use’ - “Well, that's the way we designed it”.
Half of the objects in rpc/platform I don't understand what they do and find examples from github -> test file, their api is on another site. Yes, you can say about it that they don't have a major version there, but I think a lot of libraries don't have a major version, and popular ones at that, such as drizzle orm, but I haven't had so many issues or inconsistencies there.
Certainly, my words are not a panacea, and some points - this is a taste, but still, I think that something should be changed, and it looks like I'm not the only one who thinks so.

No other choice but to block such user, no point arguing when the OG acts in bad faith.


RSS feed structure audit

Let's do a bit of an audit of Ghost RSS feeds vs WP RSS feeds, because there's quite a lot of difference at the moment. Eg.
http://john.onolan.org/rss/
vs
http://blog.kissmetrics.com/feed/
I'm fine with the two being different, but I'd like to make sure we're structuring feeds differently for the right (or at least some) reasons.
Are we using the correct tags? Are we missing any?

I've taken a brief look at this today, and identified a few things that we definitely need to (and also can quite easily) fix:

Content-Type header
I changed this a little while ago, because Chrome was doing something awful with text/xml that made the page look like an error to many users. It seems that Chrome has since bucked its ideas up and we should go back to text/xml.

Content vs Description
We very deliberately do not include just a description in our RSS feeds, however we have been misusing the description field to include the full content. Now that node-rss supports custom namespaces and fields, we should use the content module, and change the description to include just the meta description.

PubDate vs lastBuildDate and ETAGs
This bug describes an issue with ETAGs on our RSS feeds, however unfortunately simply setting the pubDate doesn't solve the problem because the lastBuildDate will still get updated every time the feed is requested. We need to either convince the node-rss library to change this behaviour, or we need to change how and when we generate our RSS so that it doesn't keep changing.

Overuse of CDATA
One thing that's pretty glaring when you compare our feeds to other people's is the use of CDATA to wrap everything. This is unnecessary, it's only really an aesthetic problem, but it's already raised as an issue on node-rss so perhaps we can get this improved.

Content-Type header: you should probably use application/rss+xml and application/atom+xml...
Content vs Description: I'd say it's not a big deal if you put the full content in description
PubDate vs lastBuildDate and ETAGs You should distinguish the first 2 and the 3rd one (which is HTTP level and has no schema AFAIK). Also, I think the current behavior (where lastBuildDate is updated every time you generate the XML) is the right one.
Overuse of CDATA that indeed could be improved, but that's not technically a bug. Just a nice-to-have feature.

@julien51, thanks for your input on this. Could you please provide the reasoning behind some of your statements? application/rss+xml doesn't appear to be treated correctly by chrome and the majority of feeds that I checked use text/xml, hence my proposal to switch back.
Also, as far as I am aware, updating last build date when the content hasn't changed causes the issues explained in #2777, so again I'm interested in your reasoning?

Sure!
Well, it's a fact that Chrome does not support RSS/Atom anymore and hence will behave badly. But the spec is clear. Now, text/xml is not the worst choice you could make.
To be honest, I don't understand the link between the Etag header (which can be anything) and the value of last-build. But there agin, I would point to the spec for lastBuildDate.

The last time the content of the channel changed.

Also, you could remove this from the RSS feed altogether since it's optional.

Looking at a wide sample of blogs online (including @haneefmubarak's list) the overwhelming majority are using text/xml, including all of medium, tumblr and wordpress. The bbc & buzzfeed use application/xml which seems like a middle-ground. I'm punting for text/xml because it's so common.
As for the ETAG, it's generated by express based on the content. Currently the last build date incorrectly changes every time the RSS feed is requested, rather than every time the feed content changes. The change in the date causes the ETAG to change. Removing the lastBuildDate would require an upstream change to the node-rss library, but it would be more efficient for us to stop regenerating it every time it is requested.

+1 for content vs description, would make RSS driven emails far simpler!

So I'm trying to implement reading the paginated rss feeds in another project, and from what I can tell the links for the next/previous pages don't exist in the feeds created. I haven't had much time to dig through the code, but I'd be willing to fix it.

Hi @amm4108, please correct me if I'm wrong, but I'm not sure that there is a standard concept of previous/next links for RSS? Our RSS feeds being paginated is kind of a weirdness, we should really remove it, but we've left it in as a fallback until our API is fully ready.

Hey @ErisDS I was looking through the docs linked, http://www.ibm.com/developerworks/library/x-tipatom2/, http://tools.ietf.org/html/rfc5005#section-3. The examples on both of these show having previous/next links as well as talking about them a little bit before hand.

@amm4108 ah I see! Still it seems like it would be the wrong thing to do, to add those links making the pagination more discoverable when ultimately we plan to remove it as soon as the API becomes properly available?

From https://github.com/TryGhost/Ghost/pull/5065#issuecomment-89817256, @adrianmacneil said:

Would it also be possible to include the post image as a separate element? It seems there are a few different standards for this, possibly the media:content tag is the right choice for this (and anecdotally is supported in mailchimp which is what we need it for).

I have done a bit of research into this, looking at example fields, and it certainly appears to be the most widely supported way of including images in RSS. The reason it wasn't done this way in the original issue was because we weren't able to add custom elements to the feed + although being the most widely supported way, the media:content element is not very widely supported.  It appears to be supported by both mailchimp and campaignmonitor making it very useful for designing nicer email campaigns. However, it seems that IFTTT pulls images from the content, as does feedly.
Now that we are able to add custom elements & namespaces adding this is straightforward, however I think it needs to be added in addition to prepending the image to the content:encoded element but not prepend it to the description element. This seems to create the best balance - meaning feeds look good in feedly & other readers, whilst still being customisable in rss-to-email campaigns.

Thanks @ErisDS, that solution works for us. We will be using the description element with mailchimp (for now), so having the image excluded from description will be fine.
It's a shame feedly does not support the media:content element so we could keep description and content:encoded consistent.

With the exception of sy:updatePeriod, sy:updateFrequency and some stuff related to comments which isn't currently relevant with Ghost the two feeds are now pretty much identical. I've also spent some time looking at a lot of other feeds, and looking at how Ghost feeds work with 3rd parties and I'm pretty happy that we've got a much better offering now.
With regard to sy:updatePeriod, sy:updateFrequency I think these might be worth adding in future if we do more work around coming up with smart numbers for these to use both in RSS and the sitemap, but with the lastBuildDate & ETAGs now working properly on our feeds I'm not convinced adding defaults for these would add value right now.
I think this issue can be closed?

@EricDS Yes, this issue could be closed. (Too bad that summary feeds won't exist before the hypothetical release of Ghost Apps).

If I recall correctly, @wilfriedE used Ghost in spring 2016 and might be able to help us test this.


Improve appearance of login modal

Consult a UX person to design it properly.

so this is what Lihi designed:

this is where my implementation stands:

i need some help/tips :

how do i change the google button to google+ button ?
adding the maximize/minimize buttons in the modals header next to the "x" button. i guess its bootstrap/backbone involved but i couldn't find any helping implementation on the web ( i never used bootstrap nor backbone so i need something to work with :) ).

will be glad if anyone can help.
Thanks

First of all, I think these are already better and I would be happy to
merge them if you create a pull request
Second, Google provide their own button and encourage you to use it:
https://developers.google.com/identity/branding-guidelines#g+signin-social-scopes
So does Facebook:
https://developers.facebook.com/docs/facebook-login/best-practices
Third, I don't think the maximize button is really necessary.
Thanks
On Mon, Apr 4, 2016 at 11:36 PM sivanb<EMAIL_ADDRESS>wrote:

so this is what Lihi designed:
[image: login modal design from lihi]
https://cloud.githubusercontent.com/assets/10827288/14262190/d965b968-fabc-11e5-9bb8-58ac99347a85.png
this is where my implementation stands:
[image: login modal current status]
https://cloud.githubusercontent.com/assets/10827288/14262255/4578307c-fabd-11e5-8c1c-2408d94e84f9.png
i need some help/tips :

how do i change the google button to google+ button ?
adding the maximize/minimize buttons in the modals header next to the
"x" button. i guess its bootstrap/backbone involved but i couldn't find any
helping implementation on the web ( i never used bootstrap nor backbone so
i need something to work with :) ).

will be glad if anyone can help.
Thanks
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/552#issuecomment-205483005

no problem , i'll create a pull request ,hopefully today.
will try updating the buttons first.
and i'm with you on the maximize button :)

did we have google signin or facebook signin button working ?
because their not working in my local site.
if i'm going to change google button to G+ , am I to go through the entire process of creating an app ID and everything described on google guidelines page ?

They work on the production site, but since the setting is url specific
they don't work when running locally.
On Mon, Apr 11, 2016, 18:51 sivanb<EMAIL_ADDRESS>wrote:

did we have google signin or facebook signin button working ?
because their not working in my local site.
if i'm going to change google button to G+ , am I to go through the entire
process of creating an app ID and everything described on google guidelines
page ?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/552#issuecomment-208414882

ok after consulting Avi i understand that google and facebook login buttons are created using bootstrap and font-awesome so i went and added bootstrap CDN links to html and updated font-awesome css CDN link + a few small html/css additions and this is what i have now (not so different then what we have now):

a few things:
1. there is no G+ button when using the current social buttons source - how critical is it ?
2. we have local bootstrap files (css, javascript) in the project - i understand there are pros and cons for using CDN vs. local files ,what do we prefer ? local files makes loading faster and its important to us as long as the server is weak ? do we make changes (is that a good practice ) in bootstrap css file thus we need the local file ?
3. apart from the issue i can see with updating the css (mentioned above) -do i need to somehow test the entire site and see how my changes influence ?

Looks good.

What do you mean about the G+ button? Google supply their own button.
I don't think there's a reason to use local files. If anything, using the CDN files will be faster.
You should test around the site after your changes to see it all works.

ok , here is my final try using bootstrap ( did find it after all)

since its my first time tempering with bootstrap there are some things i dont understand thus my questions. some reading is required :)
anyhow , i'm going to delete the bootstrap css, js, fonts local files.
go over the site to make sure i didnt ruin anything.
i also need to check that G+ sign in actually works since what i did is just change the button icon , what about functionality ? i guess i need to change the authorization code behind to enable google+ sign in? how do i go about doing that ? is it just changing the oauth module ?

I believe Google authentication works already. Doesn't it?
On Tue, Apr 19, 2016, 00:12 sivanb<EMAIL_ADDRESS>wrote:

ok , here is my final try using bootstrap ( did find it after all)
[image: screenshot from 2016-04-19 00 11 18]
https://cloud.githubusercontent.com/assets/10827288/14620037/450300fc-05c3-11e6-9004-75f6485545ed.png
since its my first time tempering with bootstrap there are some things i
dont understand thus my questions. some reading is required :)
anyhow , i'm going to delete the bootstrap css, js, fonts local files.
go over the site to make sure i didnt ruin anything.
i also need to check that G+ sign in actually works since what i did is
just change the button icon , what about functionality ? i guess i need to
change the authorization code behind to enable google+ sign in? how do i go
about doing that ? is it just changing the oauth module ?
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/hasadna/anyway/issues/552#issuecomment-211580003

ok , here is my final try using bootstrap ( did find it after all)

since its my first time tempering with bootstrap there are some things i dont understand thus my questions. some reading is required :)
anyhow , i'm going to delete the bootstrap css, js, fonts local files.
go over the site to make sure i didnt ruin anything.
i also need to check that G+ sign in actually works since what i did is just change the button icon , what about functionality ? i guess i need to change the authorization code behind to enable google+ sign in? how do i go about doing that ? is it just changing the oauth module ?

yes , Google authentication is working but isn't there a difference between Google and Google+account with regard to authentication ?

Right.
We currently use Google OAuth 2.0 authentication.
Here are instructions for migration to Google+ Sign In.
If you want you can try changing that in oauth.py, but I understand the difference is just access to more fields from the user's Google+ account, whereas we only use the name and email, which are also available with Google OAuth 2.0. Still, it will be nice if you can get it to work.
We already have the client ID and key set in our server.

ok ,just one question that comes to mind before i start : how can i test it ? (authentication is not working in my local site )

You can deploy your code to your own Heroku and set the environment variables there.
Then you can test with the OAuth 2.0 Playground.

great , thanks


Get coordinates of current position

Hello,
is it possible to get the current location of the Device and use it to calculate the distance between two points without using the cordova-plugin-geolocation?
var myCurrentPosition = ?
var someOtherPositon = {"lat": 32, "lng": -97};
plugin.google.maps.geometry.spherical.computeDistanceBetween(myCurrentPosition, someOtherPositon);

Currently using Version 2.1.1 of your Plugin with Ionic.
Best Regards
Marius

https://github.com/mapsplugin/cordova-plugin-googlemaps-doc/blob/master/v2.0.0/class/Map/getMyLocation/README.md


#40 Add ability to query on document ids

This pull request updates the logic to support using where clause to find documents by id.
The way to do it is to use the special name __id.
// Given objects in database having ids like "obj2" and "obj3", can fetch them using this:
$results = $db->query()->where('__id', 'IN', ['obj2', 'obj3'])->results();

This update was accomplished by updating Document::field() to accept an argument value of "__id" which will return the objects (internal) id.

Pull Request Test Coverage Report for Build 133

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.04%) to 92.885%

Totals

Change from base Build 130:
-0.04%

Covered Lines:
483

Relevant Lines:
520

💛  - Coveralls


Update Code Sponsor link position

@matcornic When the link is found at the bottom of the README, it is more effective in helping funding this project.

Codecov Report

Merging #20 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #20   +/-   ##
=======================================
  Coverage   98.06%   98.06%
=======================================
  Files           3        3
  Lines        1033     1033
=======================================
  Hits         1013     1013
  Misses         14       14
  Partials        6        6

Continue to review full report at Codecov.

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


Add port and sb devlink syscalls

Patch 1: Cleanup and update of syzkaller const to the latest linux-next.
Patch 2: Add the new syscalls.

Please rebase, the patches seem to be based on an older version.


Minor Update: Entity Category DIAGNOSTIC

Set Entity Category attribute to DIAGNOSTIC for all binary sensors (power flow), "self sufficiency" and Last update" sensors.

Hi Maurizio, can you fix linting problem? https://github.com/wilds/hass-atonstorage/actions/runs/7104778368/job/19340537326?pr=24


[Improvement] Introduce specified initialized SQL file to every engine

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
As of nowadays,  the configuration key kyuubi.engine.session.initialize.sql is used in both Flink and Spark engines.  To specify the initialized SQL for each engine, we need to introduce a separate key.
For example:
kyuubi.engine.flink.initialize.sql
kyuubi.engine.flink.session.initialize.sql
kyuubi.engine.spark.initialize.sql
kyuubi.engine.spark.session.initialize.sql
How should we improve?
Add new ConfigEntries to Flink and Spark engines
Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

I understand this task and want to have a try, l suppose l can complete it in 3 days.


Add continuous deployment

Add automagic deployment when rebase-merging master

Added auto-deploy when merging on master!


CI Tests: Create cucumber suite for random mode data generation.

Create a feature file of tests to validate the behaviour of random mode across validating and violating data generation strategies for all constraints.
Acceptance Criteria:

[ ] Scenarios created to confirm RANDOM can produce some data at least for each data type
[ ] Scenarios created to ensure correct number of rows are emitted
[ ] Scenarios created and documented and run to confirm and identify issues with RANDOM generation
[ ] Issues created for any unexpected behaviour

How much of the random generation testing should be unit, and how much should be cucumber?

Blocked by #545


chore(deps): update to last Backstage versioning

Hello
I've updated last Backstage versions. Can you please create a release @K-Phoen  ?
Thank you :)

Done in #47, thanks! :)


https error for some SSL links

ConnectionError: hostname 'example.com' doesn't match either of 'ssl2000.cloudflare.com', 'cloudflare.com', '*.cloudflare.com'

Fixed this by installing some libraries


cryptsetup: drop manual -lgcc_s flag

Description of changes
Introduced in 397f5c37df025e561b0cc94e71077fa0a06679f6 — it seems to have a negative effect those days at configuration time.
It does not affect static builds.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

The following packages specified with -p are not rebuilt by the pull request
pkgsMusl.cryptsetup pkgsMusl.cryptsetup.dev pkgsMusl.cryptsetup.debug pkgsStatic.cryptsetup.man pkgsMusl.cryptsetup.bin pkgsStatic.cryptsetup.dev pkgsStatic.cryptsetup.debug pkgsStatic.cryptsetup pkgsStatic.cryptsetup.bin pkgsMusl.cryptsetup.man

Result of nixpkgs-review pr 257420 run on x86_64-linux 1

5 packages built:

cryptsetup
cryptsetup.bin (cryptsetup.bin.bin ,cryptsetup.bin.debug ,cryptsetup.bin.dev ,cryptsetup.bin.man)
cryptsetup.debug (cryptsetup.debug.bin ,cryptsetup.debug.debug ,cryptsetup.debug.dev ,cryptsetup.debug.man)
cryptsetup.dev (cryptsetup.dev.bin ,cryptsetup.dev.debug ,cryptsetup.dev.dev ,cryptsetup.dev.man)
cryptsetup.man (cryptsetup.man.bin ,cryptsetup.man.debug ,cryptsetup.man.dev ,cryptsetup.man.man)

@ofborg build pkgsCross.musl64.cryptsetup pkgsMusl.cryptsetup pkgsStatic.cryptsetup pkgsMusl.pkgsCross.gnu64.cryptsetup

Should target staging

https://logs.ofborg.org/?key=nixos/nixpkgs.257420&attempt_id=00b64271-aa9e-4de7-9290-86cf3d147789
error: builder for '/nix/store/5y4d2rfy0p8q278czch1a4fhdfkrfri0-check-x86_64-unknown-linux-musl-0.15.2.drv' failed with exit code 2;
       last 10 log lines:
       >                  from libcompat.c:21:
       > /nix/store/kgnb85sbyv0vckwrr2dnydw68dni840x-fortify-headers-1.1alpine3/include/stdio.h:80:1: error: 'vsnprintf' undeclared here (not in a function); did you mean 'vsprintf'?
       >    80 | _FORTIFY_FN(vsnprintf) int vsnprintf(char * _FORTIFY_POS0 __s, size_t __n,
       >       | ^~~~~~~~~~~
       > compilation terminated due to -Wfatal-errors.
       > make[2]: *** [Makefile:421: libcompat.lo] Error 1
       > make[2]: Leaving directory '/build/check-0.15.2/lib'
       > make[1]: *** [Makefile:566: all-recursive] Error 1
       > make[1]: Leaving directory '/build/check-0.15.2'
       > make: *** [Makefile:412: all] Error 2
       For full logs, run 'nix log /nix/store/5y4d2rfy0p8q278czch1a4fhdfkrfri0-check-x86_64-unknown-linux-musl-0.15.2.drv'.
error: 1 dependencies of derivation '/nix/store/7c0i715hp7z9ymgjzjwgc5kxld617vk5-kbd-x86_64-unknown-linux-musl-2.6.2.drv' failed to build

@OfBorg test installer.luksroot-format2

@RaitoBezarius have you successfully opened a luks2 volume with this change?

It has been some time but I believe I ran successfully encryption tests
with this PR in the past but it broke after some rebase so I didn't touch
it for now. I am on vacations for the next 48 hours so I will take a look
again after. Sorry for that.
Le ven. 15 déc. 2023, 16:01, Alyssa Ross @.***> a
écrit :

@RaitoBezarius https://github.com/RaitoBezarius have you successfully
opened a luks2 volume with this change?
—
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/257420#issuecomment-1858020469,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACMZRFBFMB4H7LI5B2KKSLYJRQ4DAVCNFSM6AAAAAA5HO5OR6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQNJYGAZDANBWHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Add drop option

Description
This uses the argparse library to add a -d or --drop option to the sample data injection script.
This option allows to discard all existing product objects in the database.
Related Issue
Closes #34

So we have to decide a name for that optional flag to keep the data. What about --keep?

So we have to decide a name for that optional flag to keep the data. What about --keep?

That sounds good. Also keep a shorthand -k

Fix the merge conflict and we're good to go.


Proposal: auth helpers

@vlad-ivanov-name Thanks for the write-up! I think the general idea of authentication helpers in this way is pretty clever!
This is already a little technical but I'm wondering if this is something we could implement in rattlers AuthenticatedClient. That way not only rip (for python dependencies) would benefit from this but we could also use it for conda packages. Did you think about the technical details already? WDYT?

I'm curious how we would test this feature in CI. In the tests/ we have a package database builder. But I assume we need something alike for testing this with multiple pypi indices. Did you already have some ideas on that front?

I wonder how difficult it would be to build a small, simple pip registry server (if it can even be small and simple). I'd say for stuff like that I'd write an integration test that spawns a local server (implemented with e. g. axum -- really cool framework) and add snapshot tests with something like insta

I think this would be cool, @tdejager you think this could be part of rip?


switching presentation modes with keyboard loses focus

Hi,
in dbeaver 3.8.5 in the result pane switching presentation modes between grid and text loses focus on the result pane. If you want to switch back the presentation mode using keyboard you first need to navigate to the result pane and obtain focus again.
How to reproduce:

Run any query that returns a result set
in presentation mode hit Ctrl+` to switch between grid and text
if you hit ctrl+` again you won't be switched back to the original presentation mode because the pane is not in focus anymore.

Can't reproduce (Windows 10). What is you OS?

3.8.5
If focus on grid or text panel and click Ctrl+, switch work once and focus lost after rerender panel (no focused elements). If focus on SQL editor panel, Ctrl+ work fine.
OS Ubuntu 15.10

OS Ubuntu 16.10 with Unity

I have the same issue on Ubuntu 16.04 / Unity.

Eventually I've reproduced that. This was caused by differences in controls focus change in Windows and various GTK versions.


Switch to go-re2

When running Coraza within Caddy, profiling was showing elevated regexp.* usage. After discussions on Slack, it was demonstrated that the Go-Re2 offers much lower CPU / slightly better performance with Go-Re2 compared to the standard regexp. (There are legions of discussions about Go's regexp engine being slow on the web)
Since this is a drop-in replacement, existing testing doesn't require adjustment as far as I can see. (if this is an issue I can send another PR)
Make sure that you've checked the boxes below before you submit PR:

[ ] My code includes positive and negative tests.
[ ] I have an appropriate description with correct grammar.
[ ] I have read Contribution guidelines, maintainers note and Quality standard.
[ ] My code is properly linted and passes pre-commit tests.

Thanks for your contribution :heart:

We provide a plugin to make it easy to swap in go-re2
https://github.com/corazawaf/coraza-wasilibs
go-re2 is a pretty heavyweight dependency so it's probably better to still keep it opt-in rather than only supporting it. I think for caddy we just want to provide a build tag that uses coraza-wasilibs

I don't think we should migrate right away but defintively we need a section on how to use wasilibs. Mind working that out @monkburger? see https://github.com/corazawaf/coraza-wasilibs

Maybe for regex engines, we should have build flags... I was also working on hyperscan integration

@monkburger Are you up for working on https://github.com/corazawaf/coraza/pull/1005#issuecomment-1952009328?

@monkburger Are you up for working on #1005 (comment)?

Sorry. I haven't had any free time in the last few months to look at this.


/home/kedro_docker: No such file or directory

Hello, team!
I am closely follow instructions for the docker image flow in https://kedro-azureml.readthedocs.io. I was able to create an Azure pipeline, but it failed with the error in std_log.txt: /bin/bash: line 1: cd: /home/kedro_docker: No such file or directory. This is the working directory configured in conf/base/azureml.yml, and it’s generated by kedro-azureml. I am not sure why it pointed a non-existing directory, and how to make it works.

Can you post the Dockerfile you used? It should have a step that copies your project to /home/kedro_docker


investigate openzeppelin upgradable contract

Open Zeppelin has a set of contracts geared to help create robust contracts that provide for upgreadability, and role based management.  Will leverage OpenZeppelin upgradeable proxy for project


Relay database

Adding html template and database to save commands set by clients.

Casey, I think it looks great! Thank you for developing that.
The only comment I have is about the accessibility of stored information. It seems like there's no authentication, and the information can be viewed by everyone. I suppose that's okay for all events except the DSA ones since they are not public, correct?

Thanks for the review.
I wanted it open to make it easy to test and access, but I agree there are issues with that (even for CHIME/FRB results). I'll look into a simple authentication system.


Add >= 1.67.0 to Rust version

Checklist

[ ] Used a personal fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[ ] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[ ] Ensured the license file is being packaged.

@messense - Sorry to bother, do you have any idea how to get this to use Rust 1.67.0? It seems like the rust-feedback merged support a long time ago, but it's not resolving here.

I'm not sure, maybe @pkgw knows?

I wonder if Rust needs to be added to the Hosts section of the meta.yaml - I'm trying to understand the docs here.
I don't have experience with compile steps in conda recipes but I'll see if I can build the recipe locally sometime.

Thanks to all of you for your work on ruff and on making it available on conda-forge!
I saw in the polars feedstock repo there is a file conda_build_config.yaml which adds conda-forge/label/rust_dev as a channel source.  I believe this might make rust 1.67 available so the recipe can build.

Ohh thank you, let me try that...

Huzzah, that worked!

I'm going to re-open from a fork with a new PR.


Always display the emoji with emoji presentation

Some emojis have a text ("⚠ SERVICE PROBLEM") and an emoji ("⚠ SERVICE PROBLEM") representation. Make sure to always use the emoji presentation.
https://unicode-table.com/en/FE0F/
Co-authored-by: Markus Pröpper<EMAIL_ADDRESS>

Thanks for the notice and the link. The UTF-8 value defined in line 68 to 81 is extended by the hex value EF B8 8F according to Variation Selector-16 and Encoding table. It has been tested and works. Thank you for your contribution.