Size dismatch when load your provided pre-trained model

RuntimeError: Error(s) in loading state_dict for DistributedDataParallel:
        size mismatch for module.unet.conv.2.weight: copying a param with shape torch.Size([2, 2, 2, 64, 32]) from checkpoint, the shape in current model is torch.Size([64, 2, 2, 2, 32]).
        size mismatch for module.unet.u.conv.2.weight: copying a param with shape torch.Size([2, 2, 2, 128, 64]) from checkpoint, the shape in current model is torch.Size([128, 2, 2, 2, 64]).
        size mismatch for module.unet.u.u.conv.2.weight: copying a param with shape torch.Size([2, 2, 2, 256, 128]) from checkpoint, the shape in current model is torch.Size([256, 2, 2, 2, 128]).
        size mismatch for module.unet.u.u.u.conv.2.weight: copying a param with shape torch.Size([2, 2, 2, 256, 256]) from checkpoint, the shape in current model is torch.Size([256, 2, 2, 2, 256]).
        size mismatch for module.unet.u.u.u.deconv.2.weight: copying a param with shape torch.Size([2, 2, 2, 256, 256]) from checkpoint, the shape in current model is torch.Size([256, 2, 2, 2, 256]).
        size mismatch for module.unet.u.u.deconv.2.weight: copying a param with shape torch.Size([2, 2, 2, 128, 256]) from checkpoint, the shape in current model is torch.Size([128, 2, 2, 2, 256]).
        size mismatch for module.unet.u.deconv.2.weight: copying a param with shape torch.Size([2, 2, 2, 64, 128]) from checkpoint, the shape in current model is torch.Size([64, 2, 2, 2, 128]).
        size mismatch for module.unet.deconv.2.weight: copying a param with shape torch.Size([2, 2, 2, 32, 64]) from checkpoint, the shape in current model is torch.Size([32, 2, 2, 2, 64]).

The training process is successful and I can load my own trained model to do evaluation.
Here is my semantic_kitti_unet32_spherical_transformer.yaml
DATA:
  data_name: semantic_kitti
  data_root: /data/dataset/SemanticKITTI/dataset/
  label_mapping: util/semantic-kitti.yaml
  classes: 19
  fea_dim: 6
  voxel_size: [0.05, 0.05, 0.05]
  voxel_max: 120000

TRAIN:
  # arch
  arch: unet_spherical_transformer
  input_c: 4
  m: 32
  block_reps: 2
  block_residual: True
  layers: [32, 64, 128, 256, 256]
  quant_size_scale: 24
  patch_size: 1
  window_size: 6
  use_xyz: True
  sync_bn: True  # adopt sync_bn or not
  rel_query: True
  rel_key: True
  rel_value: True
  drop_path_rate: 0.3
  max_batch_points: 1000000
  class_weight: [ 3.1557,  8.7029,  7.8281,  6.1354,  6.3161,  7.9937,  8.9704,
                          10.1922,  1.6155,  4.2187,  1.9385,  5.5455,  2.0198,  2.6261,  1.3212,
                          5.1102,  2.5492,  5.8585,  7.3929]
  xyz_norm: False
  pc_range: [[-51.2, -51.2, -4], [51.2, 51.2, 2.4]]
  window_size_sphere: [2, 2, 80]
  window_size_scale: [2.0, 1.5]
  sphere_layers: [1,2,3,4,5]
  grad_checkpoint_layers: []
  a: 0.0125
  loss_name: ce_loss
  use_tta: False
  vote_num: 4

  # training
  aug: True
  transformer_lr_scale: 0.1
  scheduler_update: step
  scheduler: Poly

  power: 0.9
  use_amp: True
  train_gpu: [0,1]
  workers: 32  # data loader workers
  batch_size: 4 # batch size for training
  batch_size_val: 4 # batch size for validation during training, memory and speed tradeoff
  base_lr: 0.006
  epochs: 100
  start_epoch: 0
  momentum: 0.9
  weight_decay: 0.02
  drop_rate: 0.5

  ignore_label: 255
  manual_seed: 123
  print_freq: 10
  save_freq: 1
  save_path: runs/semantic_kitti_unet32_spherical_transformer
  weight: model/model_semantic_kitti.pth
  resume:
  evaluate: True  # evaluate on validation set, extra gpu memory needed and small batch_size_val is recommend
  eval_freq: 1
  val: True

Distributed:
  dist_url: tcp://<IP_ADDRESS>:6789
  dist_backend: 'nccl'
  multiprocessing_distributed: True
  world_size: 1
  rank: 0

Hi,
This issue seems to be caused by version inconsistency of spconv. Please change another version of it, and try again.

Thanks for your reply.
I checked my spconv version, which I installed is spconv-cu118 but it doesn't has the version 2.1.21

Could you try to install spconv-cu114?


setState() called after dispose()

Error on starting the app

is this issue still open

is this issue still open

No, I have identified the cause, and got it fixed in #268


[type:fixbug]fix bug :after add paged is fail

about:  https://github.com/apache/incubator-shenyu/issues/3062
fix ： Pagination fails after adding or editing

@daiwenyu cc : )

@li-keguo Hi，buddy about src/routes/System/PluginHandle/index.js , I think the current page number should be kept，just remove {}, thanks

@li-keguo Hi，buddy about src/routes/System/PluginHandle/index.js , I think the current page number should be kept，just remove {}, thanks

@daiwenyu Hi  it's ok to do this,
But I encountered a bug like this before：
There are query conditions before adding, but I didn't click the query button, my page number is on the last page，
After adding, the list cannot be queried for data。
I think all add needs to be reset after adding

e..... new condition reset too...

i try to fix it，


PathLike behavior for File

With the recent changes to the DataFuture behavior and the File based model that we are moving to in general, we want to have File behave as closely to old behavior as possible so that there's least amount of code breakage. This is one such case:
Earlier we could do this since the result of a DataFuture was a string

f = open(DataFuture1.result(), 'r')

Now the result of a DataFuture is a File, which can't simply be passed to open:

f = open(File, 'r') <-- Fails

This can be fixed by making File follow the os.PathLike interface

I believe @kylechard is already working on this


Image optimisation and progressive JPEG support

Fixes #10
This PR implements image optimisation using Pillows optimize feature. It also implements a switch to convert JPEG files to progressive which should improve user experience when used for images on the web.
We may still want to support external image optimisers as I think they probably have a few more tricks than Pillow does, but this PR is definitely an improvement.

Looks good, apart from my doc niggles!

Thanks @tomdyson!

Any update for this getting merged?


go.dev: insert space after Example

What is the URL of the page with the issue?
https://pkg.go.dev/golang.org/x/text@v0.3.2/encoding/ianaindex?tab=doc#example-Index
Though I tested at the link, you are able to observe anywhere where Example exists.
What is your user agent?
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/80.0.3987.132 Safari/537.36
Latest chrome
Screenshot

What did you do?

Open the link.
Click Example text.

What did you expect to see?
It's design proposal, not real bug. I think space should be inserted after Example box (after Output:  in the image).
What did you see instead?

Thanks for the feedback! We will plan to address this as part of an upcoming round of UX changes.
/cc @fflewddur

This is fixed. Thanks @Sajmani for the contribution!


Compression of result files

The result files contain much redundancy and can, hence, become very large. So we should think of compression techniques to reduce their size. On the one hand, these could be manual compression techniques such as dictionary encoding for file and attribute names or a more compact syntax ("R.[A,B,C]" instead of "R.A, R.B, R.C"). On the other hand, we could use compression libraries for zip, rar, 7zip or other formats.

Serializer Components for each result type to compress/format results independently, i.e., comma separated strings for INDs, UCCs, FDs and json for conditional etc.

Also review these serialization libraries:

ProtoBuf
Kryo


Merge functions in menu()

Merging of the functions "Buy/Sell resources" into "Marketplace" and "Alert attacks / Alert wine running out" into "Alerts / Notifications" options. Oh and also renamed "Search for island spaces" into "Monitor islands".
Due to new functions getting added into Ikabot, the menu is starting to get pretty clustered. These functions are the most logical ones to merge so guess we can start from here. :D
Since we're obviously not going to be having hundreds of functions in total, I tried to make it simple and gave each option their own set of 10 selections starting from 100.

All this PR is missing is the relevant changes to the README.md file.

All this PR is missing is the relevant changes to the README.md file.

Added relevant changes to the README.md file as well. :) I figured the format looks better if the menu option is used for both sub-options since that's how they are accessed by. That could also be done with the "Options / Settings" imo, but I'll leave that up to you guys.
Sorry for the double push, I'm new to using Github and I'm actually contributing for the first time ever lol.


Typescript emitting es6

A simple PATCH to make sure the ts-loader's output goes through babel so we can use things like export in a .tsx file.

:+1:


Support for webhooks

It looks like there is REST support for webhooks .

Would it be a good enhancement to add support for managing webhooks to this provider?
Would a pull request for this be welcome?

We would welcome a PR

@markgalpin - another feature request

what about xray webhooks?


Removing wrong FK definition

Why make this change?
If there is a relationship defined for a (source,target) in the database with right cardinality as ONE, we add the relationship in both the directions (source->target and target->source) to the source's RelationshipMetadata corresponding to the target entity's entry in RelationshipMetadata.TargetEntityToFkDefinitionMap dictionary.
We do this because the relationship can be 1:1 or N:1. In case of N:1, the first FK (from source->target) would be present. In case of 1:1, either or both of them can be present. But all this is known to us only at a later stage when we collect metadata from the database and actually infer which of the two relationships (or both) is/are valid.
After validating the correct relationship, we don't remove the other relationship which we added earlier. The redundant relationship jadds a redundant JOIN condition (I think this is something which is visible in the sql query generated by DAB highlighted in this issue: https://github.com/Azure/data-api-builder/issues/1940).
What is this change?
The functioning of SqlMetadatProvider.FillInferredFkInfo() is changed such that for all the FK definitions present for a target entity in the source entity's definition, the FK definitions for a target entity in the source entity's definition contain:

One entry for relationships defined between source to target in the database (via FK constraint) in the right order of referencing/referenced entity.
Two entries for relationships defined in the config between source to target (which don't exist in the database).

The above is achieved via a call to a newly added method SqlMetadataProvider.GetValidatedFKs() which  loops over all the foreign key definitions defined for the target entity in the source entity's definition and adds to the set of validated FK definitions:

All the FK definitions which actually map to a foreign key constraint defined in the database. In such a case, the source/target fields are also provided in the config, they are given precedence over the FK constraint.
FK definitions for custom relationships defined by the user in the configuration file where no FK constrain t exists between the pair of (source, target) entities.

How was this tested?
Needed manual testing to ensure the redundant join condition is not added in the query.
For a nested query like:

where the configuration for Book entity looks like:

the query generated before the fix (in main):
SELECT TOP 100 [table0].[title] AS [title], JSON_QUERY ([table1_subq].[data]) AS [publishers]
FROM [dbo].[books] AS [table0] OUTER APPLY (SELECT TOP 1 [table1].[name] AS [name]
FROM [dbo].[publishers] AS [table1]
WHERE [table0].[publisher_id] = [table1].[id] AND [table1].[id] = [table0].[publisher_id]
ORDER BY [table1].[id] ASC FOR JSON PATH, INCLUDE_NULL_VALUES,WITHOUT_ARRAY_WRAPPER)
AS [table1_subq]([data])
WHERE 1 = 1
ORDER BY [table0].[id] ASC FOR JSON PATH, INCLUDE_NULL_VALUES

after the fix:
SELECT TOP 100 [table0].[title] AS [title], JSON_QUERY ([table1_subq].[data]) AS [publishers]
FROM [dbo].[books] AS [table0] OUTER APPLY (SELECT TOP 1 [table1].[name] AS [name]
FROM [dbo].[publishers] AS [table1]
WHERE [table0].[publisher_id] = [table1].[id]
ORDER BY [table1].[id] ASC FOR JSON PATH, INCLUDE_NULL_VALUES,WITHOUT_ARRAY_WRAPPER)
AS [table1_subq]([data])
WHERE 1 = 1
ORDER BY [table0].[id] ASC FOR JSON PATH, INCLUDE_NULL_VALUES

<Observe the removal of redundant join condition in the 4th line in the second query>
Similar observations for MySql:
SELECT COALESCE(JSON_ARRAYAGG(JSON_OBJECT(@param3, `subq6`.`title`, @param4, `subq6`.`publishers`)), JSON_ARRAY()) AS `data`
FROM ( SELECT `table0`.`title` AS `title`, `table1_subq`.`data` AS `publishers` FROM `books` AS `table0` LEFT OUTER JOIN LATERAL (SELECT JSON_OBJECT(@param2, `subq5`.`name`) AS `data`
FROM ( SELECT `table1`.`name` AS `name` FROM `publishers` AS `table1`
WHERE `table0`.`publisher_id` = `table1`.`id`
ORDER BY `table1`.`id` ASC LIMIT 1 ) AS `subq5`) AS `table1_subq` ON TRUE WHERE 1 = 1 ORDER BY `table0`.`id` ASC LIMIT 100 ) AS `subq6`

For pgSql:
SELECT COALESCE(jsonb_agg(to_jsonb("subq6")), '[]') AS "data" FROM ( SELECT "table0"."title" AS "title", "table1_subq"."data" AS "publishers" FROM "public"."books" AS "table0"
LEFT OUTER JOIN LATERAL (SELECT to_jsonb("subq5") AS "data" FROM ( SELECT "table1"."name" AS "name"
FROM "public"."publishers" AS "table1"
WHERE "table0"."publisher_id" = "table1"."id"
ORDER BY "table1"."id" ASC LIMIT 1 ) AS "subq5") AS "table1_subq"
ON TRUE
WHERE 1 = 1 ORDER BY "table0"."id" ASC LIMIT 100 ) AS "subq6"

/azp run

/azp run

/azp run

In BaseSqlQueryStructure.AddJoinPredicatesForRelatedEntity(), there is conditional logic to determine whether the foreign key definition is valid or not.
With this change, can you please evaluate whether that can be removed?

At the moment, this PR is target towards main. But this needs to be ported to dev/NestedMutations as well - just calling it out.

Yes, correct. This needs to be ported and we need to build on top of it to handle other invalid cases with nested insertion. I had a similar PR for that targeted to dev/NesredMutations but I have closed it temporarily and will reopen it once this PR is merged.

In process of adding/analysing tests. Will mark the PR ready for review again when done. Can review non-testing changes meanwhile.

/azp run


Rename how-what-istio-started.md to how-was-istio-started.md

salvaging the non controversial part #396

Jenkins job istio.github.io/presubmit passed


Change error handling behaviour

I got this down to a fairly minimal change. I don't have time right now to figure out why this changes both error messages, but I suspect something to do with MonadThrow.

I think I figured out what's going on. I could fix it, but I'll wait for your error handling change to land first.


Travis Build Error: libsass bindings not found. Try reinstalling node-sass?

Can someone please save my skull from being pounded firmly against the wall and tell me how I can find a fix? This is the output from Travis http://www.codeshare.io/Z2vdz Using gulp-sass 1.2.2. Here is my travis file as well. Thanks y'all

@kevva This doesn't seem to be #497, which describes several unrelated bugs, and the defect is still outstanding.
Are you certain this ticket should be closed?

I'm using the latest version of gulp-sass which pulls in node-sass 2.0.0 beta, and I'm still experiencing this issue.

@grayghostvisuals, add
env:
  SKIP_SASS_BINARY_DOWNLOAD_FOR_CI=true

to your .travis.yml. You can always use node-sass' own travis config for reference.
@StoneCypher, these are related issues. Some folks have not reported full logs and since the partial logs differ, hence the confusion. But rest assured most of the installation issues have commonalities.
@goodforenergy, are you facing the issue locally or on CI server? If it is happening locally, please execute these commands one at a time: https://gist.github.com/am11/e5de3c49c219f0811e1d#comment-1386582. If it fails, please create a similar GH gist with the produced output and share the link.

@am11 Here's my current Travis file https://github.com/grayghostvisuals/transformicons/blob/master/.travis.yml
Do you think I still need to add that line you left above?

@grayghostvisuals, apparently you are not getting the error described in this issue anymore. So no, you do not need to add that line.
Node-sass' install script first try to download the binary and test it. If the binary is currpted or incompatible with your system, it falls back to manual compilation of binary (given the required tools are available on the system, otherwise it will fail the build).
It seems like it is downloading the correct version (v1.2.4) of node-sass binary which is compatible with OS run by TravisCI's VM. Though the current version of node-sass is v2.0.0-beta.

@am11 - it is not happening locally. We use the frontend-maven-plugin to run a build task that downloads node and executes an npm install on the build machine, and operates out of a local node_modules folder for that project. The strange thing is that we have some projects doing the same thing on the same machine, and executing absolutely fine - but certain projects with no discernible differences in the setup will fail.
Our CI server doesn't have node installed globally, but I tried doing that and running the commands in the gist you linked, and everything seemed fine.
This is the output of a failed build, compared with one with no issues (a branch of the same project).
I did just notice that the version of node we install using that build task is a little behind.. will try updating.
Any advice is much appreciated.

@goodforenergy, if this is happening intermittently on the same machine, it could be due to the network or timeout issue during node-sass being installed. I am not sure about the frontend-maven-plugin internals, but there might be a way to adjust the timeout to let the module finish its post-installation process. Moreover, there might be a way to get verbose output for each command executed.
Momentarily, taking a closer look at the failure logs suggest that it throws at clean step: Running 'gulp clean --no-color' ... before gulp build. Can you check if there is anything trying to require node-sass during clean process? (just curious: is the clean step necessary in your setup?)

@am11 - thanks for the ideas. Thankfully / frustratingly, changing the node / npm version specified in frontend-maven-plugin to v0.10.36 / 1.4.12 magically resolved the issue.
I wonder though if you're right, and it's just a timing issue (and I've perhaps just been lucky with the last few builds). I had a look at the frontend-maven-plugin docs but there is no config available to specify a timeout.
We can probably do without a clean there, but the following task is a build, which definitely requires node-sass. The reason it's being required at that point is the structure of my gulp tasks - I've separated them into different task files and my gulpfile.js just requires all my task files to make them all available.
I could try explicitly requiring gulp-sass (which itself requires node-sass) inside my Sass task rather than at the top of my sass.js task file. If I moved the require I could also add a task to emulate a small delay between npm install and the rest of the tasks to see if that helps... except now I can't reproduce the issue to see if it will fix it (facepalm).

@goodforenergy, see Heisenbug. :smiley:
(guessing here) if it is somehow downloading the older version of node-sass (v1.1.4), then binary related issue is possible. While the error suggests as if libsass is not downloaded, it might not be a partial download thingy but actually libc dependency thing (which was the issue with some prior versions of libsass). If the problem persist, would be worth a try to explicitly download npm install<EMAIL_ADDRESS>(which would demand more changes, so hopefully that is not required).

@goodforenergy It's worth remembering that gulp dependencies are a directed graph, not a tree.  There's nothing stopping those dependencies from redundantly depending on one another, provided no cycles are created.  It's perfectly fine for Z to depend on [a,b,c], then for C to also depend on [a,b], in the hope of resolving order of execution.  Part of gulp's job is to find a sensible way to parallelize what remains of the ordering echelon.
Hope that helps

FWIW: I just had the reported issue in a case where I installed node-sass using node 10.x, updated node to 12.0 and then my script failed (in my case: a gulp task). Just completely wiping the node_modules directory and rerunning npm install (using node v12) fixed the issue.
Might not be related to the original issue, but this is the first match for this exact error message on google. Maybe it helps someone else.

@apfelbox, starting with node-sass v2, node.js v0.12 and iojs v1.2 are supported. If you are running older version of node-sass and updated node.js to recently released v0.12 from v0.10, then you will face the issue. You can also explicitly specify the version when downloading the module; npm install<EMAIL_ADDRESS>

@am11 Thanks a lot, it actually worked.

@am11 I am running 2.0.1. The precompiled binary was placed in vendor/darwin-x64-node-0.10/ which was resolved in runtime by this piece of code (the last line):
var candidates = [
    path.join(__dirname, '..', 'build', 'Debug', 'binding.node'),
    path.join(__dirname, '..', 'build', 'Release', 'binding.node'),
    path.join(__dirname, '..', 'vendor', process.sassBinaryName, 'binding.node')
  ];

which returns darwin-x64-node-0.12 for node v12.x.
So my issue was just a simple mismatch in file paths. And that was easily solved by just running npm install. (please note: the reinstall would be necessary in either case, if the binaries differ between v10.x and v12.x. If they are ABI compatible the reinstallation wouldn't have been technically necessary, except of the change in directory name)

@apfelbox that is right. npm install should be run once after updating node.js. This is not always the case though but only when the minor version of node.js, io.js or atom-shell is incremented, then the npm modules which uses C++ add-ons need to be rebuild / reinstall.

This solved it for me:
npm uninstall node-sass
"node-sass": "^2.0.1" < in package.json
sudo npm update < in project

Thanks @StoneCypher. @am11 Yes, definitely a heisenbug, haha! Thanks for your suggestions, I'll keep them in mind if it crops up again.

After upgrading the node node to 0.12.0, I met the same problem.
grunt server

Loading "sass.js" tasks...ERROR
>> Error: `libsass` bindings not found. Try reinstalling `node-sass`?

@apfelbox, run these commands: https://gist.github.com/am11/e5de3c49c219f0811e1d#comment-1386582 and make a similar gist with your output.

@wangxiao same!

@luozhihua  Reinstall node 0.11.9 will work.

@wangxiao Thanks, run this commands in the directory will work too: npm rebuild node-sass

@luozhihua thanks! The rebuild did the trick

@luozhihua rebuild worked for me!

@luozhihua rebuild worked for me too, thx !

There is no need to email all these people with "this also worked for me."

Maybe Github need a "like" feature.

yeah, It will be convenient for us to find the right answer quickly and not disturb the most project watchers.

Running into this same issue, fresh install on Ubuntu 14.04, Node version 0.10.35. The same project builds fine on Mac OS, when I push to Jenkins, am getting this same error (libsass bindings not found. Try reinstalling node-sass)

@palimpsests, which version of node-sass?

The pre-release v3.0.0-pre is out. See the breaking changes in README.
npm install<EMAIL_ADDRESS>
To see the runtime coverage matrix, see node-sass-binaries readme: https://github.com/sass/node-sass-binaries/#node-sass-binaries.
Let us know what you think on https://gitter.im/sass/node-sass.

@am11 version 2.0.1 of node-sass

@palimpsests, can you test with v3.0.0-pre?

what the heck kind of error is this. it won't go away

@xtianus79 Run this commands in the directory will work: npm rebuild node-sass

what's odd about it is that I am using Visual studio to run my project's bower... and Npm packages... now when I rebuild in my CLI which is to the folder everything works... but then VS doesn't work.  When I rebuild to VS then that works and now my CLI folder doesn't work when using git bash

@xtianus79, make sure VS2015-preview and git bash are using same npm minor versions.

@am11 do yo mean for the node-sass package?  because they should be exactly the same as I put them in....

and the only reason why they are there is because VS build and places the npm packages in

Sorry I mean node.js version, not npm.

@am11 how can I find out what version of node.js  version

@xtianus79, I have no idea. I think you can find answer to such queries at http://stackoverflow.com/. Use the tag visual-studio-2015 and node.js.

Thanks.  And what is the nvm thing you were showing the other day.  Would that fix things?
Sent from my Windows Phone

From: Adeel<EMAIL_ADDRESS>Sent: 3/18/2015 12:56 PM
To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: Re: [node-sass] Travis Build Error: libsass bindings not found. Try reinstalling node-sass? (#532)
@xtianus79, I have no idea. I think you can find answer to such queries at http://stackoverflow.com/. Use the tag visual-studio-2015 and node.js.

Reply to this email directly or view it on GitHub:
https://github.com/sass/node-sass/issues/532#issuecomment-83056704

nvmw, but you will still need to 'somehow' configure VS to use the preferred node.js version, instead the one which they shipped VS with..

thanks @am11 ... would you know how to do that by any chance?  thanks
christian

unsubscribing, even though i used to want to watch this bug

@am11 they said it is 10.31 and they would write a blog post about it tomorrow.  however their solution to fix it was not clear and it didn't seem to have any affect.  it always seems like this stuff is baked in.

@xtianus79, baked-in stuff is good. But it would be nice if they let you manage which version you want to use, and even which runtime; node.js and/or io.js (which is practically node.js on steroids!).

@am11 agreed.  However, it seems like they want to let you change it but it doesn't seem to actually work.  Kind of the like the secret .gitignore file... which I figure the secret file was there because when i coped another one into the path it changed it to -copy... lol

@am11 totally fixed my issue with your help and Mads blog post he released today...
http://blogs.msdn.com/b/webdev/archive/2015/03/19/customize-external-web-tools-in-visual-studio-2015.aspx
For anyone looking to have your path setup correctly to use PS - make sure ruby, and git, NPM, and Ruby are in your path...

@luozhihua you're suggestion finally worked but the conflict was VS Vnext was using a baked in node 0.10.31 version and I have 0.12.0 installed on my path.

@xtianus79, good to know and thanks for sharing the blog link. :+1:
Meaning we can work it with io.js as well!

oh no you are going to make me look at another thing.  lol... after my build.  are you interested in getting my framework into omni aspnet generator???
Date: Thu, 19 Mar 2015 13:42:32 -0700
From<EMAIL_ADDRESS>To<EMAIL_ADDRESS>CC<EMAIL_ADDRESS>Subject: Re: [node-sass] Travis Build Error: libsass bindings not found. Try reinstalling node-sass? (#532)
@xtianus79, good to know and thanks for sharing the blog link.
Meaning we can work it with io.js as well!
—
Reply to this email directly or view it on GitHub.

FYI for those having this issue when using VS2015, you have to install the same version of node which VS is using (0.10.13 x32 currently). More info here: http://stackoverflow.com/questions/31301582/task-runner-explorer-cant-load-tasks/31304060#31304060

@JoshMcCullough, thanks for the info! But isn't it so that @madskristensen's blog post pointed out by @xtianus79  (http://blogs.msdn.com/b/webdev/archive/2015/03/19/customize-external-web-tools-in-visual-studio-2015.aspx) explains how user can change the default node.js (-like) runtimes (node.js/io.js/atom-shell etc.)? Which means you can install a latest (or your favourite) version of node.js or io.js and set VS2015 to use it for task-runner.

You should have your node engine and your node-sass binding compiled against the same C++ runtime library. You can use VS's built-in node or tell VS to use another engine, does not matter. Just use the same for all binary modules.

Cool, I'd LOVE to use the non-build-in version of node, and will check that link! Thanks.

This worked great, thanks @am11!

Is any of this worth adding to the troubleshooting guide?
On 11 Jul 2015 06:50, "Josh McCullough"<EMAIL_ADDRESS>wrote:

This worked great, thanks @am11 https://github.com/am11!
—
Reply to this email directly or view it on GitHub
https://github.com/sass/node-sass/issues/532#issuecomment-120520622.

Is any of this worth..

Implicitly yes.
Swell Story:
Given Sass editor (OOTB) support was first added in VS2013 (Update 3? or 2?), and mostly people who were using Sass with VS2013 had Web Essentials 2013 extension installed. WE2013 packs node.exe with CSS/JS superset compiler packages including node-sass and hence distill the version of node-sass binary (binding.dll->binding.node).
With VS2015, "node runtime" is a first class citizen of IDE. While MSBuild is responsible for building the backend code, Task Runner les user configure the front-end build system of their choice (Bower, Grunt, Gulp etc.) and build the front-end artifacts at build time. Therefore WE2015 dropped all the packaging and manifesting of node.js runtime & packages in favour of out-of-the-box task runner support and focuses on enhancing the editor functionality (preview window etc.). While other extensions like (https://github.com/madskristensen/NpmTaskRunner) extend on task runner capabilities to provide more node-y stuff.
With that said, it may confuse the user of VS2013, who upgraded to VS2015, if they install node-sass with system-installed node.exe or copy from other machine and then expect it to run via task runner (like coffeescript or less packages). Since (as we know and some users may not.. that) node-sass is based on native (C++) binary and the binary downloaded at install-time is specific to that version of node.exe, OS bitness/arch etc., it is not as "portable" as other npm packages.
So a short version of this story would probably save us from explaining it over and again. :wink:

I look forward to your pull request @am11 :D
On 11 Jul 2015 10:47, "Adeel Mujahid"<EMAIL_ADDRESS>wrote:

Is any of this worth..
Implicitly yes.
Swell Story:
Given Sass editor (OOTB) support was first added in VS2013 (Update 3? or
2?), and mostly people who were using Sass with VS2013 had Web Essentials
2013 extension installed. WE2013 packs node.exe with CSS/JS superset
compiler packages including node-sass and hence distill the version of
node-sass binary (binding.dll->binding.node).
With VS2015, "node runtime" is a first class citizen of IDE. While MSBuild
is responsible for building the backend code, Task Runner les user
configure the front-end build system of their choice (Bower, Grunt, Gulp
etc.) and build the front-end artifacts at build time. Therefore WE2015
dropped all the packaging and manifesting of node.js runtime & packages in
favour of out-of-the-box task runner support and focuses on enhancing the
editor functionality (preview window etc.). While other extensions like (
https://github.com/madskristensen/NpmTaskRunner) extend on task runner
capabilities to provide more node-y stuff.
With that said, it may confuse the user of VS2013, who upgraded to VS2015,
if they install node-sass with system-installed node.exe or copy from other
machine and then expect it to run via task runner (like coffeescript or
less packages). Since (as we know and some users may not.. that) node-sass
is based on native (C++) binary and the binary downloaded at install-time
is specific to that version of node.exe, OS bitness/arch etc., it is not as
"portable" as other npm packages.
So a short version of this story would probably save us from explaining it
over and again. [image: :wink:]
—
Reply to this email directly or view it on GitHub
https://github.com/sass/node-sass/issues/532#issuecomment-120556951.


Start adding unit tests for GCP actuator

#554
A few notes:

It's clear to me that K8s values e2e over unit tests. So we shouldn't be aiming for high coverage here, but instead testing critical/complex pieces of logic.
I can't add all such unit tests myself, so I'll need help from contributors.

cc @kubernetes/sig-cluster-lifecycle

This change is

/assign @jessicaochen

/assign @kris-nova

cc @kubernetes/sig-cluster-lifecycle-pr-reviews

/lgtm


HCRN can not run...

There may omit some codes for HCRN.

Thank you for your concern. We only include files for HCRN that we modified. I would suggest cloning the original HCRN repository (linked on our README), then replacing the equivalent files from the HCRN repository with the ones we include here.

OK，Thanks


Newlines should be normalized when checking if a task is done

The CSV reader & CSV writer might produce different newlines

Fixed by c80c297a767fc810c5abe7804b9b85466b08378f


First pass on the book

Changes proposed in this pull request:
Aviar are done, doing QC on allomancy. This took a long ass time to figure out how to do :sweat_smile:

need to set target branch to the 1.20 port branch

closing undesired duplicate of #122


Support OKEx API 2.0 And Huobi.pro API ?

@nntaoli would you be able to clarify, is there documentation to OKEx API 2.0?

@jheusser   this is  okex api 2.0 document , https://img.bafang.com/okex/html/okex_com.api.html


⚠ HDBits has degraded performance

In 82dde52, HDBits ($HDB) experienced degraded performance:

HTTP code: 200
Response time: 2311 ms

Resolved: HDBits performance has improved in deb5cd8 after 6 minutes.


Add dynamicProperty and dynamicType to DynamicData

Adding dynamicProperty and dynamicType to DynamicData per https://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/vmodl.DynamicData.html fixes the test_deserialization.rb failures:
Here is the change to the DynamicData properties:
vmodl["DynamicData"]["props"] = [
  {"name"=>"dynamicProperty", "is-optional"=>true, "is-array"=>true,  "version-id-ref"=>nil, "wsdl_type"=>"DynamicProperty"},
  {"name"=>"dynamicType",     "is-optional"=>true, "is-array"=>false, "version-id-ref"=>nil, "wsdl_type"=>"xsd:string"}
]

Does anything else need to be done to update the vmodl.db file?  I just did Marshal.load(), update the hash, and Marshal.dump()

I'm not sure. I've never dealt with the vmodl.db file before. Let's see how CI runs now and I'll check with others around here to find out about that. If that is the procedure to update it, 👍 to this all day long.

Awesome thanks, I ask because just adding those two hashes jumped the file size up from 741K to 1.3M
ruby-1.8.7 looks like it failed for a different reason I'll see if I can reproduce locally

Yeah, ruby-1.8.7 doesn't work with SimpleCov. I need to switch it out for RCov and use them based on RUBY_VERSION.

That jump doesn't seem too unlikely, but I'm still looking to find out how vmodl.db gets handled.

@agrare Don't worry about fixing the 1.8.7 issue. I'll handle that today.

This looks like it's fine and is working for me alright in a test environment and everything works in my local environment. 👍 Thank you for your contributions!

Thanks!


Store calibration coefficients as numpy binary files

Is your feature request related to a problem? Please describe.
File sizes of the current .csv files are large and can cause issues for package distribution.
Describe the solution you'd like
See if there are alternatives such as .npy or .npz
Describe alternatives you've considered
N/A
Additional context
N/A

Like this:
import numpy as np np.savez('file.npz', satobj.spectral_coeffs) np.load('file.npz')['arr_0']

The coefficients were replaced with .npz files in the most recent commit to the v2 branch: https://github.com/NTNU-SmallSat-Lab/hypso-package/commit/88ed3e62e072ca14f8d882a122b2a7433ab29884


Add documentation on ISO stage attribute that some stages are handled by ISO/CS, not the author

We should also give some more information for MN ISO on stages that are handled by ISO/CS, not the authors.
The last stage the author will handle is DIS (or DTR, DTS, DAM depending on doctype).
The F-stages, like FDIS and FDAM, and subsequent ones (like PRF, Pub) are created by ISO/CS.
Functionality wise, we want to retain the ability to use those codes (e.g. for mirroring and tracking purposes), but just let the authors know in a normal submission process, those codes are not used.

Since I don't know the inner workings of ISO, and you do: is that list exhaustive?


Missing "x located and EMP'd y" message and systems checked embed

When you defeated a bounty it used to give a somewhat lore-friendly message like " located and EMP'd  who is being detained by security forces" or something. Let's bring that back!
An example with no message:
https://discord.com/channels/711548456019296289/721311036891725856/935114699807260673

Also missing the embed that shows how many systems everyone checked and how much money/XP they got. Changing this to bug


remove additional artifacts

archiveArtifacts removed because they are already defined here https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/Jenkinsfile#L102 and her https://github.com/kiegroup/droolsjbpm-build-bootstrap/blob/master/Jenkinsfile#L105
related with https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/1383

@Ginxo so I understand that additionalArtifacts will only have it's "values" in the new_pr_job.groovy. All other new jobs wwill have the value additionalArtifacts [ ] - so empty.

@mbiarnes indeed because they are already defined in Jenkinsfile and the need to be splitted in several archiveArtifacts executions


Fix

Hey @eric-z-wang and @snferguson. Just to clarify this should be this fixed in the latest python version. Seems like it was resolved when you pulled in main. Let me know if you're still having any issues.


some jpg images are not opening

Not all jpg format images, but some are not opening up in manga reader.

I uploaded the folder which is not opening for me in the application.
This is the first time I encountered this issue in the application.
To make sure, I checked again with another manga that is in jpg and it works fine.

This is what happens,

Please check the below folder that has the images.
#1 - Episode 1.zip

The image element excepts a "link/url" and "#" is used to show fragment, for example, https://github.com/mienaiyami/react-ts-offline-manga-reader#features, notice #features at the end.


Trojan detected (<IP_ADDRESS> only)

Hello,
A trojan is reported in your last jar <IP_ADDRESS>
https://www.virustotal.com/gui/file/65aceaf78f60ba4c11149c422b28961a58c4d56be5ad2dd1da7e9ab468ef45e7

False positive, as is typical when you scan something with 50 engines. Never heard of "Rising".

Indeed. https://www.virustotal.com/gui/file/65aceaf78f60ba4c11149c422b28961a58c4d56be5ad2dd1da7e9ab468ef45e7 shows nothing detected.


[Task]: Add newline after license header in message files

What needs to happen?
weblate gets confused if there is no newline between the header and the first translation.
It will see the header as a comment attached to the first line, if this line then changes or moves the header will no longer be at the top of the file
Issue Priority
Priority: 2
Issue Component
Component: Translations

.take-issue


Infer Parquet JSON Logical and Converted Type as UTF-8

Which issue does this PR close?

Relates to #3373
Rationale for this change

JSON data must be UTF-8, we can therefore safely infer json fields as containing UTF8 data. This leads to a superior experience as BinaryArray cannot be output to non-binary formats such as CSV and JSON.
What changes are included in this PR?

Are there any user-facing changes?

There is a draft PR in https://github.com/apache/arrow/pull/13901 that adds a canonical arrow extension type for JSON data backed by UTF-8 arrays.

Seems reasonable to me -- I think we ought to have a test for it, however, to avoid regressions in the future

There is a test?


Allow livestreams in search results.

No idea if what I did would work since I never used Java before and didn't test or check it. Either way, I would like it if live streams weren't filtered out.

Refs #107

Hmm yes, doesn't work. But still, live streams not being filtered out would still be appreciated.

Would only be acceptable if this were an option that can be enabled.

Would only be acceptable if this were an option that can be enabled.

Would only be acceptable if this were an option that can be enabled.

Wouldn't hurt to add the option

Would only be acceptable if this were an option that can be enabled.

Wouldn't hurt to add the option


Support caching virtualenvs created when using ExecutionMode.VIRTUALENV

As of Cosmos 1.2, when using ExecutionMode.VIRTUALENV, each task will create a new Python virtual environment, in a temporary directory:
https://github.com/astronomer/astronomer-cosmos/blob/a433f15d6fd20f5fd713268040eba09727db4a2c/cosmos/operators/virtualenv.py#L68
This can cause delays, as discussed in the Slack thread:
https://apache-airflow.slack.com/archives/C059CC42E9W/p1697614400289939
This could be improved, assuming the Airflow worker node is reused to run multiple tasks.
Proposal
Persist the virtual environment directory if users set the configuration: ExecutionConfig.virtualenv_path.

As discussed with @tatiana I'd be happy to take a first stab at this :)

Thank you very much for taking the lead on this, @LennartKloppenburg ! Please, let us know if you'd like any support

Thinking about whether it'd make sense to add a clean-up callback to delete the virtual env that should be executed after the whole DAG has completed?
Or should we defer this responsibility/flexibility to the end-user?

More things to consider:

It could be useful to also centralize and cache the installation of dbt deps, as this is currently still happening in every task with this PR. Implementing this too would invalidate the install_deps flag on the operator level (on DbtLocalBaseOperator for instance) and make more sense on the ExecutionConfig instead, at least when using using VirtualEnv as ExecutionMode.

If we let an operator create a virtual env and cache it, it can cause concurrency issues with other operators simultaneously doing the same thing. My changes work when starting with 1 in isolation and then running the rest...
Perhaps the most elegant solution would be to add a "set-up" operator at the start of a VirtualEnv-based DAG that sets up the env, installs python requirements, installs dbt deps and everything, and then another one that tears it down at the end. That would take care of a lot of the complexity we'd otherwise end up implementing on the operator level.

The current PR would also split the operator's responsibility into "do whatever DBT thing it needs to do" and "optionally set up a virtual env if necessary" and that feels like an anti-pattern.

@LennartKloppenburg, we discussed this last week, and I'll add some thoughts here as well:
The challenge with having the setup in a separate operator is that due to the distributed nature of Airflow, there is no guarantee that this operator would be run in the same nodes running the other dbt/Cosmos tasks.
And if users are running Airflow using the Airflow K8s executor, a new pod is created each time an Airflow worker node picks up a task - so it is necessary to have it at an operator level.
If the setup was in some remote service, we could try to leverage the Airflow 2.7 DAG-level setup/teardown:
https://airflow.apache.org/docs/apache-airflow/stable/howto/setup-and-teardown.html
If Airflow had a worker-node level setup/tear down, it would be optimal for our use case. Still, let's say different tasks had different dependencies - we may still have some concurrency challenges if we use asynchronous operators (it's been discussed to have Cosmos supporting dbt Cloud, for instance, and in that case, we'd be leveraging Airflow deferrable operators).
For this reason, I believe we'll need to come up with some solution to the concurrency issue at a task level, for now. More thoughts on the PR itself.

Yep, you're totally right! Sorry for duplicating the question here, but your info is excellent as a paper-trail so let's leave it :D


I see. The thing I liked the best about the app was that the black theme was 100% AMOLED black. Too bad.
Good luck!
Dale Forrest
https://sacredpeak.ink
-------- Original Message --------
On 11/22/24 08:22, Mrnofish  wrote:

The black theme is now almost identical to the dark one. The only UI element that is still displaying as expected is the location bar, where the background is still black. Btw the row shading that is
DuckDuckGo removed one tracker.  More
Report Spam
The black theme is now almost identical to the dark one.
The only UI element that is still displaying as expected is the location bar, where the background is still black.
Btw the row shading that is used in the hourly view is quite handy, it would be cool to have an option for something similar in the black theme, too.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

@wynteryyc it is a bug. Will bring it back. What OS (android/ios) ? what version?

I attached a screenshot with the version from droifify (fdroid).
thank you!
Dale Forrest
https://sacredpeak.ink
-------- Original Message --------
On 11/25/24 01:26, farfromrefuge  wrote:

@wynteryyc it is a bug. Will bring it back. What OS (android/ios) ? what version? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Mes
DuckDuckGo removed one tracker.   Will bring it back. What OS (android/ios) ? what version?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

thank you!

@farfromrefug

BTW the row shading that is used in the hourly view is quite handy, it would be cool to have an option for something similar in the black theme, too.

Any chance?
Perhaps the backgrounds of the hourly panels could alternate between full black and a dark grey, for increased readability while maintaining the substantial blackness of the theme.


Validating a relationship

Hi there me again,
I'm kinda stuck with a relationship validation problem.
Is there any way to validate two foreign keys of a pivot table?
For example, let's say that you have subjects and users.

A user can have multiple subjects and a subject can have multiple users.
A user can't assign himself to a subject twice.

But, how do I add a validation that checks if the user isn't already assigned to the same subject?
I want it to throw an error if the user is already assigned to the same subject (not a 500 error).
By the way, I want a validation on this endpoint:

http://localhost:8000/v1/users/1/relationships/subjects

I really appreciate the help, thank you!
Sincerly,
Stefan

Hi!
Thanks for the question, but this isn't really a Laravel JSON API question. As we use Laravel's validation feature, you need to work out how you would do it with Laravel's validators - and then once you've done that you can then use it for your JSON API validators.
It sounds like what you need to use is Laravel's exists and unique rules, that inspect the database:
https://laravel.com/docs/5.8/validation#rule-exists
https://laravel.com/docs/5.8/validation#rule-unique
If you can't do what you need to do with either of those, then you'll need to write your own validation rule. The docs for that are here:
https://laravel.com/docs/5.8/validation#custom-validation-rules
For the relationship endpoints, how the data is passed to your validator is described here:
https://laravel-json-api.readthedocs.io/en/latest/basics/validators/#modify-relationship-validation
I'm going to close this issue as I think the above gives the info you need to tackle the problem, but feel free to re-open if you feel that there's a specific problem validating relationships in this package!


Errors from synopsis

Hi
I have tried to run the README synopsis, but getting multiple errors.
The first one is
Type 'Result' is not declared
Sorry, without that working, I cannot really work out what is going on ... but would like to use the module

I just updated the README, sorry, that was a typo. This package is an implementation of a monad, basically a computation with a side-effect, that is hidden.

OK thanks!! - but now there is another error ;-)
Two terms in a row across lines (missing semicolon or comma?)
------> t.error('Bad value!') if $value eq 'bad'⏏
expecting any of:
infix
infix stopper

Another typo, missing semicolon. I probably should have written this synopsis in an editor instead of on Github :P

@librasteve Please let me know if there is anything else I can do to close this issue. Thanks!

sorry - yes that's all good - thanks!


Typescript error when using multiline theme override on MuiListItemText

I want to override the default styling of MuiListItemText when using multiline, as documented but I causes a typescript error.
I suppose this is because multiline is missing in ListItemTextClassKey.
Want me to create a pull request for it?

[x] This is not a v0.x issue.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior 🤔
No error, since it is valid according to the docs.
Current Behavior 😯
Typescript error:
Object literal may only specify known properties, and 'multiline' does not exist in type 'Partial<Record<ListItemTextClassKey, CSSProperties>>'.ts(2322)

Context 🔦

I want to change the margins since they are slightly too large for my use case.
Your Environment 🌎

tsconfig
{
  "compilerOptions": {
    "target": "es5",
    "lib": [
      "dom",
      "dom.iterable",
      "esnext"
    ],
    "allowJs": true,
    "skipLibCheck": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "preserve"
  },
  "include": [
    "src"
  ]
}

Tech
Version

Material-UI
v4.0.0-beta.0

React
16.8.3

TypeScript
3.4.5

Looks like the ListItemText typings need to be updated.
export type ListItemTextClassKey =
  | 'root'
  | 'inset'
  | 'dense'
  | 'primary'
  | 'secondary'
+ | 'multiline';
- | 'textDense';

Want to give it a go? :)

Are you planning to PR this? @joshwooding

@alxsnchez I’ve marked it as a good first issue so someone else is free to pick it up. I’m personally not planning to create a PR.

Created a PR for this: #15822

Closed by #15822


chore: release main

:robot: I have created a release beep boop
redlog: 1.5.1
1.5.1 (2024-05-11)
Bug Fixes

update component name (1924fa0)

internal/logtheme: 1.2.0
1.2.0 (2024-05-11)
Features

catppuccin: bump version (c7a7624)
catppuccin: bump version (1ea6b99)
catppuccin: bump version (ad1a9fb)
catppuccin: bump version (db94821)
release 1.2 (c2ec968)

Bug Fixes

add gallery section (4da21ab)
new version with license (5809ad9)
require slog (40e9556)

internal/themes: 1.2.0
1.2.0 (2024-05-11)
Features

catppuccin: bump version (c7a7624)
catppuccin: bump version (1ea6b99)
catppuccin: bump version (ad1a9fb)
catppuccin: bump version (db94821)
release 1.2 (c2ec968)

Bug Fixes

add gallery section (4da21ab)
new version with license (5809ad9)
require slog (40e9556)
versions (4a2abfb)

pkg/catppuccin: 1.6.0
1.6.0 (2024-05-11)
Features

add Default to catppuccin (f81efbd)
catppuccin (3846146)
catppuccin: bump version (c7a7624)
catppuccin: bump version (1ea6b99)
catppuccin: bump version (ad1a9fb)
catppuccin: bump version (db94821)
release 1.2 (c2ec968)

Bug Fixes

add gallery section (4da21ab)
create hex color (388c271)
image for catppuccin (f21e2d9)
image sizes (b1342ae)
new version with license (5809ad9)
require slog (40e9556)
touch catp (28082bb)
versions (4a2abfb)

This PR was generated with Release Please. See documentation.

:rocket: This description was created by Ellipsis for commit 2fc025a13bdb22d25d881e50112ff2b33aed0a9b

Summary:
This PR updates versions and addresses various bug fixes and feature enhancements across the project.
Key points:

Version bump for redlog to 1.5.1
Version bump for internal/logtheme to 1.2.0
Version bump for internal/themes to 1.2.0
Version bump for pkg/catppuccin to 1.6.0
Bug fixes and feature enhancements across multiple components

Generated with :heart: by ellipsis.dev

:robot: Release is at https://github.com/op/redlog/releases/tag/redlog/v1.5.1 :sunflower:

:robot: Release is at https://github.com/op/redlog/releases/tag/internal/logtheme/v1.2.0 :sunflower:

:robot: Release is at https://github.com/op/redlog/releases/tag/internal/themes/v1.2.0 :sunflower:

:robot: Release is at https://github.com/op/redlog/releases/tag/pkg/catppuccin/v1.6.0 :sunflower:


Remove old “new in” statements

While old {% addedin %} statements were removed in f2b5c698fffd728b2c4200fdb2bc71ce5491cd75, manual references to old versions (including in code blocks) were not cleaned up. This PR does that, and fixes a place where the missing old {% addedin %} was actively confusing (https://www.11ty.dev/docs/collections/#return-values)

Awesome, thank you!


Update setup.py

Type
enhancement

Description

Added a debug print statement (print("Aaa")) to setup.py for enhanced logging during package setup.

Changes walkthrough
Relevant filesEnhancement

setup.pyAdd Debug Print Statement to setup.py

setup.py

Added a print statement at the beginning of the file.

+1/-0

✨ PR-Agent usage:
Comment /help on the PR to get a list of all available PR-Agent tools and their descriptions

Preparing review...

Persistent review updated to latest commit https://github.com/Codium-ai/pr-agent/commit/26606a502ed97a1641491dac2cc8db85de2ec5de

Preparing review...

Persistent review updated to latest commit https://github.com/Codium-ai/pr-agent/commit/26606a502ed97a1641491dac2cc8db85de2ec5de


Macho loader omitting indirect symbols since 10.3

Describe the bug
Between Ghidra release 10.2.3 and 10.3 there was a change to how the MachoProgramBuilder loaded some symbols. Commit a0473e8 modified symbol parsing by removing the function processIndirectSymbols. Due to this some symbols are now omitted during loading of certain machos. Where I noticed this is in machos with the following segments and sections (__TEXT_EXEC,__auth_stubs), (__DATA_CONST,__auth_got), and (__DATA_CONST,__got). From the commit message it appears that these symbols were thought to be duplicates and that does appear to be the case as a symbol still exists in the EXTERNAL memory block. However, there are xrefs to the symbols which were omitted and so not applying the symbol name in these other areas results in a loss of context.
To Reproduce
Example machos can be found in the arm64e architecture type on macOS systems (e.g. /bin/ls with the indirect symbols listed by otool -Iv). Loading the macho in Ghidra 10.2.3 and also in 10.3 (or later) will show that the indirect symbols don't appear anymore starting in 10.3.
Expected behavior
The indirect symbol names are applied.
Environment (please complete the following information):

OS: macOS 13.4
Java Version: 17.0
Ghidra Version: First seen in 10.3 and still seen in the latest 10.3.2
Ghidra Origin: official GitHub distro

These were intentionally removed because if analysis is working correctly, things like the GOT should inherit labels that ultimately trace back to the thunks in the EXTERNAL block.  Is this not happening after analysis?
For these indirect symbols we were using the section name as the namespace which caused problems with the demangler, since that only operates on global symbols.

When I import /bin/ls from my macOS 13.4.1, i am getting Unknown dyld info bind opcode d0 which seems to be messing things up.  Are you seeing that too?

I am not seeing any labels added at the indirect symbol locations after the standard default auto analysis for the /bin/ls example case. I am not getting the error you encountered on load. I used batch import and then opened the AARCH64 version.

Ok, I will investigate further.

Yes, checking with Ghidra 10.3.2 and using /bin/ls from a macOS 13.5 system I see the same thing at this address after analysis. The operands field of "LAB_c009000000000007" is in red.

Ok, thanks for checking.  This should be fixed in master now.


Re-introduction of improved CSS selectors specificity fix

Re-introduction of improved CSS selectors specificity fix reverted in 0a0b580981bcd7ba6af33161993355bed99056cd
Now allows .super-class to override :host's styling
Fixes #3326
@azakus, @sorvell, @rictic for review

Fixed via #3413. Thanks!


[Pin Me] FastUI Discussion Slack Channel

FYI, there's a slack channel for FastUI Discussion here:
https://pydanticlogfire.slack.com/archives/C0720M7D31S

@sydney-runkle, I was chatting with @samuelcolvin and we thought it would be a good idea to create a pinned issue to alert active contributors to the presence of this discussion slack channel.
(Feel free to pin this issue or create a new one that a pydantic team member can edit/manage)

I would love to join but I don't have a<EMAIL_ADDRESS>account... An invitation could be helpfull.

@hasansezertasan I didn’t need anything special when I signed up from the link on this page: https://docs.pydantic.dev/logfire/help/

@hasansezertasan I didn’t need anything special when I signed up from the link on this page: https://docs.pydantic.dev/logfire/help/

Thank you for pointing out this link. I'm in!

Closing this issue because the link added to the readme in https://github.com/pydantic/FastUI/pull/302


exec: python: not found

LocalAI version:
latest-aio-cpu/latest-cpu (tested with both

Environment, CPU architecture, OS, and Version:
Linux Desktop-j42f 6.8.0-44-generic #44-Ubuntu SMP PREEMPT_DYNAMIC Tue Aug 13 13:35:26 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Describe the bug
Requests to the embeddings endpoint cause a HTTP 500 error with the following error message when used with a custom model.
{"error":{"code":500,"message":"grpc service not ready","type":""}}
The error seems to be caused by a missing python install as indicated by the following debug output:
8:12PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:38153): stderr /build/backend/python/sentencetransformers/../common/libbackend.sh: line 180: exec: python: not found

To Reproduce

Setup
Docker hosted LocalAI instanz with the following docker file and model configuration

Dockerfile
FROM localai/localai:latest-cpu
RUN apt-get update && apt-get install -y wget  &&
wget -O /build/models/pytorch_model.bin https://huggingface.co/medicalai/ClinicalBERT/resolve/main/pytorch_model.bin
ENV DEBUG=true
COPY models/* /build/models/
Modelconfiguration
name: clinicalbert
backend: sentencetransformers
embeddings: true
parameters:
model: pytorch_model.bin

Build and launch dockercontainer without any further options

Request an embedding from the mebedding endpoint using model=clinicalbert

Expected behavior
A correct embedding should be returned

Logs
10:16PM DBG Request received: {"model":"clinicalbert","language":"","translate":false,"n":0,"top_p":null,"top_k":null,"temperature":null,"max_tokens":null,"echo":false,"batch":0,"ignore_eos":false,"repeat_penalty":0,"repeat_last_n":0,"n_keep":0,"frequency_penalty":0,"presence_penalty":0,"tfz":null,"typical_p":null,"seed":null,"negative_prompt":"","rope_freq_base":0,"rope_freq_scale":0,"negative_prompt_scale":0,"use_fast_tokenizer":false,"clip_skip":0,"tokenizer":"","file":"","size":"","prompt":null,"instruction":"","input":"person with fever","stop":null,"messages":null,"functions":null,"function_call":null,"stream":false,"mode":0,"step":0,"grammar":"","grammar_json_functions":null,"backend":"","model_base_name":""}
10:16PM DBG guessDefaultsFromFile: not a GGUF file
10:16PM DBG Parameter Config: &{PredictionOptions:{Model:pytorch_model.bin Language: Translate:false N:0 TopP:0xc0005fe678 TopK:0xc0005fe680 Temperature:0xc0005fe688 Maxtokens:0xc0005fe6c8 Echo:false Batch:0 IgnoreEOS:false RepeatPenalty:0 RepeatLastN:0 Keep:0 FrequencyPenalty:0 PresencePenalty:0 TFZ:0xc0005fe6c0 TypicalP:0xc0005fe6b8 Seed:0xc0005fe6f0 NegativePrompt: RopeFreqBase:0 RopeFreqScale:0 NegativePromptScale:0 UseFastTokenizer:false ClipSkip:0 Tokenizer:} Name:clinicalbert F16:0xc0005fe670 Threads:0xc0005fe658 Debug:0xc0005fe8d0 Roles:map[] Embeddings:0xc0005fe4e0 Backend:sentencetransformers TemplateConfig:{Chat: ChatMessage: Completion: Edit: Functions: UseTokenizerTemplate:false JoinChatMessagesByCharacter:} PromptStrings:[] InputStrings:[person with fever] InputToken:[] functionCallString: functionCallNameString: ResponseFormat: ResponseFormatMap:map[] FunctionsConfig:{DisableNoAction:false GrammarConfig:{ParallelCalls:false DisableParallelNewLines:false MixedMode:false NoMixedFreeString:false NoGrammar:false Prefix: ExpectStringsAfterJSON:false PropOrder: SchemaType:} NoActionFunctionName: NoActionDescriptionName: ResponseRegex:[] JSONRegexMatch:[] ReplaceFunctionResults:[] ReplaceLLMResult:[] CaptureLLMResult:[] FunctionNameKey: FunctionArgumentsKey:} FeatureFlag:map[] LLMConfig:{SystemPrompt: TensorSplit: MainGPU: RMSNormEps:0 NGQA:0 PromptCachePath: PromptCacheAll:false PromptCacheRO:false MirostatETA:0xc0005fe6b0 MirostatTAU:0xc0005fe698 Mirostat:0xc0005fe690 NGPULayers:0xc0005fe6d0 MMap:0xc0005fe6d8 MMlock:0xc0005fe6d9 LowVRAM:0xc0005fe6d9 Grammar: StopWords:[] Cutstrings:[] TrimSpace:[] TrimSuffix:[] ContextSize:0xc0005fe650 NUMA:false LoraAdapter: LoraBase: LoraScale:0 NoMulMatQ:false DraftModel: NDraft:0 Quantization: GPUMemoryUtilization:0 TrustRemoteCode:false EnforceEager:false SwapSpace:0 MaxModelLen:0 TensorParallelSize:0 MMProj: FlashAttention:false NoKVOffloading:false RopeScaling: ModelType: YarnExtFactor:0 YarnAttnFactor:0 YarnBetaFast:0 YarnBetaSlow:0} AutoGPTQ:{ModelBaseName: Device: Triton:false UseFastTokenizer:false} Diffusers:{CUDA:false PipelineType: SchedulerType: EnableParameters: CFGScale:0 IMG2IMG:false ClipSkip:0 ClipModel: ClipSubFolder: ControlNet:} Step:0 GRPC:{Attempts:0 AttemptsSleepTime:0} TTSConfig:{Voice: VallE:{AudioPath:}} CUDA:false DownloadFiles:[] Description: Usage:}
10:16PM INF Loading model 'pytorch_model.bin' with backend sentencetransformers
10:16PM DBG Loading model in memory from file: /build/models/pytorch_model.bin
10:16PM DBG Loading Model pytorch_model.bin with gRPC (file: /build/models/pytorch_model.bin) (backend: sentencetransformers): {backendString:sentencetransformers model:pytorch_model.bin threads:12 assetDir:/tmp/localai/backend_data context:{emptyCtx:{}} gRPCOptions:0xc0002d7208 externalBackends:map[autogptq:/build/backend/python/autogptq/run.sh bark:/build/backend/python/bark/run.sh coqui:/build/backend/python/coqui/run.sh diffusers:/build/backend/python/diffusers/run.sh exllama:/build/backend/python/exllama/run.sh exllama2:/build/backend/python/exllama2/run.sh huggingface-embeddings:/build/backend/python/sentencetransformers/run.sh mamba:/build/backend/python/mamba/run.sh openvoice:/build/backend/python/openvoice/run.sh parler-tts:/build/backend/python/parler-tts/run.sh rerankers:/build/backend/python/rerankers/run.sh sentencetransformers:/build/backend/python/sentencetransformers/run.sh transformers:/build/backend/python/transformers/run.sh transformers-musicgen:/build/backend/python/transformers-musicgen/run.sh vall-e-x:/build/backend/python/vall-e-x/run.sh vllm:/build/backend/python/vllm/run.sh] grpcAttempts:20 grpcAttemptsDelay:2 singleActiveBackend:false parallelRequests:false}
10:16PM DBG Loading external backend: /build/backend/python/sentencetransformers/run.sh
10:16PM DBG Loading GRPC Process: /build/backend/python/sentencetransformers/run.sh
10:16PM DBG GRPC Service for pytorch_model.bin will be running at: '<IP_ADDRESS>:40125'
10:16PM DBG GRPC Service state dir: /tmp/go-processmanager2441360389
10:16PM DBG GRPC Service Started
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stdout Initializing libbackend for build
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stderr /build/backend/python/sentencetransformers/../common/libbackend.sh: line 91: uv: command not found
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stdout virtualenv created
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stdout virtualenv activated
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stdout activated virtualenv has been ensured
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stderr /build/backend/python/sentencetransformers/../common/libbackend.sh: line 97: /build/backend/python/sentencetransformers/venv/bin/activate: No such file or directory
10:16PM DBG GRPC(pytorch_model.bin-<IP_ADDRESS>:40125): stderr /build/backend/python/sentencetransformers/../common/libbackend.sh: line 180: exec: python: not found
10:17PM ERR failed starting/connecting to the gRPC service error="rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:40125: connect: connection refused""
10:17PM DBG GRPC Service NOT ready
10:17PM ERR Server error error="grpc service not ready" ip=<IP_ADDRESS> latency=40.428444674s method=POST status=500 url=/v1/embeddings

Additional context

CPU images don't have Python installed

Thanks for the information. If the CPU images don't have python by design,
what is the recommended way to run models like the clinicalbert project on
a server only equipped with CPU?
Is one of the other backends also capable of using these models and doesn't
require python?
On Tue, Sep 17, 2024, 00:37 Alexander Izotov @.***>
wrote:

CPU images don't have Python installed. It's by design
—
Reply to this email directly, view it on GitHub
https://github.com/mudler/LocalAI/issues/3583#issuecomment-2354150083,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AN2GBNVMHOZEORV3MG5UD3DZW5MSTAVCNFSM6AAAAABOKG5H7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJUGE2TAMBYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Thanks for the information. If the CPU images don't have python by design, what is the recommended way to run models like the clinicalbert project on a server only equipped with CPU? Is one of the other backends also capable of using these models and doesn't require python?
…
On Tue, Sep 17, 2024, 00:37 Alexander Izotov @.> wrote: CPU images don't have Python installed. It's by design — Reply to this email directly, view it on GitHub <#3583 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AN2GBNVMHOZEORV3MG5UD3DZW5MSTAVCNFSM6AAAAABOKG5H7CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNJUGE2TAMBYGM . You are receiving this because you authored the thread.Message ID: @.>

You need to add Python and installation of chosen backend, in your case sentencetransformers (https://github.com/mudler/LocalAI/tree/master/backend/python/sentencetransformers), to your Dockerfile. There is install.sh which sets up venv and installs requirements.

Unfortunately i still cannot make it work
Once python, uv as well as the sentencetransformers backend are installed (using the backend install script) its fails because of missing the module backend_pb2
It looks like this is a dependency on another backend but i couldn't figure out which backends i have to build additionally.

Try this:
FROM localai/localai:latest-cpu

ENV CONDA_DIR /opt/conda
RUN curl https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh -o ~/miniconda.sh && \
    /bin/bash ~/miniconda.sh -b -p /opt/conda

ENV PATH $CONDA_DIR/bin:$PATH

RUN pip install grpcio-tools==1.66.0 \
    uv

RUN make -C backend/python/sentencetransformers protogen \
    && make -C backend/python/sentencetransformers
    ```

Also specifying local file doesn't seem to work, SentenceTransformer backend receives model_name like this: sentence-transformers/pytorch_model.bin and throws an error:

ERR Server error error="could not load model (no success): Unexpected err=OSError("sentence-transformers/pytorch_model.bin is not a local folder and is not a valid model identifier listed on 'https://huggingface.co/models'\nIf this is a private repository, make sure to pass a token having permission to this repo either by logging in with huggingface-cli login or by passing token=<your_token>"), type(err)=<class 'OSError'>" ip=<IP_ADDRESS> latency=6.441716341s method=POST status=500 url=/embeddings

So for now yaml file should look like this:

name: clinicalbert
backend: sentencetransformers
embeddings: true
parameters:
model: medicalai/ClinicalBERT

another way would be to use the gpu images which comes with python installed. See also: https://localai.io/basics/container/#standard-container-images

Thanks for the help, the gpu images then worked. I had assumed them to be only working for systems with gpus.
The issue pointed out by @Nyralei does occur with the local model, however the modified yaml also doesnt seem to work for me. Is there any incompatibility with the sentence-transformer backend that causes the following message:
DBG GRPC(medicalai/ClinicalBERT-<IP_ADDRESS>:36351): stderr No sentence-transformers model found with name medicalai/ClinicalBERT. Creating a new one with mean pooling.
(I'm generally not that experienced with this so already thanks a lot for any help)

DBG GRPC(medicalai/ClinicalBERT-<IP_ADDRESS>:36351): stderr No sentence-transformers model found with name medicalai/ClinicalBERT. Creating a new one with mean pooling.

This message appears when sentence-transformers starts to download the model. Is there network activity? Did it create the directory with model in models path?


hotfix(styles): 13682 - change styles

remove couple of arbitrary numbers and added styles for opened intercom logo (it's different element) to match design
anyone can approve that

Codecov Report

Merging #405 (b5b6752) into main (9afe870) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #405   +/-   ##
=======================================
  Coverage   11.77%   11.77%
=======================================
  Files         544      544
  Lines       38841    38841
  Branches     1168     1168
=======================================
  Hits         4572     4572
  Misses      33824    33824
  Partials      445      445


Create fieldset and legend CSS-only component

Create CSS-only component and add example in the card-control stories:
https://www.figma.com/file/xZ0IW0MJO0vnFicmrHiKaY/Components-Post?type=design&node-id=22630-6660&mode=design&t=xWWBsj2nb4x41dUt-0

Already developed and released.


Hosted server

Added UIAlertController to ask for base url for the hosted server.
Added option in the alert to deploy hosted server on heroku directly from the app.
Added a new option in SettingsViewController to change the server url.

@Eliottiosdevs Can you review this pr?


require.js conflict

UPDATE: Read the resolution below

The issue is reproduced here:
http://www.candid.io/joefresh.html
The JS error is referencing this doc: http://requirejs.org/docs/errors.html#mismatch
We've done a number of integrations with our script (http://api.getcandid.com/scripts/widget.js) which references keen 3.0.4... this is the first conflict we've seen.
Any ideas would be appreciated.

This has resurfaced in v3.4.0-rc.

@elliottshort thanks for reporting - would you mind sharing a bit more about your setup? Which version of RequireJS is causing the issue, and how are you loading/configuring the library? Thanks for your help!

Also affecting my project with 3.4.0
require.config( {
    'baseUrl' : 'app',
    'paths' : {
        'keen' : "../lib/keen-js/dist/keen"
    },
   ...
} );

'use strict';

require( [ "angularAMD", "keen" ], function( angularAmd, Keen )
{

    angularAmd.service( 'AnalyticsService', function()
    {
        return Keen;
    } );

} );

I immediately load it into my AngularAMD project. If I refresh without clearing cache, everything then loads fine. If I clear cache, it dies.

@centaur2048 sorry to hear about this– which version of requirejs are you using?

Requirejs version: 2.1.16

No resolution.
I've tried loading this on the page using script tags and directly using RequireJs configuration. Neither has worked.
I am at the point where I want to begin using your chart libraries; so, would be nice to resolve this. I just pulled 3.4.1-RC4 and the issue still persists.

@centaur2048 Google Charts shipped a UMD/RequireJS bug that has been causing intermittent and difficult-to-debug crashes, so we just recently shipped a version of keen-js that omits GC entirely. Please give this file a try and let me know how it goes:
https://d26b395fwzu5fz.cloudfront.net/3.4.1-rc4/keen-c3.js

Excellent! Tested with both script tag and using RequireJs and the issue appears to be resolved.

Closing now– this issue has stood open for a long time as a point of reference for others struggling with the issue, but now our v3 docs should properly highlight the issue. Thanks again @nariman-haghighi @agrapsas for the help here!


Filamant usage

When i have added the filamant and the spool grams it will use more then i putted in.
Like the filamant roll was 1kg, used over 750 grams, so left 250 grams, and putted the weight with the spool holder in its ways 1257 grams. But when i print like an yxz cube of 4.8 grams it thinks it take all of the 250 grams left. Idontknow if i am doing something wrong.

https://github.com/Donkie/Spoolman/assets/147885183/5ce80261-ab61-4e47-96bd-c809958fae4b
https://github.com/Donkie/Spoolman/assets/147885183/c25aa8a3-18cc-4890-b975-37f7703d7603

What is your density and diameter set to in the filament's settings?

Density is 1.24 and diameter 1.75

Isseu is fixed, resinstalled the software now its working good! Thanks @Donkie


在vm中执行init 0或者关机操作的时候 系统资源无法及时回收

前提系统资源使用较满
1 已经使用的vm 以linux举例 执行init 0操作
2 vm 正常关机
3 约3秒后 UI中 vm状态 显示stoped
4 在UI中 对这个关闭的vm 执行 Start 操作 会报资源不足
等待时间 可能在几分钟之后 有一定几率  无法启动vm
临时解决方案  在host页面将主机 reconnect 后，正常启动关闭的vm

Thanks for reporting bug @snailyang . From QQ discussion, when VM starting failed, it might report:  No enough resource.

althrough vm is power off, but zstack does not it. zstack think vm is stopped but not destroyed, so resource is keeped.
In case, if vm restart again, that will cause resource race condition.
so my opinion is destroy the vm manually.

We will fix it in 1.0. ZStack dynamically monitor vm status and sync to
database.
On Fri, Nov 13, 2015 at 4:23 PM, RyuZen<EMAIL_ADDRESS>wrote:

althrough vm is power off, but zstack does not it. zstack think vm is
stopped but not destroyed, so resource is keeped.
In case, if vm restart again, that will cause resource race condition.
so my opinion is destroy the vm manually.
—
Reply to this email directly or view it on GitHub
https://github.com/zstackorg/zstack/issues/147#issuecomment-156360301.

--
Yongkang You

fixed in upstream


feat: Show "more button" disabled instead of hiding it

Relates to DHIS2-6986.
Changes include:

Making "show more" button disabled instead of hiding it when user fully expands control bar
Updating button styles

Can I get a screenshot please? :)

@cooper-joe sure:

you can also test the app on netlify:
https://deploy-preview-323--dhis2-dashboards.netlify.com/


Suggested change in DYLD_LIBRARY_PATH

DYLD_LIBRARY_PATH is set to "$PIPER_ROOT_FOLDER/piper-phonemize-master/install/lib"
However, the folder name should be "piper-phonemize" i.e. without the master. I manually changed it in .zprofile and now its working. Please check if this is replicable in other systems as well.

corrected as per your suggestions, I have also made sure that git clones the piper-phonemize into piper-phonemize folder and not in piper-phonemize-master. Thanks you!


Refactor alertsManager.ts

This is a preliminar refactor of alertsManager.ts in order to unify how Alerts API is being used from the UI.
We need to upgrade to Alerts 0.4.x and that has changes on the ui-services, but before to upgrade I think is good trying to simplify and use a consistent way to create triggers and fetch alerts.
There are some parts commented in datasources code as it will be simplify with 0.4.x when we can modify conditions in a single call.
@mtho11 and @jshaughn please, can you take a look ?
If this is ok, then tomorrow we can work upgrading 0.4.x + ui-services and fixing missing things on UI code.

Looks like it needs a rebase due to global commit that went in earlier.

Other than the variable names, this looks OK to me.

LGTM Lucas. Ship it! ;)

@mtho11, @jshaughn, I've sent a feedback commit and rebase with master, can you check everything looks good ?

Maarvelous!


[rlgl] Reviewed rlUpdateShaderBuffer(), it can not update the size

With this change rlUpdateShaderBuffer updates the size of the buffer.

@MrScautHD I'm afraid I don't understand this PR, it looks confusing to me on its intended behaviour... It should be reviewed more carefully...

@MrScautHD I'm afraid I don't understand this PR, it looks confusing to me on its intended behaviour... It should be reviewed more carefully...

After you set the size in loadbuffer you can not anymore change the size in the buffer update

After you set the size in loadbuffer you can not anymore change the size in the buffer update

And that's the expected behaviour, rlUpdateShaderBuffer is sued to update an existent pre-defined shader buffer, not change its size.

:/


[FEATURE] Add withHost option for username

Resolves: #370
I added a "withHost" option for the username segment which makes the username segment also show the hostname just as in normal POSIX shells, like this: username@hostname.
Config option:
"username": {
    "withHost": true
}

Screenshot:

@b-ryan ?

My initial reaction to this is that I feel like there should be a better way to handle this. This code is essentially going to duplicate the hostname segment, meaning if there happened to be a change necessary to that segment, I would need to remember to update this code alongside it. Needing to remember this is not a great strategy.
I also think the larger problem you have is just fine-grained control over the way segments are put together. For example, my first idea (not necessarily the best way to do this), would be to give options like prefix and suffix to every segment. The default would be a single space, but you could then do something like this in your config:
"segments": [
  {"type": "username", "suffix": "@"},
  {"type": "hostname": "prefix": ""}
]

I think this deserves more thought, so I am not wanting to rush into incorporating this change.

Alright, so how do you want to proceed?


Support VALUES() construct in parser and rewrite for upsert query

@sougou
One thing I'm concerned about in general that I noticed while working on this is that schema.Table FindColumn is O(n) and seems to be called in loops quite often in dml.go.  I looked at adding a columnCache map[string]int to the struct, which would cache a mapping of ColIdent.Lowered() to position in the Columns slice. But it messed up a bunch of tests.  Do you think we should add it back? I also wasn't sure about synchronization/mutability concerns.

cc @adkhare not sure if you guys still would benefit from this

thanks for the heads up @adkhare! I'll take care of recreating the sql.go and re-pushing

@sougou pushed a new revision for review. Added a few comments to explain. I think this approach is much more elegant as well as more complete in terms of syntax support.

resolved merge conflicts

I see that you cheated, albeit elegantly :).
The high level objection is that there are some advantages to treating the AST as read-only. However, I have myself broken that rule in a couple of places.
I'll think about it some more. If I can't come up with something better, we can go with your approach.

Resolved merge conflicts again. Let me know if you come up with anything :)

LGTM


Adding zs_simple_toggle directive

Simple_Toggle PR

Please correct module names in documentation and example

Please commit directly to upstream :octocat:


Support for using tracing span fields as metrics labels (dynamic labels remix)

This is a remix of #87 where we solve the issue of cached callsites by pushing dynamism directly into Label itself, so that the macros can understand the full scope of when caching is safe to perform.
It accomplishes this by utilizing a resolved/unresolved paradigm, letting labels be declared upfront as "dynamic" so that downstream layers/recorders can potentially "resolve" them by providing a value, such as the tracing layer checking all current span fields and using those values.
An example:
// A counter with entirely static labels.  "Static" here defines a label that is fixed and can't
// be updated by a downstream layer, not specifically that both key/value are `&'static str`.
counter!("my_counter", 1, "key" => "value");

// A counter with a dynamic label.  This allows downstream layers to inspect it, and if desired,
// update the value of the label with whatever they want.
counter!("my_counter", 1, "dynamic_key");

Some design assumptions here:
All layers/recorders will be forced to filter out dynamic labels that are not yet resolved.  This is an ergonomics snag that we could potentially solve by adding another type that deals with entirely unresolved labels, and then have Label be a resolved label that always has a key/value.  Not sure how big of an issue this is, since once your recorder handles it, you're done.
This approach does not address the underlying issue with downstream layers/recorders adding new labels to a key during registration.  One potential solution is to add the ability for recorders to declare that they're going to modify the key, or all keys, such that the callsite can detect whether or not it's safe to cache the identifier.  This might involve a tweaked identifier that exposes its own cacheability, or some new Recorder trait method that determines if a given Key would be altered if registered.

Closing this as we merged #87


Fix bug in dark mode navbar hover

When the navbar "a " elements are hovered, its hard to see the text in the dark mode. Hence removing the hover as shown below would be a suitable fix.

Hi! I'd like to take this one for OSD w/AnitaB.
For clarity, is it completely take out the link hover color? Or is it taking it out only when it is in dark mode?

Take it out for both light and dark modes

Assigned to @ceruleanox

Hi!
While adding the following fixes the issue, it does not remove the hover:
.dark-theme .nav-link:hover{
color: rgba(255, 255, 255, 1) !important;
}
The black hover comes from the default template (Bootstrap probably) being used. That is, the color is not defined in any CSS file. Did you want me to create a PR with the addition? Or did you want to define another issue to make this edit?

you can create a new issue for this

Writing to follow up that I created separate issue and pull request:
#1010 - https://github.com/smaranjitghose/awesome-portfolio-websites/issues/1010
PR - https://github.com/smaranjitghose/awesome-portfolio-websites/pull/1011


Keystone authorization improvement

What this PR does / why we need it:

Support flexible authorization policy configuration like the following:
[
  {
    "resource": {
      "verbs": [
        "get",
        "list",
        "watch"
      ],
      "resources": [
        "pods"
      ],
      "version": "*",
      "namespace": "default"
    },
    "match": [
      {
        "type": "role",
        "values": [
          "k8s-admin",
          "k8s-viewer",
          "k8s-editor"
        ]
      },
      {
        "type": "project",
        "values": [
          "c1f7910086964990847dc6c8b128f63c"
        ]
      }
    ]
  }
]

Change the example policy file and the doc accordingly

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #64
Special notes for your reviewer: None

/ok-to-test
/lgtm


Datasources API Update

Like we discussed in Matrix chat, this updates the Datasources API to use JSON refs rather than our bespoke "metadata query" API which could have returned more than one Datasource for a query. I pulled in a new library called jsonref that takes care of resolving the reference to the Datasource (including fetching from the Perses API if that's what's referenced). One other nice side-effect of this is that the DatasourcesRegistry no longer needs to block rendering while loading the entire list of Datasources. Instead, they're loaded on demand as the panels request them.
Some of the sample data was a little out of date, so I updated that to fix a few compile errors and use the new ref API. Let me know if you have questions!

Closing this while we discuss in #404


compilecatalog: Switch to new HTTP client implementation

The new HTTP client was introduced in https://github.com/puppetlabs/puppet/pull/7826. First released in Puppet 6.11.0. The old HTTP client is deprecated. The new implementation makes it quite easy to configure additional/custom TLS certificates. I
plan to implement that in another PR.

@alexjfisher any objections on merging this?

I think it's ok.


test: enrich ut for WithWriteTimeout in server/option.go

What type of PR is this?

test: Adding missing tests or correcting existing tests
Check the PR title.

[x] This PR title match the format: <type>(optional scope): <description>
[x] The description of this PR title is user-oriented and clear enough for others to understand.

(Optional) Translate the PR title into Chinese.
补充 server/option.go 中 WithWriteTimeout 的单元测试
(Optional) More detail description for this PR(en: English/zh: Chinese).

en: enrich ut for WithWriteTimeout in server/option.go
zh(optional): 补充 server/option.go 中 WithWriteTimeout 的单元测试
Which issue(s) this PR fixes:

null

LGTM


Feat: Add some more information for exceptions collected via FlutterError.onError

:scroll: Description

The information in the red square is added by this PR.
:bulb: Motivation and Context

:green_heart: How did you test it?
Changed test accordingly
:pencil: Checklist

[x] I reviewed submitted code
[x] I added tests to verify changes
[ ] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

:crystal_ball: Next steps

Codecov Report

Merging #538 (e22e346) into main (3e7deaa) will increase coverage by 0.45%.
The diff coverage is n/a.

:exclamation: Current head e22e346 differs from pull request most recent head fdf86e9. Consider uploading reports for the commit fdf86e9 to get more accurate results

@@            Coverage Diff             @@
##             main     #538      +/-   ##
==========================================
+ Coverage   91.54%   92.00%   +0.45%
==========================================
  Files          74        7      -67
  Lines        2426      250    -2176
==========================================
- Hits         2221      230    -1991
+ Misses        205       20     -185

Impacted Files
Coverage Δ

dart/lib/src/utils.dart

dart/lib/src/platform_checker.dart

dart/lib/src/sentry_user_feedback.dart

dart/lib/src/protocol/max_request_body_size.dart

dart/lib/src/protocol/sentry_user.dart

dart/lib/src/protocol/sentry_browser.dart

dart/lib/src/protocol/sentry_device.dart

dart/lib/src/transport/rate_limit_parser.dart

dart/lib/src/sentry_envelope_item.dart

dart/lib/src/protocol/sentry_package.dart

... and 57 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 3e7deaa...fdf86e9. Read the comment docs.

How often can the information field be larger than what Sentry can display properly? It transforms an array into a single line, so it could end up truncated or not fitting the UI very well.

Hard to say as its origin can be the Flutter framework, libraried and developers themselves.
So it's probably better to assume that it can be very long.

Perhaps we need to find another way to present it?

What would be a better way to display this?
As far as I can tell, the only data which is displayed as a text block is the exception description.
The events data could be another place for this, but then the information would be visually disconnected in the Sentry UI :(

It doesn't play nicely if it's really long :(

@ueman is this ready to be merged or the multiple line thing should be tested?

@ueman is this ready to be merged or the multiple line thing should be tested?

It works and is tested but it could be that it doesn't look that good in the Sentry UI for long information. So unless you or @bruno-garcia has a better idea where to put the information this is good to go.

I tried to add it to the events extra data, but then this information kinda gets lost.

what do you mean by kinda get lost? does it make to Sentry or not easy to find since the information is down there in the additional data?
just trying to understand if we have a bug or not.

I tried to add it to the events extra data, but then this information kinda gets lost.

what do you mean by kinda get lost? does it make to Sentry or not easy to find since the information is down there in the additional data?
just trying to understand if we have a bug or not.

It gets visually lost when it at the same place as all the device, os and app information. It does make to Sentry so it's not a bug.

This event has the data added to the mechanism and as the crash_context. At the top I think it's really useful, though it might not look good for long text, just like @bruno-garcia said. At the bottom, the information gets kinda visually lost next to all the meta data.

I'm a bit wary of adding data that'll be potentially large in that field in this form. Perhaps best we find a way to break in up in more 'key/value' pairs

This is looks amazing for us, as we have 3 different flutter apps all using this context data and we've only just realized it's missing. Very keen to help out in any way that I can.

Thanks! That's really appreciated.
Do you mind answering the following questions?

How long are your context and information values?
What length of these fields have you seen in the wild?
How would you like to see these fields in the Sentry UI?

Our context fields are typically 3-4 words, similar length to your example. We have none longer than 36 characters. I'm afraid we've never seen information values in practice, as Sentry isn't capturing them :P. Looking at the definition of FlutterErrorDetails, it seems reasonable to suggest these should be key/value pairs, but as far as I can tell you could only split on the newlines that may or may not exist. Seems fine for most use-cases? I don't know a lot about the Sentry UI though sorry. A neat UX might be that if a tag is too long up the top, it is cut off and can be clicked to scroll down to the full value.

Okay, I've changed it so that the mechanism has a tag which tells the user to look for a flutter_error_details context down below. Down there, everything displays well. I hope that is satisfying for all :D


Rehash after install on zsh systems

A detailed description of the proposed feature
It'd be great if rehash was automatically run after every executable install when running on zsh systems (Catalina).
The motivation for the feature
Save the user having to remember to run it after every install that adds binaries.
How the feature would be relevant to at least 90% of Homebrew users
I guess as soon as 90% of users are on zsh
What alternatives to the feature have been considered
The alternative is having to do it yourself

I'm pretty sure this isn't possible given that Homebrew is executed in a non-ZSH shell at all times. If you can figure it out and submit a PR, though: we'll review it. Thanks!


Upgrade gradle Android base libs

TASK upgrade build:gradle to 2.2.3
TASK upgrade compileSdkVersion 25
TASK upgrade buildToolsVersion 25.0.2
TASK upgrade targetSdkVersion 25
TASK upgrade support-fragment 25.1.0

@olidroide thanks for the pull request. I will release it this weekend.
Thanks again.


Granularity

I as a Squeak Developer want to be able to choose the granularity of the analysis: Whether I only want to monitor a function or a whole program should be my decision so that I can quickly eliminate bottlenecks.

Add this to Message Tally Console (e.g. Start, Stop, Filter).


Set ui-index setting to local if rancher version is formal

Problem:
For now, we don't respect the ui-index setting in formal
rancher version. There is no way for users to customize their UI in
those version.
Solution:

Use local value in ui-index setting when it is a formal version.
When ui-index setting is local, fetch UI from file
When in development version, always fetch UI from remote address
in ui-index.

Related issue:
https://github.com/rancher/rancher/issues/14392
https://github.com/rancher/rancher/issues/17488
https://github.com/rancher/rancher/issues/17312

This previous PR has been reverted in https://github.com/rancher/rancher/pull/17864
export the following env will fix this issue.
export CATTLE_UI_INDEX_DEFAULT=${UI_INDEX:-"https://releases.rancher.com/ui/latest2/index.html"}
export CATTLE_RKE_VERSION_DEFAULT="$(grep -m1 '^github.com/rancher/rke' vendor.conf | awk '{print $2}')"

LGTM as the only difference is exporting the envs

Rebased

We have tested it including upgrade from v2.1.x

Updated

Updated

@orangedeng Can you delete the generator package since it is no longer being used?

Updated, Sorry about that.

np. lgtm. just waiting for green build


Move key-generation into new module

Codecov Report

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

@@            Coverage Diff            @@
##             master     #480   +/-   ##
=========================================
  Coverage     99.65%   99.65%
  Complexity     1169     1169
=========================================
  Files           189      189
  Lines          3766     3766
  Branches        194      194
=========================================
  Hits           3753     3753
  Partials         13       13

Impacted Files
Coverage Δ
Complexity Δ

...uorum/tessera/key/generation/KeyGeneratorImpl.java
100% <ø> (ø)
7 <0> (?)

...um/tessera/key/generation/KeyGeneratorFactory.java
100% <ø> (ø)
1 <0> (?)

...essera/config/cli/parsers/KeyGenerationParser.java
95% <ø> (ø)
8 <0> (ø)
:arrow_down:

...era/key/generation/DefaultKeyGeneratorFactory.java
100% <ø> (ø)
2 <0> (?)

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 345ac5a...8438640. Read the comment docs.


Footer Fiasco: Misaligned with Navbar in Vibrant Light Mode

Is your feature request related to a problem? Please describe.
I'm frustrated when the footer in the light theme doesn't stay aligned with the navbar. The vibrant colors and overall layout feel disrupted, especially when navigating pages. This misalignment makes the UI look inconsistent and impacts the user experience negatively, making the footer appear detached from the rest of the design.
Describe the solution you'd like
I’d like the footer to align perfectly with the navbar in the light theme, maintaining consistent spacing and structure. The dynamic, colorful nature of the theme should be preserved without any visual discrepancies between key elements like the navbar and footer.
Describe alternatives you've considered
I’ve considered removing the footer in light mode, but that would take away from the site's design. Another option could be simplifying the layout, but that would reduce the visual appeal and limit customization.
Additional context
This issue only seems to occur in the light theme. Dark theme behaves as expected. Here's a screenshot highlighting the misalignment between the footer and navbar.

Please assign this Issue to Me

I have thought of this design  to look perfect with the vibe of your website

thanks for your input but i prefer the design that we have right now

Fine then . No problem


Build status badge broken

When going through the README I noticed that your repositories "build status badge" from Travis CI is broken.

Looks like it is linking to the old name of the repo? Either way, it doesn't look like CI has been set up for the project under this name.

Fixed..


There is a problem with npm install when using node 4.x

The bug is in contextify, and I worked around the problem with the help of this comment:
https://github.com/brianmcd/contextify/issues/180#issuecomment-142148860
I opened this in case anybody else comes across this problem.
When this bug is fixed and a new release made, this issue should be closed.

👍🏻
On Thu, Oct 15, 2015 at 10:37 AM Joseph Rawson<EMAIL_ADDRESS>wrote:

The bug is in contextify, and I worked around the problem with the help of
this comment:
brianmcd/contextify#180 (comment)
https://github.com/brianmcd/contextify/issues/180#issuecomment-142148860
I opened this in case anybody else comes across this problem.
When this bug https://github.com/brianmcd/contextify/issues/180 is
fixed and a new release made, this issue should be closed.
—
Reply to this email directly or view it on GitHub
https://github.com/KyleAMathews/coffee-react-quickstart/issues/30.


Unable to send dupalicate param on multipart request

Is there any way to send @Part parameters with the same key as part of a multipart request?
In this example, I want to send multiple tags
part parameter
....
@Part(name: "tags") List<String> tags
....
generator output
.....
_data.fields.add(MapEntry('tags', jsonEncode(tags)));
.....
Desiree behavior: it should generate multiple MapEntry instances for the same parameter
I used a List as a parameter type but then looking into the generator code I notice that any field with type Map, BuiltMap, List, BuiltList will be converted to JSON.
Does anyone have an idea on how to solve this issue?

Hi @trevorwang , cloud you please help me on this? or at least give me yours thoughts about this.

really awesome, thanks so much!!


Have a unique id for each entity

It would be great if each entity had a unique id, that can never change. At first I thought the guid was a good idea, but the guid can change on certain workflows as explained by @Maksims .
The reason I want a unique id for each entity, when there is a findbyname function, is because I want to search for an entity without relying on a magic string.
I am also aware that I can search for entities using an entity attribute, but that's not the best solution when you are looking for a specific entity and there is no reason to having to expose the entity and assign it in the inspector.
What I want is basically a findbyname that is safe. Having a unique id for each entity would solve the issue.

A guid is a unique id for the lifetime of the app. The issues described with in https://github.com/playcanvas/editor/issues/616 are to do with the data in the project, not in the engne.