Wrong md5 sum returned

When semanticdb is run on a file:
package a;
public class Main {
  abstract class A {
      abstract void hello();
  }
  abstract class B extends A{
      @Override void hello(){
          System.out.println("Hello!");
      }
  }
  class C extends B{
      @Override void hello(){
          System.out.println("Bye!");
      }
  }
}

Java semanticdb returns:
D41D8CD98F00B204E9800998ECF8427E
while running md5sum Main.java returns:
9F1F9093CB007C3D3A57BA6D7C871858
This is also the same as returned by https://github.com/scalameta/metals/blob/main/mtags/src/main/scala/scala/meta/internal/mtags/MD5.scala

Thank you for reporting! I just kickstarted a 0.7.3 release with a fix for this bug

Something weird has happened with the release, It looks like 0.7.3 was released last month:
https://repo1.maven.org/maven2/com/sourcegraph/semanticdb-javac/0.7.3/
and if I check the sources jar it has the previous version of MD5.java. Checking locally it all should work correctly with the fix, but it actually doesn't.
Maybe there was a broken release last month?

Weird, I checked the "releases" page and it didn't include 0.7.3, I pushed a new tag for 0.7.4

Weird, I checked the "releases" page and it didn't include 0.7.3, I pushed a new tag for 0.7.4

Thanks! It's super mysterious :thinking:

Och wow, it seems 0.7.3 is hardcoded:
2022-01-12 15:09:11.552Z error [SonatypeClient] [promote] Failed  - (SonatypeClient.scala:182)
2022-01-12 15:09:11.553Z error [SonatypeClient] Activity name:release, started:2022-01-12T15:09:04.510Z, stopped:2022-01-12T15:09:09.479Z  - (SonatypeClient.scala:456)
2022-01-12 15:09:11.554Z error [SonatypeClient]     Failed: RepositoryWritePolicy, failureMessage:Artifact updating: Repository ='releases:Releases' does not allow updating artifact='/com/sourcegraph/lsif-java_2.13/0.7.3/lsif-java_2.13-0.7.3.pom'  - (SonatypeClient.scala:375)
2022-01-12 15:09:11.556Z error [Sonatype] [STAGE_FAILURE] Failed to promote the repository.  - (Sonatype.scala:425)

maybe dynver is not setup?

The 0.7.4 release succeeded after I created a new empty commit.


Feature Request - Image Upload To Gallery/Insert From Gallery

It might be worthwhile to have a plugin that allows you to upload images to the server, instead of base64 encoding them directly into the editor, the later pick those images from a gallery.
This would be really useful when dealing with large images or when you have an image you want to reuse at a later point.
For this last use case, an example would be using SunEditor in a CMS and the user uploads some type of logo that they want to use on several pages. Instead of base64 encoding it into each page's content, I would upload it, then pick it from an Insert From Gallery dialog on later screens. It would then insert either the relative or absolute path of the image into the editor.
This would be a fairly significant changes since you'd need a way to upload to the server and a dialog that lets the user pick uploaded files from a gallery.

Hi~
You can still upload to the server instead of base64 with the "imageUploadUrl" option.
The file gallery is a plugin I really want to add.
I will develop file gallery after processing other issue
I appreciate your good ideas. : )


Get_last_failure does not catch errors such as POST, PATCH, which can…

… affect the retry mechanism because the default value of proxy_next_upstream, error timeout, does not contain non_idempotent
The following is the explanation of proxy_next_upstream.
proxy_next_upstream
Specifies in which cases a request should be passed to the next server:
Default:
proxy_next_upstream error timeout;
non_idempotent
normally, requests with a non-idempotent method (POST, LOCK, PATCH) are not passed to the next server if a request has been sent to an upstream server (1.9.13); enabling this option explicitly allows retrying such requests;
NOTE: Please read the CONTRIBUTING.md guidelines before submitting your patch,
and ensure you followed them all:
https://github.com/Kong/kong/blob/master/CONTRIBUTING.md#contributing
Summary
SUMMARY_GOES_HERE
Full changelog

[Implement ...]
[Add related tests]
...

Issues resolved
Fix #XXX

@kingljl Thank you for the patch! Catching failures on unsafe HTTP methods requests should definitely happen. However, I don't think we wish to enforce the best practice provided by Nginx (rightfully so) which is to not retry such requests... Overall, this PR would need some regression tests proving this behaviour.
Ping @hishamhm @Tieske - this feels like an important discussion to have.

iirc correctly the failures are still caught in the logging phase.
This change is dangerous though, since we do not want non-idempotent requests to be retried by default. When the retries were implemented it was a deliberate choice to stick to the existing nginx directive (from a MVP feature perspective).
The proper way to do this is to recreate the nginx retry logic in Kong. Copy the configuration option into the service entity, such that they are configurable on a per service basis (effectively have nginx retry every request, and have Kong decide when to stop).

@hishamhm I was suggesting a test that asserts the upstream server (Target )is marked as unhealthy when a non-idempotent request fails (i.e. not any logging plugin, but specifically the healthcheck core component). If anything mostly to ensure we do not experience any regression in this scenario and demonstrate to users such as @kingljl that such failures are properly caught by the balancer/healthchecks.
It seems like this is already the case anyway (I originally misinterpreted the patch as implementing the behavior described in my above paragraph). And retrying non-idempotent requests is a no-no at this time (unanimously). Let's close this then!
@kingljl Thank you for the suggestion; I believe the thread to be insightful enough as to why we unfortunately cannot incorporate it.


The grammar seems off here

I know it sounds off, but the previous version is more grammatically correct. English is weird :)

Are you sure? Cause at least the "of" seems off

Yep, I'm sure. English is strange. https://www.englishbaby.com/vocab/word/11619/work-off-of


About PlayerPortalEvent（MineCraft1.14.1）

[20:42:51 ERROR]: Could not pass event PlayerPortalEvent to Multiverse-Core v3.0.0-SNAPSHOT-b761
java.lang.NoSuchMethodError: org.bukkit.event.player.PlayerPortalEvent.getPortalTravelAgent()Lorg/bukkit/TravelAgent;
at com.onarandombox.MultiverseCore.listeners.MVPlayerListener.playerPortal(MVPlayerListener.java:307) ~[?:?]
at com.destroystokyo.paper.event.executor.asm.generated.GeneratedEventExecutor276.execute(Unknown Source) ~[?:?]
at org.bukkit.plugin.EventExecutor.lambda$create$1(EventExecutor.java:69) ~[patched_1.14.1.jar:git-Paper-22]
at co.aikar.timings.TimedEventExecutor.execute(TimedEventExecutor.java:80) ~[patched_1.14.1.jar:git-Paper-22]
at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:70) ~[patched_1.14.1.jar:git-Paper-22]
at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:534) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.EntityPlayer.a(EntityPlayer.java:843) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.Entity.doPortalTick(Entity.java:2160) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.Entity.entityBaseTick(Entity.java:393) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.EntityLiving.entityBaseTick(EntityLiving.java:236) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.Entity.tick(Entity.java:365) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.EntityLiving.tick(EntityLiving.java:2273) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.EntityHuman.tick(EntityHuman.java:150) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.EntityPlayer.playerTick(EntityPlayer.java:418) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.PlayerConnection.tick(PlayerConnection.java:146) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.NetworkManager.a(NetworkManager.java:259) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.ServerConnection.c(ServerConnection.java:129) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.MinecraftServer.b(MinecraftServer.java:1198) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.DedicatedServer.b(DedicatedServer.java:418) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.MinecraftServer.a(MinecraftServer.java:1057) ~[patched_1.14.1.jar:git-Paper-22]
at net.minecraft.server.v1_14_R1.MinecraftServer.run(MinecraftServer.java:902) ~[patched_1.14.1.jar:git-Paper-22]
at java.lang.Thread.run(Unknown Source) [?:1.8.0_211]

Can confirm this bug. Very annoying, because it breaks uSkyblock as well

Seem to be appearing with both 2.5.0 and 3.0.0-b760 (alpha) versions.

This is due to the removal of the TravelAgent API from the Spigot project (see https://www.spigotmc.org/threads/bukkit-craftbukkit-spigot-bungeecord-1-14-1-development-builds.369724/) - and also completely breaks MV-NP as it heavily relied on it for generating portals.

Hello, Multiverse is aware of these errors and will be working on a 1.14 compatibility update soon.
A message from dumptruckman:
I just want to let you know that I understand there are some issues with Multiverse running on 1.14. The reason behind this is the removal of something called the TravelAgent. Because this was removed, some stuff broke related to nether and end portals. In particular, Multiverse-NetherPortals is not working at all.
You should all know that 1.14, 1.14.1, and 1.14.2 have been full of problems in general. What you may not know is that TravelAgent is going to come back. When it does, most of the things that 1.14 broke in MV will no longer be broken. Since I have so little time to devote to this project, it seems to be in my best interest to just wait for that to happen rather than make a bunch of changes I will need to change back later. I know you're all anxious to get your servers working perfectly for 1.14 but from what I hear, 1.14 is just far from perfect itself right now. Please be patient while we wait for better days.

This appears to be fixed in the latest Multiverse dev build (4.0.0) - https://ci.onarandombox.com/job/Multiverse-Core/


SQLite extension needed for UWP

We should probably mention this in the handson readme:
http://sqlite.org/download.html
http://sqlite.org/2016/sqlite-uwp-3140200.vsix

Yup, it is in the readme to add it via the Extensions and Updates.

Before this weekend, I will be updating to 3.0, which should solve this issue in the future ;)

I am still seeing this issue in latest code.  I also did not see a mention of installing vis Extension and Updates in the latest Readme.

It can simply be removed. I am pretty sure I removed it... hmmmm

Now removed removed :) thanks!


Add dimensions option for embedding

Description
This pull request introduces an dimensions option into the GraphRAG's embedding, allowing it to take a user-defined size of dimensions which won't affect current usage of default embedding dimensions.
Related Issues
None.
Proposed Changes
Modified the GraphRAG embedding code to accept a dimensions parameter, enabling users to customize its size.
Added relevant error checks to ensure the input dimensions value is within reasonable limits.
Checklist

[√ ] I have tested these changes locally.
[ √] I have reviewed the code changes.
[ ] I have updated the documentation (if necessary).
[ ] I have added appropriate unit tests (if applicable).

Additional Notes
According to https://openai.com/index/new-embedding-models-and-api-updates/, the text-embedding-3-large has a default dimensions size of 3072, which is not suitable for everyone.
Noticing excessive embedding dimensions can lead to significant computational and storage overhead without yielding proportional performance improvements.
How to use
add dimensions: <your dimensions> in setting.yaml after initialize the project.
embeddings:
  # parallelization: override the global parallelization settings for embeddings
  async_mode: threaded # or asyncio
  llm:
    api_key: ${EMBEDDING_KEY}
    type: azure_openai_embedding # or azure_openai_embedding
    model: text-embedding-3-large
    api_base: ${EMBEDDING_BASE}
    api_version: "2024-02-01"
    # organization: <organization_id>
    deployment_name: text-embedding-3-large
    dimensions: 1024

add dimensions: <your dimensions> in OpenAIEmbedding(graphrag_local_search.ipynb)

Moreover, what bothers me is that after setting the dimensions once in setting.yaml (or not setting it at all, thus defaulting to dimensions=None, which would not be invoked in OpenAI's client.embeddings.create), such dimensions (either None or a certain number) will persist throughout the same project even if the setting.yaml changed. So I have to make a new dir , run python -m graphrag.index --init --root ./ragtest and set up setting.yaml every time I want to set up a new project.

Hi!
Is this a revision of #1020 ?

Hi!
Is this a revision of #1020 ?

Yes! Sorry I forgot to close it #1020 .

Hi @AlonsoGuevara , I'm following the progress of this PR, and the dimensions parameter for embeddings is a useful enhancement. I would like to have this feature in GraphRAG . Please let me know if there's anything I can do to assist in moving this forward.


Add unit tests for Zend\Expressive\Router\RouteResult

Hello. If you don't mind, I can do this.

@nikolaykovenko don't mind at all. Go for it!


Type narrowing error while function return type is not marked as NoReturn

Environment data

Language Server version: 2023.8.41 (23 August 2023) PreRelease
OS and version: win11
Python version (& distribution if applicable, e.g. Anaconda): python3.9

Code Snippet
from typing import NoReturn, Optional

def raise_exc():
    raise Exception()

def get() -> Optional[int]:
    ...

def main():
    x = get()  # int | None
    if x is None:
        raise_exc()
    x.as_integer_ratio()  # pylance: "as_integer_ratio" is not a known member of "None"

main()

raise_exc is inferred as NoReturn, so according to type narrowing x in x.as_integer_ratio() should be inferred as int. But pylance consider it to be int | None.
But if I add return type obviously, pylance will provide the correct inference:
from typing import NoReturn, Optional

def raise_exc() -> NoReturn:  # <---------------
    raise Exception()

def get() -> Optional[int]:
    ...

def main():
    x = get()  # int | None
    if x is None:
        raise_exc()
    x.as_integer_ratio()  # pylance work right

main()

This is expected behavior. You need to include an explicit NoReturn return type annotation if you want pyright to assume a NoReturn behavior for purposes of code flow analysis. Return type inference will not be used in this case.

thanks for your reply!


Add custom SwiftLint rules

This PR adds some custom SwiftLint rules including checking for the SwifterSwift:  prefix in doc strings

          1 Warning

:warning:
The source files have been modified. Please consider adding a CHANGELOG entry if necessary.

          4 Messages

:book:
Thank you for submitting a pull request to SwifterSwift. The team will review your submission as soon as possible.

:book:
iOS: Executed 589 tests, with 0 failures (0 unexpected) in 12.947 (15.449) seconds

:book:
tvOS: Executed 564 tests, with 0 failures (0 unexpected) in 6.684 (8.755) seconds

:book:
macOS: Executed 422 tests, with 0 failures (0 unexpected) in 1.076 (1.436) seconds

  Generated by :no_entry_sign: Danger

Cool stuff @omaralbeik 💯 🎉

@guykogus I see this PR will be useful for PRs like #727 😜

@omaralbeik @guykogus Any still discussion open in this one? Or good to go?


Just an experiment

Nothing to see here ....
Thank you for helping make the Radius documentation better!
Please follow this checklist before submitting:

[ ] Read the contribution guide
[ ] Commands include options for Linux, MacOS, and Windows within codetabs
[ ] New file and folder names are globally unique
[ ] Page references use shortcodes instead of markdown or URL links
[ ] Images use HTML style and have alternative text
[ ] Places where multiple code/command options are given have codetabs

In addition, please fill out the following to help reviewers understand this pull request:
Description

Auto-generated description

🤖[deprecated] Generated by Copilot at be0bc19
Summary
Walkthrough
Issue reference

@rynowak still experimenting with this PR?

Done with this. I backed it up on my fork in case we ever need it.


Commutation Checker with PauliGate

Environment

Qiskit version:  1.0, 1.2 and 1.3
Python version:  3.12.7
Operating system: Linux

What is happening?
The commutation checker always fails to commute a PauliGate with any other gate. I get this error message.
return self.cc.commute(op1, qargs1, cargs1, op2, qargs2, cargs2, max_num_qubits)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
qiskit.exceptions.QiskitError: 'Unable to hash a non-float instruction parameter.'

I think it is because the parameter in a PauliGate is the Pauli operator that it implements rather than a Parameter or a float. I realized that CommutatorChecker did not have a unittest for this particular case, and also I have tried it for different python versions 1.0, 1.2 and 1.3. 1.0 and 1.2 work fine but 1.3 does not.
2 things have changed.

The way that parameters are hashed has been ported to rust (the parameter in PauliGate is a string so I don't see why we can't hash it).
Before if one of the gates was parameterized commute would return False. Now it does some more invoved logic.

How can we reproduce the issue?
from qiskit.circuit.commutation_library import SessionCommutationChecker as scc
from qiskit.circuit.library.generalized_gates.pauli import PauliGate
from qiskit.circuit.library.standard_gates.rx import RXGate
from qiskit.circuit.library.standard_gates.x import XGate
from qiskit.circuit.parameter import Parameter

pauli_gate = PauliGate("XX")
# pauli_gate = XGate()
rx_gate_theta = RXGate(Parameter("Theta"))
print(scc.commute(pauli_gate, [0, 1], [], rx_gate_theta, [0], []))
print(scc.commute(rx_gate_theta, [0], [], pauli_gate, [0, 1], []))

What should happen?
For versions up to 1.2 we get False (which is not the correct answer). And for version 1.3 we get the error message.
Any suggestions?
I think the best option would be to fix the hashing. If there is a deeper reason why that is not possible then we need to change the logic of the function.

Thanks for the reports! Indeed for the PauliEvolutionGate we'd need to do a custom caching, since the Paulis to evolve are not stored in the params. However the more sensible solution is likely just to not cache them (we already have some exceptions for this, e.g. for LinearFunction).
For the PauliGate the issue seems to be that the Python version of the commutation checker supported strings as cache, but the Rust version now doesn't anymore. If the performance cost is acceptable we could also just skip the cache here. Otherwise  we'd have to support hash on strings to cache the params here.

@aeddins-ibm: you're actually pointing at something worse -- the commutation checker will try caching a gate it does not know and only use what's inside Gate.params as key. So any gate storing information impacting the definition outside of Gate.params can lead to a wrong result.


feat: add battlenet

Basically copied the star citizen config. Not sure about the GL settings, I think its for nvidia. I cant really test it as I am using AMD. I have been using this setup for a couple of days now and it works flawlessly.

just saw that my commit doesn`t adhere to the common style. Should I amend it?

you can reword in git rebase interactive

you can reword in git rebase interactive

yea thats basically the same. Will do so


Size of a resized (down) image is higher than original

Hello,
When I resize a PNG image down, the file size goes up considerably. Am I missing something in the code below? (Using image v0.3.11)
// main.rs
extern crate image;

use std::fs::File;
use std::path::Path;

use image::{
    GenericImage,
    imageops,
};

fn main() {
    let img             = image::open(&Path::new("test.png")).unwrap();
    let (width, height) = img.dimensions();
    let nwidth          = width / 2;
    let ratio           = nwidth as f64 / width as f64;
    let nheight         = (height as f64 * ratio).round() as u32;
    let resized_img     = img.resize(nwidth, nheight, imageops::Nearest);
    let ref mut fout    = File::create(&Path::new("test-resized.png")).unwrap();
    let _               = resized_img.save(fout, image::PNG).unwrap();
}

I am using this image https://upload.wikimedia.org/wikipedia/commons/4/47/PNG_transparency_demonstration_1.png which goes from 218 KB to 480 KB after resize.
I can't wrap my head around this.
Thanks. :-)

The image is currently saved uncompressed. This is fixed in master. I should release a new version soon.

Thanks, you guys are the best. :-)


CRF layers raise InvalidArgumentError in TPU

I tried training a CRF model in TPUStrategy, but it raised InvalidArgumentError. detail please see: https://colab.research.google.com/drive/1cRm0dd12TIPQbsl9pmI1KdiFtubB0ZIZ?usp=sharing

Thanks, we are looking for a CRF codeowner. See https://github.com/tensorflow/addons/issues/2476#issuecomment-874261227

Hi @ziliwang, for keep you updated. I am working on this issue.

Hi @ziliwang , after investigation, I am pretty sure it is a bug of Keras. If you change your code from:
train_iterator = iter(train_dataset)
train_step(train_iterator)
  # print(round(float(training_loss.result()), 4))
  # training_loss.reset_states()
print(model.weights[0].numpy())

add one line of code:
train_iterator = iter(train_dataset)
train_step(train_iterator)
  # print(round(float(training_loss.result()), 4))
  # training_loss.reset_states()
print(model.weights[0])   # ATTENTION: comment me will cause a bug in next line
print(model.weights[0].numpy())

It will fix the error. it is a weird behavior. Maybe is a bug of functional Keras API. You can double check by running code at https://colab.research.google.com/drive/1ryCgLJxPbIcTe6xgN4EH6hDDLLSrpHQW?usp=sharing
And I have found that this behavior only exits on functional Keras API (not on Sequential API).  I have create a colab with a new model written in functional API and Sequential API at https://colab.research.google.com/drive/1GyBdh-fRV--BSOin4ldf48YitkvbyE7f?usp=sharing . You can double check it.

/cc @qlzh727 What do you think?

@yuefengzhou from distribution strategy team.
From https://colab.sandbox.google.com/drive/1ryCgLJxPbIcTe6xgN4EH6hDDLLSrpHQW?usp=sharing#scrollTo=tpLYkZyVIoV6, the output of model.weights[0] is a TPUDistributedVariable, which is intended, but I am not sure why the chain_kernel:0 has numpy unavailable. The rest of the replica has the same value. Maybe it is a variable read issue when get_value is called outside of the strategy context.

@yuefengz

@howl-anderson Thanks for the replies. I tried to replace the CRF layer with a Keras dense layer, and it has shown everything is ok. I guess the CRF layer is in-compatibility with functional API when in the TPU strategy. I'm a newbie in Keras and TPU, and my target is to use the CRF in TPU strategy, the Sequential API really solved my issue. Thanks again for your help.

Hi @ziliwang, it's great to see that my code can help you. Since your issue is solved by using sequential API. So, could you close this issue for me? And I will keep trying to find the root cause why CRF layer failed with the TPU strategy. I will keep you updated  in this thread.

@howl-anderson  I meet the same problem when using crf_log_likelihood in TPU. Can CRF be used in TPU now?  Thank you!


Documentation improvements and code cleanups for graph package

Expand the godoc documentation for the graph package.
Centralize DefaultTag in the graphs/tag package instead of defining it
twice.
Remove some unnecessary "config" structs that are only used to pass
a few parameters to a function.
Simplify the GetParentsSize function - there's no reason for it to take
an accumulator argument.
Unexport some functions that aren't needed outside the package.

That's super cool thanks :+1:

Windows CI failure looks unrelated.

LGTM

Updated commit to remove ImageExportConfig, another struct that was just used for passing two parameters to a single function.

Thanks! Re-LGTM

LGTM


Calling a function without arguments passes typecheck in case of variadic argument list

I was just about to submit a definition to flow-typed when I encountered this bug:
function emit(event: string, ...params: any[]) {}
emit('something');
// $ExpectError
emit(); // this line passes type check !!!

function emit2(event: string) {}
emit2('something');
// $ExpectError
emit2(); // Error: too few parameters

Flow sandbox
Seems like the normal parameters aren't checked in case of a variadic parameter pack.

cc @avikchaudhuri seems to be a bug in multiflow

Sorry, meant to cc @gabelevi

this now correctly errors


Refactor CSV import code to be more efficient

4 parallel tasks that we can do now:

[ ] (salomone) Make JSON data: We will store our list of expected fields and their data types into a file called meta.json. Use Pandas to take a new .csv file, guess the data types and produce the meta.json. Use the make_draft_json.py file as a starting point.

[ ] (unclaimed) Figure out how to read a CSV into memory (so that we can edit values such as messy data) and then write it to SQL efficiently. Use demo_load_to_sql_without_pandas.py as a starting point.

[ ] (unclaimed) Everything else for our load_data.py file, which handles downloading files if needed, comparing manifest.csv to the manifest table in SQL to decide whether to load a table or not, handling errors. Temporarily just use dataframe = pandas.read_csv and dataframe.to_sql() in the csv_to_sql() function until #2 is ready. Use my list of functions and the rough outline in the main() function as a guide, but there are probably additional things I didn't think of.

[ ] (Neal) Get data upload tools to S3 configured.

Stuff to do after:

[ ] run make_draft_json.py on all our data
[ ] set up data cleaning phase in between read and write (see note in the csv_to_sql() function)

To get working:

Pull the branch overhaul-csv-loading into your repo
Make a new branch off of that branch for your portion
When you're ready to share your work, make a pull request on Github into the overhaul-csv-loading branch (not the dev branch). We'll consolidate all our work there and make sure it's working before merging into dev.
(let me know if you need help with any of this!)

What you'll see in the /scripts folder:
/__root__

database_management.py: contains tools to connect to our database. Moved to root because this can be also be used later in other places (e.g. analysis scripts). I created this for housing_risk but I have not yet tested this in our project, so it might need minor changes.
-secrets.example.json: check out the addition of the local_database vs. remote_database, and make this edit to your secrets.json copy (or ask me for a copy if you don't have one yet).

/data

I moved the small_data, big_data, and output_data folders into here to clean up our root

/ingestion:

make_draft_json.py: for item #1
demo_load_to....: for item #2
load_data.py: for item #3
manifest.csv: I edited the columns available here to match what was used in the housing_risk example code. I deleted all the rows except for 3 - one small table that is immediately available in the repo, plus two large tables that are both a) able to be downloaded from S3 (to test download code) and b) need to go to the same table in SQL (to test append to sql table functionality)
meta.json: my proposed structure for the JSON file that stores field names and data types.
example_....: these are the old load_data.py scripts and files, which you can look at for reference on how things are previously done. We'll delete these once we get everything working.

If you're feeling ambitious:
Unit tests!!!
Since this new approach should be production-worthy, I want to make sure we get at least a decent amount of unit tests written. If you're into test driven development, write these tests as you go, otherwise I'll want to get them written before we merge to dev. If you're not familiar with unit tests, don't worry about it yet.
Resources:

High performance with named tuples and custom classes, but only discusses the read from csv part of the equation. Slightly clunky for data type parsing. Typically we won't have larger-than-memory data sets so the SQL inserts are our bigger problem. District Data Labs CSV article
Odo, another library that claims to be good at parsing dates.
BULK INSERT command in SQL. Use this with the load into Pandas, fix data problems (cleaning), and then could process comma delimited into pipe delimited flat file to deal with some data format issues and load from there? StackOverflow Discussion. Pay attention to the dtype parameter in the pandas.read_csv method to pass it manual overrides of data types instead of inferring when reading the file.

Neal,
In make_draft_json.py, you note:

#use command line arguments to pass (relative) filepath and table_name.
#we should use positional arguments in the command line

Just to confirm, the code will only ingest and convert the files that are given as command line arguments, correct?
If so, is this how you picture the command to run the program?
python make_draft_json.py ../example/relative/filepath example_table
Should the program be able to parse multiple arguments, ie.
python make_draft_json.py ../example/relative/filepath1 example_table1, ../example/relative/filepath2 example_table2
argparse seems like it might be good for this. Alternatively, I wonder if we could use fileinput to read the information from the manifest file. This might be cleaner than specifying the data files on the command line (but could also maybe get confusing)? What do you think?

@salomoneb - I think that it is OK to use just one file path for the command line arguments. I think normally we will be processing files one-by-one (since we have to manually review the output anyways...).
If we do have a need to run multiple files frequently, we can import this code into another file and have it call the make_draft_json() function directly - the `if 'name' == 'main' code is only run when this file itself is run from the command line.
I don't think we should add the files to the existing manifest.csv until they have been "validated", i.e. the file has been added to the meta.json (by running the make_draft_json routine).
Argparse looks like it will be handy if/when we start getting complex. For now, I think we can just run with:
sys.argv[1] - returns the first item after the make_draft_json.py name
sys.argv[2] - returns the second item after the make_draft_json.py name

Neal,
https://gist.github.com/salomoneb/53f8c6fb851346f7dd812fa518808859
Here's a test/proof-of-concept version of this script. There are still two things left to do with this:

Error handling and cleaning
Expanding the metadata for each field

Regarding the second point, can you explain the difference between field_name_matches_sql_name, source_name, and sql_name? Also, I assume display_name and display_text would be manually added?

Cool.
Your questions:
"source_name" - whatever the field is called in the original CSV file. If the first row of the CSV is a header row, this is the string that matches; if there is no header, it is an integer.
sql_name = if the name in the original CSV is not intuitive, we can optionally call it something else in our database (e.g. ACS rent is 'hd01_vd01' instead of 'median_rent'). The make_json script should generate a default by taking source_name and applying functions to make it play nice with SQL, e.g. replace space with underscore, force to lower case, etc.
display_name - yes, added manually - but your script should pre-fill with sql_name / source_name.
display_text - yes, add manually
So basically your script should make source_name, sql_name, and display_name all equal to whatever the column is named in the CSV - having 3 versions is to give us flexibility.

@blw9u2012 here are the 5 tables for the Preservation Catalog, which are a good starting point for testing real data: https://s3.amazonaws.com/nhumphrey-misc/PresCat_Export_20160401.zip

Photos of the workflow that we discussed at our meeting last night.


New updated react component docs

Nice job @akhileshverma92  , Merged the changes to the main file , try to add more code snippets and the examples in the future contributions ✅🚀


Unit conversions

This PR allows to specify the conversion of unit of measurement. Currently only time units are supported. If a tuple in a form of {from, to} is passed to :unit option, the measurement function is wrapped and the measurement is converted to the desired unit.
The unit conversion relies on the fact that the measurement is a number, but since it's not checked anywhere, we simply crash with a BadArithmetic when performing the conversion.
I'm not sure how to handle converting from smaller to bigger units when it comes to rounding. Currently, e.g. when converting from nanoseconds to milliseconds, the result is a float - however, I think that it would be most convenient if it is an integer. The question is, should we always round down (e.g. by using div/2 instead of //2), or using round/2which uses half-up rounding strategy.
Closes #27
/cc @bryannaegele @binaryseed

Codecov Report

Merging #30 into master will decrease coverage by 0.26%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #30      +/-   ##
==========================================
- Coverage    98.3%   98.03%   -0.27%
==========================================
  Files           1        1
  Lines          59       51       -8
==========================================
- Hits           58       50       -8
  Misses          1        1

Flag
Coverage Δ

#1_5_otp18
98.03% <100%> (-0.27%)
:arrow_down:

#1_5_otp20
98.03% <100%> (-0.27%)
:arrow_down:

#1_8_otp19
98.03% <100%> (-0.27%)
:arrow_down:

#1_8_otp21
98.03% <100%> (-0.27%)
:arrow_down:

Impacted Files
Coverage Δ

lib/telemetry_metrics.ex
98.03% <100%> (-0.27%)
:arrow_down:

Continue to review full report at Codecov.

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

@arkgil I would send them as floats... unless there is a backend that doesn't support floats? although that would be very weird.

@josevalim right, some of the metric system support fractions of time units - let's leave it as it is and it'll be up to the reporter to decide. I'll add a bit about it to the reporters guide.

I'm so excited for this PR!
Prometheus requires floats but OpenCensus supports both. It seems fine to require the reporter to convert to float if that's all it supports.


[SE-0091][gardening][stdlib/public] Move operators into types

Looks like operators as static functions are more popular in the codebase.
Ignoring whitespaces: https://github.com/apple/swift/pull/15151/files?w=1

@swift-ci smoke test

Moving operators into types can have overload resolution implications. Specifically, a hack makes a homogeneous infix operator definition inside the type always "win." Therefore, source compatibility and compilation time could be affected.

Hmm if this is not acceptable, why SE-0091 is introduced? Should we have per-type decision on this topic?

@swift-ci please test source compatibility

@xwu Is #13817 related to what you said?

@ikesyo Your refactoring is likely to be superior compared to the current situation, but my meaning is that there are functional changes formally possible as a consequence.
#13817 is where @moiseev took advantage of the hack to favor homogeneous comparison over heterogeneous comparison in concrete types.
As long as there aren't lots of overloads (as there are for integers), I would guess that your refactoring should have, in practice, no functional change.

@xwu is correct that source-compatibility regressions are possible here. However, the source-compatibility suite ran cleanly, and this is definitely the direction we want to go (absent source-compatibility issues), so I'm going to go ahead and merge. Thanks @ikesyo

Thanks @xwu and @DougGregor!


Using Abstract class doesn't generate setter for list relations

I'm using the interface entity now and was trying out it out as abstract class entity but when I changed it. The generated code didn't have a setter for @OnToMany and @ManyToMany attributes with a List/Set type I also tried it with Result/MutableResult which also doesn't generate the setter. The getter are generated correctly though.
Also @OneToOne generates correctly both a setter and getter when using an Abstract class entity

This is intentional. Changes to collections must be tracked internally by requery, so they are created automatically, and you simply add/remove items from the collection. Allowing the collection to be replaced is error prone and usually not what users intend. Instead use the standard collection api to modify it (add/remove/clear/addAll etc)

Okay that I can understand. @npurushe does that also mean that if it can't find any relationships (empty table for instance) that it will have an empty list in which you can add new entities? Also why does the interface Entity generate the setter then shouldn't it also only generate a getter?

Yes it will have a default collection in which you can add entities. I agree the interface should probably not generate a setter unless it is required for some reason.


remove treetaggers

replace the dependency to the treetagger to spacy for languages other than english

Issue Fixed in Pull Request No. 6


Rancher UI not working after upgrade to 2.2.0

What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):
Air gapped cluster with rancher v2.1.0 or 2.1.7
Upgrade to 2.2.0
Result:
[ERROR] failed to serve UI: Get https://test/ui/latest2/index.html: dail tcp: lookuptest on : server misbehaving
Actual Result:
Working
Rancher UI on v2.2.0
Other details that may be helpful:
Upgrade from v2.1.0 to v2.2.0 gives the same result as upgrade from v2.1.7.
When starting a new container with rancher v2.2.0 the UI is working.
Environment information

Rancher version : v2.2.0
Installation option: Air Gapped single install

Cluster information

Cluster type: Air Gapped Custom

Machine type: Metal 96 Cores and 756GB

Docker version (use docker version):

Client:
 Version:           17.03.2-ce
 API version:       1.27
 Go version:        go1.7.5
 Git commit:        f5ec1e2
 Built:             Tue Jun 27 03:35:14 2017
 OS/Arch:           linux/amd64

Server:
 Version:           17.03.2-ce
 API version:       1.27 (minium version 1.12)
 Go version:        go1.7.5
 Git commit:        f5ec1e2
 Built:             Tue Jun 27 03:35:14 2017
 OS/Arch:           linux/amd64
 Experimental:      False

container.log

Please provide exact steps/commands used, and can you also provide the history from this setup (what versions of Rancher are used)? Is there a proxy in play here?
This does not reproduce from scratch starting on v2.1.7 and upgrading to v2.2.0 in an airgapped environment.

I guess you updated the ui-setting. You can change it to local via  API /v3/settings/ui-index

It should be the same with https://github.com/rancher/rancher/issues/19327

Close in favor of https://github.com/rancher/rancher/issues/19327


[PG]: Support SQL Browser - PGAdmin4

From @TamalSaha on March 7, 2017 5:26
Copied from original issue: k8sdb/postgres#11

This issue was moved to kubedb/project#68


[zh] update dns-pod-server.md

Signed-off-by: song<EMAIL_ADDRESS>

This PR seems to be conflicted with #33993, maybe you can check if this file have other place need to update.

#33993

This PR seems to be conflicted with #33993, maybe you can check if this file have other place need to update.

[zh]Update content/zh/docs/concepts/services-networking/dns-pod-service.md #33993

@Sea-n Thanks for pointing it out 😄 👍 .  already Reformatted the document format.

/approve


torch.utils.ffi is deprecated

Trying to run ./make.sh calls on python build.py in line 14, which has from torch.utils.ffi import create_extension in line 3. Which causes the following error:

ImportError: torch.utils.ffi is deprecated. Please use cpp extensions instead.

Could you update your code to use cpp extensions instead?

@adityaarun1

@StrangeTcy You are required to run python setup.py build develop inside the lib directory as mentioned here. ./make.sh is required if you wish to compile with PyTorch 0.4.0. In that case, please ensure that you checkout from the correct branch.

@ruotianluo Do you think a code clean-up for the 1.0 branch will be helpful? I have earlier simply added the required changes, and did not remove obsolete code which was needed for 0.4.0. I will be happy to remove these if you feel so.

0.4 version is already archived in a separate branch. Feel free to submit a pull request.

Ok, seems to be my bad. I'll try to follow your advice and hopefully close the issue.

damn


Update to Chromium 79.0.3945.79

Chromium 79 was released to the stable branch today.
It might be best to do a squash merge on this.

does this release contain the changes related to ad blockers?

If you are talking about Google's Manifest V3, then I don't think so. According to Google's Migrating to Manifest V3 document, it's mostly in preview, so Chrome 80 or 81 might have those changes (both of which are in the dev/canary branches).

@tangalbert919 have you successfully compiled Chromium with this patchset?

Yes, I have.

On second thought, I'll take care of this myself.

hey @Eloston , could you create a tag for this new version? thanks


Create a contact info block

Add links to social networks (LinkedIn, Facebook, Instagram), phone number, email, Telegram username, etc.

Random comment


[otbn] Memory Access Alignment

Currently I can't see anything in the OTBN spec that specifies whether memory access should be aligned or not.
I would propose that all accesses must be 4-byte aligned (both narrow and wide accesses). Any unaligned access would cause OTBN to halt with an error.

Sounds reasonable to me. Should this also apply to bus accesses?

Yes, only aligned accesses. That should be added to the docs.
Rupert: What kind of bus accesses do you mean?

Actually, wide DMEM accesses also should be 256b-aligned.

Yes, I think both should be the case, alignment to XLEN

@imphil: I mean, can the TL-UL bus generate a read for address 0x123 within, say, our DMEM?

can the TL-UL bus generate a read for address 0x123 within, say, our DMEM?

For reads: sub-word accesses not crossing a word boundary are supported by the bus adapter.
For writes: only aligned word accesses.
For all "inside OTBN" accesses: only aligned word accesses; for DMEM, a word can be 32b when accessed from the base ISA side, or a 256b word when accessed fro the BN side.

From a hardware perspective we can happily support reading 32-bit aligned 256 bit words on the wide side.
Though a related question is do we want to increase the data bus width between OTBN and DMem to allow faster reads on the wide side? When we were doing the performance numbers how many cycles did we assume for a load and store?

From a hardware perspective we can happily support reading 32-bit aligned 256 bit words on the wide side.

Yes, but there's no BN instruction using that functionality.

Though a related question is do we want to increase the data bus width between OTBN and DMem to allow faster reads on the wide side?

The dmem bus is already 256b wide. The performance numbers were assuming a single cycle for loads/stores.

Ah my mistake I had thought it was currently a 32-bit data bus, hence easily supported reads of 32-bit aligned 256 bit words.
In that case the original suggestion of 32-bit aligned narrow and 256-bit aligned wide accesses only is the way to go. I will add this to the docs.

Ah on a closer look there's already mention of alignment on the LID/SID instructions, though the psuedo code for the instructions looks a bit odd
memaddr = GPR[rs1] + offset / WLEN / 8

The offset / WLEN / 8 is turning the offset into an address for  a WLEN width memory (i.e. the native addresses used by the DMem) but GPR[rs1] is indicated as a byte address. I think we want something like:
memaddr = (GPS[rs1] + offset) / (WLEN / 8)

yes, it's a mistake I've made consistently in various places :-)

Ok I'll have a look through and correct and ensure alignment requirements as suitably obvious.


Cost management pages sometimes display wrong localized strings

Describe the bug
During testing I noticed that sometimes the pages don't show correct strings, after a brief discussion with @boaz0 it turned out that this could be a problem with react-i18n localizing the texts.
To Reproduce
Steps to reproduce the behavior:

This behavior is inconsistent and I haven't found a way to reproduce it on purpose
Happens on any of the Cost Management pages, see screenshot for example

Expected behavior
Correct strings are displayed
Screenshots

Desktop (please complete the following information):

OS: Fedora
Browser Firefox
Version 70

Additional context
Found on both CI/QA

I have seen this occasionally, but not reproducible.

I am going to look into it. It could be a problem with react-i18n or webpack.
Anyway, I will take a look and find what can be done.

ping @dchorvat1 is this still happening?

I am closing this because it seems to be fixed by itself.
@dchorvat1 if you think it is not fixed please re-open.
Thanks.


Move to peer dependency

https://github.com/AlaskaAirlines/auro-avatar/blob/fe51117c299bb8f14b3c29dd3acc25b77a0897c4/src/auro-avatar.js#L8
https://github.com/AlaskaAirlines/auro-avatar/blob/fe51117c299bb8f14b3c29dd3acc25b77a0897c4/package.json#L21
Look at moving this nested dependency to be a peer dependency to remove possible conflict.

Was looking at the wrong branch. This issue is already resolved.


Links not working

Attach (recommended) or Link to PDF file here:
example_file_with_links_not_working.pdf
Configuration:

Web browser and its version: Firefox 62.0b5, dev edition
Operating system and its version: macOS High Sierra 10.13.5 (17F77)
PDF.js version: PDF.js: 2.0.625 (the one that comes with Firefox)
Is a browser extension: I guess (?

Steps to reproduce the problem:

Open the attached pdf
Click on one of the links

What is the expected behavior? (add screenshot)
The link to work
What went wrong? (add screenshot)
The link does nothing

The pdf was exported using Word from a docx file. The links do work in Adobe Acrobat or Preview in macOS. Please tell me if you need more info.
Thanks!
F

Oh I see, thanks @Snuffleupagus
Closing as it's a duplicate

@Snuffleupagus do you know of any way I can convert a docx file to pdf and maintain working links?


Resolve type issues in redis cache

Why are these changes needed?

Related issue number

Checks

[ ] I've included any doc changes needed for https://microsoft.github.io/autogen/. See https://microsoft.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[ ] I've made sure all auto checks have passed.

Codecov Report
Attention: Patch coverage is 15.38462% with 11 lines in your changes are missing coverage. Please review.

Project coverage is 25.39%. Comparing base (09a4918) to head (c2c944b).

Files
Patch %
Lines

autogen/cache/redis_cache.py
15.38%
11 Missing :warning:

Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1872       +/-   ##
===========================================
- Coverage   36.02%   25.39%   -10.63%
===========================================
  Files          63       63
  Lines        6621     6627        +6
  Branches     1462     1588      +126
===========================================
- Hits         2385     1683      -702
- Misses       4041     4731      +690
- Partials      195      213       +18

Flag
Coverage Δ

unittests
25.35% <15.38%> (-10.68%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

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


Keyboard shortcut to switch ipython console tabs (macOS)?

Problem Description
There are customizable keyboard shortcuts for "cycle to next file" and "cycle to previous file" in the code editor, for all three operating systems.  But there aren't any corresponding keyboard shortcuts for cycling to the next/previous ipython console.
In Windows and Linux, the default "ctrl + pageUp" "ctrl + pageDown" happen to also work for cycling next/previous ipython console tabs (coincidence?), but not for macOS.
I wonder whether there is a way to unify this experience --- namely, provide customizable keyboard shortcuts to cycle to previous/next ipython console tab.

Hi @jsh9,
This is a very good request, we are going to work in unifying our shortcuts for macOS in a future release.
Thanks for reporting!

Hi @jsh9,
While I'm trying to reproduce your error, I encounter that pageUp in mac is fn+Up and pageDown is fn+Down. So if you try in macOS to do cmd + fun + Up you will have the same action than ctrl + PageUp in Linux and Windows. Right now this shortcut is hard-coded, so it is not configurable but we will work on making this configurable for Spyder 5.

Thank you!


Generated docs not linked in a visible enough manner

I've had several people ask me how to find out the namespaces that types and functions live in. While it's been easy enough to point them to the generated docs it would be nice if this information were easier to find. It's currently linked in the readme, but not very clearly.
Can we figure out a way to make this more apparent?

My apologies if this has been asked before in another issue, but is there any reason that finding the namespace is even necessary for Win32 APIs?  In particular, I've been using CsWin32 and because it's scoped only to the Win32 APIs, it allows you simply specify just the method or type you want without the full namespace (e.g. CreateFile).  When the Win32 namespaces were being changed and rearranged like crazy, this made CsWin32 far nicer to use than the Rust crate (didn't have to touch the NativeMethods.txt file, just had to update the usings).  Presumably the namespaces should be becoming more and more stable, so that should be less of a pain going forward, but it still is annoying to lookup the namespaces for every single API that I'm using when it seems like a task that could be automated.  It makes using the Rust crate take far longer to setup and get going than something like CsWin32.  In my mind, the Win32 APIs are a large enough part of the crate to justify special casing them, especially if they are generating enough questions to necessitate better documentation.
Personally, about 95% of the time that I use the docs, I am only using it to look up namespaces.  The other 5% is looking up APIs where the Rust version differs from the expected API, e.g. overloaded members.
I don't actually have a strong opinion about requiring the namespaces, but it did always seem strange to me and it is very time consuming.  However, in the end, what I like most about this crate is that it actually works.  If that requires me to use artificial namespaces, I am fine with that.  I just wanted to throw out the idea that there could be alternative approaches rather than just changing the documentation.

There are a handful of APIs that collide if you were to generate them all in a single namespace. The Windows crate also lets you take advantage of the namespaces to generate all the APIs in a single namespace without having to name them all e.g. Direct3D11::*. I'm not sure how @AArnott is handling these issues.
Taking a step back though, I'm getting closer to solving #432 which should solve both the doc and the namespace problem in a more idiomatic way for Rust developers with a collection of crates that will hopefully be easier to work with in general.

@kennykerr I was not suggesting to generate them in a single namespace, but rather special casing how the names are resolved by the build script.  I was assuming that you would allow either the short name or fully qualified name, so that both CreateFile and Windows.Win32.Storage.FileSystem.CreateFile would be valid.  I'm not actually sure what CsWin32 does, but in the event of a collision/conflict, you could require the fully-qualified name.  The more I think about this issue, the more I have thoughts on it, but it sounds like you think #432 might be a better solution, so maybe I'll hold off until I see how that changes the experience.

Consider also that the windows crate consumes metadata from other sources, such as the Windows App SDK, WebView2, and files directly fed in by the developer, further increasing the likelihood of collisions. That said, one could perhaps argue we could accept the naked declarations and only throw an error if ambiguity arises.
error: "Initialize" is an ambiguous reference to multiple APIs. Provide the full namespace to resolve.
Windows.Win32.Security.ExtensibleAuthenticationProtocol.IAccountingProviderConf.Initialize
Windows.Win32.Security.Cryptography.Certificates.ICertificatePolicy.Initialize
... 29831 more

Will have to think about the value here versus the increased build macro complexity (and potentially perf hit).

Yes, having to scan each namespace for unqualified names would likely be prohibitive.
In the long run, I expect the build macro to be a tool that is only used for more "interesting" use cases.

@riverar I don't think the example you give is a good solution, mainly for the reason you mention of causing collisions (especially with additional WinMDs).  I think it would need to be explicitly-opted into.  Again, I'm not an expert on Rust build scripts and what is possible, but there is an issue that mentions attributes, so perhaps something more like this is more what I'm imagining:
windows::build! {
   [Win32Metadata]
   Initialize
}

However, as I think about it more, I think there are even better solutions out there than that.   Perf and complexity are more of a concern to me than collisions.  However, again, I'll try not to take up too much space on this issue if @kennykerr thinks are other solutions to help.

Can we please discuss this in a separate issue? The discussion here has almost nothing to do with the issue here.

I don't mind if you want to move the link more prominently toward the top of the readme. Not sure what else to suggest at this point.

As the one who contributed most to getting off topic, I do apologize.  In addition to moving the section to the top of the readme, I would also suggest giving that section its own heading to make it more prominent/easier to find.

I have simplified the readme and made this link more prominent.


v4.2.13 not yet available on NPM

Latest available version which fixes "Muted video" bug, is still not available through npm. When can it be published there?
Thanks

@Kamilius yep Sir .. I had some issues to authenticate to npmjs (now fixed), npm publish will come soon.
Thanks for the feedback

@berryamin thanks for an answer :) Waiting for it

@Kamilius Hello, release 4.2.14 is ready, but I'm still unable to use npmjs services, very sorry about that, I'm trying to sort this out .. I'm able to generate tokens there, but when doing "npm publish", it asks for OTP, and I don't know which 2FA auth provider to choose .. any tips greatly appreciated.

Hi @berryamin
someone (most certainly a previous maintainer) enabled the two-factor authentication protection for packages for the mediaelement package. That means you must enable 2FA for your account (choose "Authorization and Publishing"). You do not need an auth provider for that but an app that can generate the 6-digit codes for you. There are two mentioned in the npm-help but you can use any app that can handle TOTP.
PS: if you release a new version, the version number in package.json needs to be updated, too.

Hi @d--j Now I understand the 2FA stuff, and especially TOTP, many thanks for pointing this out.

4.2.14 • Public • Published 2 minutes ago
Thanks everyone for your patience :) Next release will be more fast and efficient :)


[BUG]

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Bloxstrap_20240502T163240Z.log

Are you getting this error every single time you launch?

I was, until I fully restarted my computer and reinstalled bloxstrap

Are you getting this error every single time you launch?

My comment ^
Posted

Seems like restarting your computer would've been the only thing you needed to do since this was an issue with Windows somewhere.


MCXN94X FlexPWM Enablement

Please fix a typo in the commit message. Change inlcuding to including

Thank you, typo fixed.


Login callback to custom scheme

this URL
http://localhost:3000/auth/twitter?callback_scheme=callback.app

callbacks to url:
callback.app:///login?api_key=XXXXXXXXXXXXXXXXXXXXX

that can be handled by iOS and OSX client apps.

LGTM. try it.


How to condition based on multiple features?

I would like to condition the model using multiple features. In my case, I have lot of columns say A, B, C and D and some of the columns are categorical and some are numerical. Now I wanted to implement stable diffusion by conditioning on all the columns together. Please advise what are the modifications I need to do.
Thanks.

Hello @vinodrajendran001,
I think based on your requirement you can use the class embeddings(for categorical) and timestep embeddings for numerical conditioning.
Lets go through the categorical conditions first. Assume you have two categorical variables A/B both having 3 classes each(A1/A2/A3 and B1/B2/B3).
You can either use two seperate class embeddings for each of the two here(https://github.com/explainingai-code/StableDiffusion-PyTorch/blob/main/models/unet_cond_base.py#L61). So class_a_emb and class_b_emb and then based on your input add the the conditioning embedding values to the timestep embedding here (https://github.com/explainingai-code/StableDiffusion-PyTorch/blob/main/models/unet_cond_base.py#L155). So for this case rather than just adding class_emb you would add a_emb and b_emb values both.
You could also combine the classes(assuming every data point has values for both classes). So you have just one class embedding but your embedding values are for (A1B1, A1B2 , A1B3, ..., A3B1, A3B2, A3B3). This will make the changes simpler(infact I think everything will work out of the box and no modification is needed) but it assumes you have values for both classes for all training data and also during generation you would not be able to generate say an image with only one condition A1.
For numerical cases, you can convert them to positional embeddings using(https://github.com/explainingai-code/StableDiffusion-PyTorch/blob/main/models/blocks.py#L5) and then use something like timestep embeddings(https://github.com/explainingai-code/StableDiffusion-PyTorch/blob/main/models/unet_cond_base.py#L148C9-L149C35). With different t_proj layer for timesteps and numerical conditioning field. And then just like class embedding add that to the timestep embedding. Though if your numerical field values do not cover entire range from min to max values then it might make sense to rather bin them and convert them also to classes only.
So assuming one additional numerical condition and the above two classes.
Ultimately you would do this.
time_step_emb = time_step_emb + class_emb + numerical_emb

And then this timestep_emb would be passed to downblocks and upblocks here (https://github.com/explainingai-code/StableDiffusion-PyTorch/blob/main/models/unet_cond_base.py#L167)

That's a good idea. Let me try to translate your inputs into code and experiment.
Thanks :-)


uptest: use the new and public uptest

Description of your changes
Update to consume the new Uptest version.
I have:

[x] Run make reviewable test to ensure this PR is ready for review.

How has this code been tested

/test-examples="examples/iam/role.yaml"

/test-examples="examples/iam/role.yaml"

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

/test-examples="examples/iam/role.yaml"

/test-examples="examples/iam/role.yaml"

/test-examples="examples/iam/role.yaml"

/test-examples="examples/iam/role.yaml"


Allow passing parameters to LuaFunction

https://gist.github.com/Ameliorate/4a652272fbae858959e4fa5252853417 seems to be a valid workaround to this issue, for the time being.


Add sincospi

Resolves #112.

Checklist

Please ensure the following tasks are completed before submitting this pull request.

[x] Read, understood, and followed the contributing guidelines, including the relevant style guides.
[x] Read and understand the Code of Conduct.
[x] Read and understood the licensing terms.
[x] Searched for existing issues and pull requests before submitting this pull request.
[x] Filed an issue (or an issue already existed) prior to submitting this pull request.
[x] Rebased onto latest develop.
[x] Submitted against develop branch.

Description

What is the purpose of this pull request?

This pull request:

Adds a sincospi function that merges the functionality of sincos, sinpi, and cospi

Related Issues

Does this pull request have any related issues?

This pull request:

resolves #112

Questions

Any questions for reviewers of this pull request?

No.
Other

Any other information relevant to this pull request? This may include screenshots, references, and/or implementation notes.

No.

@stdlib-js/reviewers

@rreusser Looks good! Will squash and merge once @Planeshifter approves and Circle CI finishes running its tests.


Receiving transfers is disabled even if I have minted and deposited SVT to the UDC contract

Thanks for filing a bug report :-)
Steps to Reproduce

Connect to the dApp at https://lightclient.raiden.network/staging/
A message Receiving transfers is disabled is shown
Mint and Deposit UDC tokens

Expected Result

I get a message Receiving transfers is enabled
The message Receiving transfers is disabled is not shown after connecting to the dApp

Actual Result

Nothing happens
When I reload the dApp it still shows Receiving transfers is disabled

Additional Infos (Optional)
- Browser & version
- Browser console errors
- Device / OS

@christianbrb
The rate to SVT is also required for receiving. Currently we don't provide a mechanism that can be used to set that value.

@kelsos Thanks :) That's important. I have created issue https://github.com/raiden-network/light-client/issues/1654 and pushed it up in the product backlog. Closing this issue.

How do I set the SVT rate?
CC @agatsoh

It's a little bit tricky now. One way is to go to browser's DevTools, Application, Local Storage, search for raiden_mainnet_<registry_addr>_<account_addr> key, edit it, go to the empty config object and add it there as a json, like:
  ...
  "config": {
    "rateToSvt": {
      "0x<token_addr>": "5000000000000000000"
    }
  },
  ...

Setting it to 5 * 10^18, like I did above, means every 1 * 10^18 wei of token (1 token, if token has 18 decimals, as default) is worth 5 SVT (5e18 wei of SVT), so as the default monitoringReward is 5SVT, the SDK will start sending MS requests once the amount transferred to us in a channel surpasses 1 token, but receiving will be enabled for every token network from scratch.

We do not need to document this, because #1705 is currently being implemented.


Change boost::shared_ptr to std::shared_ptr

Starting with PCL 1.11, PCL uses std::shared_ptr and std::weak_ptr instead of the boost smart pointers. The change leverages type aliases included with the 1.10.0 release

Thanks for your PR. Maybe it's better to change them to pcl::shared_ptr to support the latest PCL as well as older ones.

Done, now it uses pcl::shared_ptr.


Interactive Tutorial - Updating Your App

Hello,
The tutorial area remains black for this interactive step
tested under chrome and same issue with private mode in chrome ( windows 10 home / chrome Version 89.0.4389.114 (Build officiel) (64 bits)
too bad its the most interesting part of the tutorial :)

sorry it was because of a network latency i guess. now its working


Devise confirmable and subdomains: Can't change the confirmation_instructions.html.erb to generate a confirmation_url with a subdomain url in it.

I'm using Rails 4, ruby 2.1.5 and Devise (3.4.1). I have a problem with the email confirmation link, when using devise confirmable. When a user creates an account, they get an email:
You can confirm your account email through the link below:

http://lvh.me:3000/users/confirmation?confirmation_token=xsTNUw5oQYTPf_CBwZXD

However, it doesn't work since the user's subdomain is not on the link, it should be e.g.
http://mysubdomain.lvh.me:3000/users/confirmation?confirmation_token=xsTNUw5oQYTPf_CBwZXD

If I manually add the subdomain link on the browser, it does confirm the account.
How could I change the confirmation_instructions.html.erb link_to to generate a confirmation_url with the subdomain in front of it? For example:

Welcome <%= @email %>!

You can confirm your account email through the link below:

<%= link_to 'Confirm my account', confirmation_url(@resource, :confirmation_token => @resource.confirmation_token, :subdomain => @resource.subdomain) %>

I tried e.g. https://github.com/plataformatec/devise/wiki/How-To:-Send-emails-from-subdomains and https://github.com/fortuity/rails3-subdomain-devise/wiki/Tutorial-(Walkthrough) But neither worked for me, I got an error if I use :subdomain => @resource.subdomain in the confirmation_url:
 "NoMethodError in Accounts#create, undefined method `subdomain' for #<User:0x...>"

Here is the create action in my AccountsController:
def create
  @account = Account.new(account_params)
    if @account.valid? && verify_recaptcha
<EMAIL_ADDRESS><EMAIL_ADDRESS>       @account.save
       @account.create_default_lists
       redirect_to new_user_session_url(subdomain: @account.subdomain)
    else
       render action: 'new'
    end
end

Here are my routes:
user_confirmation     POST   /users/confirmation(.:format)                         devise/confirmations#create
new_user_confirmation GET    /users/confirmation/new(.:format)                   devise/confirmations#new
                      GET    /users/confirmation(.:format)                       devise/confirmations#show

In development.rb I have set, should I somehow add a subdomain setting in front of the host?
config.action_mailer.default_url_options = { host: "lvh.me:3000" }

In ApplicationController I have:
protect_from_forgery
before_filter :authenticate_user!, :set_mailer_host

private

def current_account
   @current_account ||= Account.find_by(subdomain: request.subdomain)
end

helper_method :current_account

def set_mailer_host
   subdomain = current_account ? "#{current_account.subdomain}." : ""
   ActionMailer::Base.default_url_options[:host] = "#{subdomain}lvh.me:3000"
end

end

And here is the error on the console, which I get if I use :subdomain => @resource.subdomain in the confirmation_url. I also tried @resource.account.subdomain, which didn't work either.
ActionView::Template::Error (undefined method `subdomain' for #<User:0x007fbfcc27e5a0>):
    2:
    3:
You can confirm your account email through the link below:

    4:
    5:
<%= link_to 'Confirm my account', confirmation_url(@resource, :confirmation_token => @resource.confirmation_token, **:subdomain => @resource.subdomain**) %>

  app/views/devise/mailer/confirmation_instructions.html.erb:5:in `_app_views_devise_mailer_confirmation_instructions_html_erb___2999600516167812245_702'
  app/controllers/accounts_controller.rb:14:in `create'

This is a Rails issue, not a Devise one, since we are simply relying on Rails to send the e-mails.  :) Therefore, you can simply look up for Rails solutions for sending subdomains in e-mails and adapt them with Devise. Here is one for example:
http://stackoverflow.com/questions/19307994/rails-4-actionmailer-subdomain-urls
In case you make it work, we would love if you could take a couple minutes and update the wiki too! Thanks for writing!

Thanks for your reply @josevalim! I'm using the apartment gem, so I managed to solve this by using 'subdomain: Apartment::Tenant.current'. So I put the following in my confirmation_instructions.html.erb:
<%= link_to 'Confirm my account', user_confirmation_url(confirmation_token: @token, subdomain: Apartment::Tenant.current) %>


RAC-6038: hide try rackhd button until implemented

37902 | Slack Ticket   @jturnquist The "Try RackHD" button on the https://rackhd.github.io appears to do   nothing.
Before

After

@iceiilin  @anhou , can this PR be merged ?


raftstore-v2: use larger target file size

What is changed and how it works?
Issue Number: Ref #14352
What's Changed:
Use the same target file size as if compaction guard is enabled.

This should ease the problem in #14352.
Check List
Tests

Unit test
Integration test

Release note
None

The problem can only be solved by share table cache. As pr body writes, it's only for easing the problem.

After the patch, file count is reduced from 240k per node to 65k on one testing cluster:

/run-triage

/merge

/check-issue-triage-complete


Add note ID to available meta fields

When added, this should also be added to querying: https://github.com/OpenNTF/org.openntf.xsp.jakartaee/issues/265


Buffer size when playing a remote file

Hi, I'm sorry to use the issue tracker to ask this but is there a way to reduce the buffer size when playing a remote http file ? Problem is that the current buffer size is too large and songs can take more than 20 seconds to start playing even in Wifi. Thanks.

+1


Thermal Dynamics compatability

I get the following error in the crash report when trying to use a big reactor with one of the new flux-plated fluiducts
java.lang.ClassCastException: erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPowerTap cannot be cast to cofh.api.energy.IEnergyReceiver
at cofh.thermaldynamics.ducts.fluid.TileFluidDuctFlux.cacheStructural(TileFluidDuctFlux.java:162)
at cofh.thermaldynamics.block.TileMultiBlock.handleSideUpdate(TileMultiBlock.java:394)
at cofh.thermaldynamics.block.TileMultiBlock.onNeighborTileChange(TileMultiBlock.java:470)
at cofh.thermaldynamics.ducts.fluid.TileFluidDuctFlux.onNeighborTileChange(TileFluidDuctFlux.java:57)
at cofh.core.block.BlockCoFHBase.onNeighborChange(BlockCoFHBase.java:189)
at net.minecraft.world.World.func_147453_f(World.java:3875)
at erogenousbeef.core.multiblock.MultiblockTileEntityBase.notifyNeighborsOfTileChange(MultiblockTileEntityBase.java:338)
at erogenousbeef.bigreactors.common.multiblock.tileentity.TileEntityReactorPowerTap.onMachineAssembled(TileEntityReactorPowerTap.java:51)
at erogenousbeef.core.multiblock.MultiblockControllerBase.assembleMachine(MultiblockControllerBase.java:336)
at erogenousbeef.core.multiblock.MultiblockControllerBase.checkIfMachineIsWhole(MultiblockControllerBase.java:320)
at erogenousbeef.core.multiblock.MultiblockWorldRegistry.tickEnd(MultiblockWorldRegistry.java:222)
at erogenousbeef.core.multiblock.MultiblockRegistry.tickEnd(MultiblockRegistry.java:36)
at erogenousbeef.core.multiblock.MultiblockServerTickHandler.onWorldTick(MultiblockServerTickHandler.java:22)
at cpw.mods.fml.common.eventhandler.ASMEventHandler_589_MultiblockServerTickHandler_onWorldTick_WorldTickEvent.invoke(.dynamic)
at cpw.mods.fml.common.eventhandler.ASMEventHandler.invoke(ASMEventHandler.java:54)
at cpw.mods.fml.common.eventhandler.EventBus.post(EventBus.java:138)
at cpw.mods.fml.common.FMLCommonHandler.onPostWorldTick(FMLCommonHandler.java:255)
at net.minecraft.server.MinecraftServer.func_71190_q(MinecraftServer.java:645)
at net.minecraft.server.MinecraftServer.func_71217_p(MinecraftServer.java:547)
at net.minecraft.server.integrated.IntegratedServer.func_71217_p(IntegratedServer.java:111)
at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:427)
at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685)

Must be latest cohf core, latest big reactors?

It's FTB Infinity 1.2.0.
Bigreactors 0.4.1A2
Thermal Dynamics 1.0.0RC1-69
COFH Core 3.0.0RC1-181
Also reproduced with version 0.4.2A2 with no other changes. It seems to only be the flux-plated fluiducts and not any other version of the ducts.

sent it to the other side as well? Its might be a bug in thermal dynamics.

There's most likely been an API change in the new versions of the CoFH Energy interfaces. I expect I need to update BR's Energy interfaces to work with the RC1 versions of the CoFH mods.

Going to do the best I can do get something out for this, but this is a really busy week.

The API change has been in for months. This isn't anything new.

@KingLemming has fixed this in Thermal Dynamics, please upgrade to Thermal Dynamics 3.0.0 RC5 (or newer).


Kyle Headshot

Description of changes:
Headshot for site
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Closing in favor of #382


NIFI-7871 Correct errors for UUID3, UUID5 and hash functions in EL Guide

hash function documentation was added incorrectly in between UUID3 and UUID5 functions. Corrected.
Also improved example provided for UUID3 and UUID5.  Added warning to hash function with an external link referencing NIST policies.

Ran contrib-check and all tests pass. +1, merging.


[WIP] Custom OEmbed providers

no-issue
This PR is open to share code with Kevin and receive feedback

Codecov Report

Merging #13730 (3ec6836) into main (98de2d4) will decrease coverage by 0.15%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main   #13730      +/-   ##
==========================================
- Coverage   38.94%   38.78%   -0.16%
==========================================
  Files        1084     1085       +1
  Lines       73452    73552     +100
  Branches     5021     4899     -122
==========================================
- Hits        28605    28528      -77
- Misses      44803    44978     +175
- Partials       44       46       +2

Impacted Files
Coverage Δ

core/server/api/canary/oembed.js
0.00% <0.00%> (ø)

core/server/services/nft-oembed.js
0.00% <0.00%> (ø)

core/server/services/oembed.js
0.00% <0.00%> (ø)

core/server/data/db/connection.js
62.26% <0.00%> (-32.08%)
:arrow_down:

core/shared/config/loader.js
86.84% <0.00%> (-10.53%)
:arrow_down:

core/frontend/services/routing/registry.js
69.42% <0.00%> (-4.96%)
:arrow_down:

core/server/data/schema/fixtures/utils.js
68.53% <0.00%> (-4.37%)
:arrow_down:

core/server/data/importer/handlers/image.js
42.85% <0.00%> (-4.09%)
:arrow_down:

core/shared/settings-cache/cache.js
65.97% <0.00%> (-3.48%)
:arrow_down:

...ore/server/web/shared/middlewares/url-redirects.js
47.41% <0.00%> (-3.45%)
:arrow_down:

... and 9 more

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 98de2d4...3ec6836. Read the comment docs.


Logging

Add a logging module to decouple Sentry from the app and to improve debugging experience generally

[ ] Add logging module
[ ] Replace Sentry.captureExceptions with equivalent
[ ] Replace Sentry.captureMessage with equivalent
[ ] Replace Sentry.addBreadcrumb with equivalent

Implementation currently used on desktop wallet app here: https://github.com/vegaprotocol/vegawallet-desktop/blob/develop/frontend/src/lib/logging.ts
We also have another implementation from console v1 here: https://github.com/vegaprotocol/slimline-console/blob/master/src/lib/logging.ts

Related to #2506


Need help with testing

I have some problems with implementing delayed brunches into the functional simulator, the first one is that I can't properly test it for some reason. For example, after I added simple test, you have suggested to me, it worked without enabling delayed slots. The other is that as soon as I launch test using new feature, my OS crushes, but i don't see any reasons for that.

@olegladin — could you please take a look?

The other is that as soon as I launch test using new feature, my OS crushes, but i don't see any reasons for that.

Have you tried to run GDB?


Add warning about keys file during match onboarding

          1 Warning

:warning:
Please provide a changelog summary in the Pull Request description @KrauseFx

  Generated by :no_entry_sign: Danger


Breaking @QueryParams camelCase vs snake_case between 6.60.0 vs 6.62.3

Information

Version: 6.62.3

Between 6.60.0 and 6.62.3 at some time, @QueryParams behavior must have changed. Using something like @QueryParams("camelCase") used to work fine, but after updating to the latest version, the argument will be empty even though set via query (/somepath?camelCase=123). req.query shows an object { camel_case: '123' }, so it looks like query params are now automatically snake cased. Is this a bug? Is this expected? Any way to customize this behavior?
I got loads of places where I use camelCased query params and I only coincidentally found this bug (because it doesn't really yield an error).

@bkniffler Can you create a reproducible repository example. Because there is no code that change the query params to snake case in Ts.ED itself ^^.
See you
Romain

Here is a repo example. https://github.com/Romakita/tsed-query-params
All works as expected!


Rename, refactor, and re-organize some stuff

Rename, refactor, and re-organize some stuff
Refactor & re-organize more snapshot type stuff
Remove unused StakeStateV2

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#443
#442
#441
#440  👈 (View in Graphite)
#436
#435
#434
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


[Checkout] Logged in user is not seeing PersonalDetails step

[x] When logged in user clicks "go to checkout" then he's going right to "Review" step
[ ] when on Personal Data step on Checkout user is chosing to log in, then after operation he's redirected into "Review" step
[ ] when on Personal Data step user choses to create an account, then after registration and auto login he's redirected into Shipping step
[ ] if logged in user doesn't have shipping address (fields are filled by us by setting '-' signs), then he's redirected to shipping step with an empty form to fill

he's seeing another step. Wil be implemented in #607


[C++][Python] Helper to generate boolean masks

Describe the enhancement requested
In various conditions it would be helpful to be able to generate boolean masks that point to specific indices of an array.
For example it can be combined with if_else  compute functions to merge two arrays by picking exactly which rows should come from each of one the arrays. Or combined with replace_with_mask to set rows in an array.
At the moment there is no easy way to create such a mask
Component(s)
C++, Python

Or combined with replace_with_mask to set rows in an array.

The proposed helper will still be useful, but just to mention that for this use case we would ideally implement the replace_with_indices kernel (https://github.com/apache/arrow/issues/25505) so you actually don't need to convert your indices to a mask in the first place.


unpacking tuples for easily readibility

Hi Max,
I was following your tutorial and while it was very helpful and easy to follow, I found these bits abit disjointed given that it was hard to keep track of the visit variable. I'm suggesting maintaining a consistent way to do these by just unpacking tuples simply.
If you don't think this suggestion is helpful and/or significant feel free to ignore.
Cheers.

Thank you @ngacho, this makes sense. I will merge your request.


zim crashing on start-up

Describe the bug
When starting zim, it crashes with the following message:
This is zim 0.75.2
Platform: posix
Locale: en_US UTF-8
FS encoding: utf-8
Python: (3, 11, 6, 'final', 0)
PyGObject: (3, 46, 0)

======= Traceback =======
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/main/__init__.py", line 962, in main
    ZIM_APPLICATION.run(*argv[1:])
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/main/__init__.py", line 733, in run
    self._run_cmd(cmd, args) # test seam
    ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/main/__init__.py", line 764, in _run_cmd
    self._run_main_loop(cmd)
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/main/__init__.py", line 806, in _run_main_loop
    w = cmd.run()
        ^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/main/__init__.py", line 261, in run
    from zim.gui.mainwindow import MainWindow
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/gui/mainwindow.py", line 39, in <module>
    from zim.gui.pageview import PageView
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/gui/pageview/__init__.py", line 4083, in <module>
    CURSOR_LINK = Gdk.Cursor.new_from_name(Gdk.Display.get_default(), 'pointer')
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: constructor returned NULL

If starting from a shell, the following messages appear in the console as well:
Gdk-Message: 09:03:57.738: Unable to load pointer from the cursor theme
ERROR: Exception while loading plugin: insertsymbol
Traceback (most recent call last):
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/__init__.py", line 414, in load_plugins_from_preferences
    self.load_plugin(name)
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/__init__.py", line 522, in load_plugin
    klass = self.get_plugin_class(name)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/__init__.py", line 469, in get_plugin_class
    mod = get_module(modname)
          ^^^^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/utils.py", line 36, in get_module
    mod = __import__(name)
          ^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/insertsymbol.py", line 11, in <module>
    from zim.gui.pageview import PageViewExtension
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/gui/pageview/__init__.py", line 4083, in <module>
    CURSOR_LINK = Gdk.Cursor.new_from_name(Gdk.Display.get_default(), 'pointer')
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: constructor returned NULL
Gdk-Message: 09:03:57.761: Unable to load pointer from the cursor theme
ERROR: Exception while loading plugin: versioncontrol
Traceback (most recent call last):
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/__init__.py", line 414, in load_plugins_from_preferences
    self.load_plugin(name)
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/__init__.py", line 522, in load_plugin
    klass = self.get_plugin_class(name)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/__init__.py", line 469, in get_plugin_class
    mod = get_module(modname)
          ^^^^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/utils.py", line 36, in get_module
    mod = __import__(name)
          ^^^^^^^^^^^^^^^^
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/plugins/versioncontrol/__init__.py", line 28, in <module>
    from zim.gui.mainwindow import MainWindowExtension
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/gui/mainwindow.py", line 39, in <module>
    from zim.gui.pageview import PageView
  File "/nix/store/hqqccmp915jlmwsq52gsavshxr5kfpvj-zim-0.75.2/lib/python3.11/site-packages/zim/gui/pageview/__init__.py", line 4083, in <module>
    CURSOR_LINK = Gdk.Cursor.new_from_name(Gdk.Display.get_default(), 'pointer')
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
(...)

The same warnings, errors and tracebacks are also shown for the screenshot, quicknote, tags, pageindex and journal plugins.
zim had been working fine for me for years, so this appears to be related to a recent update to NixOS 23.11 (i.e. some commit in the last week or two, probably).
Steps To Reproduce

start zim

Expected behavior
No errors, zim starts up fine.
Screenshots
See above.
Notify maintainers
cc @pSub

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.77, NixOS, 23.11 (Tapir), 23.11.git.729a974ad17c`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.1`
 - nixpkgs: `/nixdev/nixpkgs`

Add a :+1: reaction to issues you find important.

I was able to fix this (or at least, work around it) by setting a default cursor theme. In my case, I simply added the following package to the list of user packages (i.e. users.users.<username>.packages):
         (pkgs.runCommandLocal "gtk-cursor-fix" {} ''
            dir=$out/share/icons
            mkdir -p $dir
            ln -s ${gnome.adwaita-icon-theme}/share/icons/Adwaita $dir/default
         '')

The above code was a minor adaptation (to use a different theme) of the code in this comment: https://github.com/NixOS/nixpkgs/issues/207339#issuecomment-1762695954


pd.read_excel now working

The pd.read_excel() function is not working where it used to work before. I get the following runtime error:
RuntimeError: dictionary changed size during iteration
My current workaround is to convert to a csv file, but would be ideal if the read_excel worked again.
Anyone else experiencing this?

You reported at a wrong repository?


No go-to-definition support across files in vscode.dev (typescript)

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.67.2 (vscode.dev)
OS Version: Mac OS Monterey 12.4, Chrome Version 102.0.5005.61 (Official Build) (x86_64)

The web version of vscode is lacking some LSP features for Typescript, like the go-to definition across files.
Steps to Reproduce:
Open a typescript project
Do a language service action
Expected Result: Same as desktop experience

Duplicate of https://github.com/microsoft/TypeScript/issues/47600


Cleaner UI

Changed frontend in an attempt to improve user experience 😳✌

Ready For review. This PR also fixes the bug referenced in a previous issue (#72).


Retry GetLatesetBlockByHeight call if the call errors out during block enqueue

We noticed the indexer erroring out when:

End Height = -1
The indexer has caught up to the blockchain current height
The indexer sleeps to let new blocks be created
The indexer attempts to get the latest height

The error in the below picture is probably a retry-able error, we could retry to get the latest block height a set number of times instead of just crashing:

The code at issue is here:
https://github.com/DefiantLabs/cosmos-tax-cli/blob/c3e003ae4b1ea1fa186d0168ba1b27559eace1a5/cmd/index.go#L278-L281

Closed by #485


Swallow OIDC errors

Pull Request Test Coverage Report for Build f9d91be9d1fc3dfc761a723bfec87efcb59633d6-PR-1025

0 of 4 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.1%) to 66.299%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_http/lib/fz_http/oidc/start_proxy.ex
0
4
0.0%

Totals

Change from base Build aa67b689e583a052c74bd014d9bb2f32c38932ad:
-0.1%

Covered Lines:
1141

Relevant Lines:
1721

💛  - Coveralls


Awesome Mac application sharing recommendation - Awesome Mac

http://wangchujiang.com/awesome-mac/
A curated list of awesome applications, softwares, tools and shiny things for Mac osx. - Awesome Mac

Suggest ideas here.


Update tapir-core, tapir-http4s-server, ... to 0.17.0-M11

Updates

com.softwaremill.sttp.tapir:tapir-core
com.softwaremill.sttp.tapir:tapir-http4s-server
com.softwaremill.sttp.tapir:tapir-json-circe
com.softwaremill.sttp.tapir:tapir-openapi-circe-yaml
com.softwaremill.sttp.tapir:tapir-openapi-docs
com.softwaremill.sttp.tapir:tapir-swagger-ui-http4s

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.softwaremill.sttp.tapir" } ]

labels: library-update, semver-pre-release

breaking changens in tapir api, waiting for stable release


Grav permissions and /or user access not working correctly

Grav permissions and /or user access not working correctly. When adding access to a page and enabling dynamic page viewing, the page is still displayed. In addition, adding access to a page is not limiting access to the page by other users as it should.

duplicate: https://github.com/getgrav/grav-plugin-login/issues/166


Add Overview(s) on Building a Layer 2 (with Avail)

Context
After some deliberation, it seems like starting with this serves better - outlining the various considerations and associated principles in building a layer two (whether rollup or validium) and how data availability fits in - and where Avail comes into play and how Avail "enables", "powers", or "is incorporated" in the design of the solution.
Acceptance Criteria

[x] L2 Scaling Solutions: Provide a general overview, focusing on data availability.
[x] Data Availability (DA) Overview: Differentiate between off-chain and on-chain DA.
[x] Layer 2 Design Principles: Discuss considerations for building Layer 2 solutions, be it rollup or validium.
[x] Modular Architectures: Delve into architectures of "modular" blockchains, highlighting rollup-based solutions.

Include a transaction + data lifecycle

[x] Role of Avail: Describe Avail's integration and its significance in shaping validiums and optimiums - "Avail-powered".

Include a transaction + data lifecycle

Let's refocus this into a "Solutions" page?
Marketing team will have a solutions page on the website - we should have an equivalent on the docs that goes into more depth (but still links out to other articles for details)

2023-10-10 Update:

Drafts in progress and ready to propose changes mid-week.
Effort tied into some of the other explainer material we planned to create.

This is captured in https://github.com/availproject/availproject.github.io/issues/163


Add new parameter to createLoadBalancerRule API

Description
ACL rules are currently not enforced when a Load Balancer is used. When created, ACL rules are implemented in the VR in the FORWARD chain. In order for the LB to work only through the configured IPs, it is necessary to configure the rule in the INPUT chain. However, since all traffic into the VR is being allowed, only forwarding is blocked to the unconfigured IPs.
To work around this situation, it is possible to configure LB rules via createLoadBalancerRule API. However, the cidrlist parameter used to configure the CIDRs that can access the load balancer, had been deprecated in favor of the firewall rule implementation, which is not intuitive and does not support VRs in VPCs. Therefore, the parameter was reimplemented to allow users to create rules in the Load Balancer backend that restrict the access according to the source IP.
Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[ ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?
New unit tests were created. Alongside that, the changes were manually tested in a local lab. By using the createLoadBalancerRule API with the cidrlist parameter to restrict network traffic.

@JoaoJandre
there are many parameters supported by haproxy but not supported in cloudstack.
I suggest you to collaborate with @ravening on https://github.com/apache/cloudstack/pull/5799

@JoaoJandre there are many parameters supported by haproxy but not supported in cloudstack. I suggest you to collaborate with @ravening on #5799

I would rather move on with this PR only, as it is re-adding a feature that was deprecated/removed without a proper alternative. This PR is small, concise, unit tested, and ready to be used in production. The alternative you pointed out is a huge PR that looks a bit too complicated. Therefore, I would rather move on with this small addition to restore the API workings.
Anyways, I can note that PR here, and if we ever need such a featureset, we might be able to help there.

@weizhouapache, PR #5799 has being developed through 2 years from now (originally developed in PR #4141). It passed through 4.15, 4.16, and 4.17, and we do not have guarantee that will be merged in 4.18.  Also, there is a lot of changes in #5799, which would require a good documentation and a lot of tests. Therefore, I would rather go with these small changes instead of blocking the feature for something we do not have guarantee.

@weizhouapache, PR #5799 has being developed through 2 years from now (originally developed in PR #4141). It passed through 4.15, 4.16, and 4.17, and we do not have guarantee that will be merged in 4.18. Also, there is a lot of changes in #5799, which would require a good documentation and a lot of tests. Therefore, I would rather go with these small changes instead of blocking the feature for something we do not have guarantee.

@GutoVeronezi @JoaoJandre
as far as I know, #5799 is not beeing developed, tt has been deployed in their production for around two years.
It is ready for review and test. The reason it is not merged is, nobody in cloudstack community has reviewed and tested it.
I hope you guys can review/test it and collaborate with @ravening @soreana on merging #5799 and changes for cidrlist into 4.18

based on tests performed in our labs and code reviews. Lgtm.

@weizhouapache I have a suggestion for #5799. We can test it gradually, like what we did when we developed it. We can have a branch named HAproxy-LoadBalancer in the community. I will port all the changes from #5799 to HAproxy-LoadBalancer one by one. When satisfied with its quality, we can merge it to the main branch. That way, it would be far easier for community members to test it.
This feature could be part of it, too.

@soreana
Each PR can be merged only if there are at least 2 approvals and all smoke tests pass.
Most users use official release. If someone want to test a feature, they can build and test the specific branch, it is not needed to merge it into main.

Hey @DaanHoogland could you review and run the tests?

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

Packaging result: :heavy_check_mark: el7 :heavy_check_mark: el8 :heavy_check_mark: debian :heavy_check_mark: suse15. SL-JID 3900

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-4618)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 37051 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr6460-t4618-kvm-centos7.zip
Smoke tests completed. 101 look OK, 0 have errors
Only failed tests results shown below:

Test
Result
Time (s)
Test File

@acs-robot a Jenkins job has been kicked to build UI QA env. I'll keep you posted as I make progress.

UI build: :heavy_check_mark:
Live QA URL: http://qa.cloudstack.cloud:8080/client/pr/6460 (SL-JID-2086)