text:
Script fails with error parsing token on firewall main page

Hola!
I've been trying to use the script with OPNsense 24.7.7-amd64, done all the steps as per README and getting the following error:
/migrate_pfsense/src# python3 migrate_pfsense.py
connecting to firewall on https://192.168.8.x
[+] firewall login sucessful
==== STARTING MIGRATION OF STATIC ROUTES
==== STARTING MIGRATION OF CERTIFICATES
error parsing token on firewall main page

I've pinpointed it that at the failing call r.text there are no "hidden" values with CSRF, instead it's being passed as JavaScript:
xhr.setRequestHeader("X-CSRFToken", "O0r5HWqHwRocQMk40fFHyg" );
After investigation it seems that system_camanager.php and subsequent links are missing from modern OPNsense, it's been replaced with /ui/trust/cert

What was the version of OPNsense that migration script was known to work with?

Having exactly the same issue using OPNsense 24.7.7-amd64 freshly installed.

It has been used in opnsense 23.x.
not updated yet for 24.x series.

Thank you for your reply.
I just took my chances and downloaded the 23.x series release, did a fresh install, imported everything and was able to update up to 24.7, took a bit longer but worked flawlessly.
Thank you for your work!

@sysadminbr  Is there any plan to update the tool for 24.7?

Updated to work with 24.7.7.

closing it since it was updated to work on most recent 24.7 opnsense series.

authors: sudheeshb sysadminbr tjakobi useribs


text:
Support loadbalancer for ingress-nginx

/kind feature
Describe the solution you'd like
[A clear and concise description of what you want to happen.]
Hi, I've been following this tutorial
and have created manually a loadbalancer with two service pointing to both ports 80 and 443 with ssl-passthrough, because ingress-nginx should be terminating that.
Is it possible to allow the creation of a loadbalancer additionally to the already provisioned controlPlaneLoadBalancer?
Do I need a regular floating ip that ingress-nginx is able to pick that up or use something like metallb for multiple ones?
Thanks in advance!
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
I'll definitely try out your tilt setup next
https://github.com/syself/cluster-api-provider-hetzner/blob/main/docs/developers/development.md#tilt-for-dev-in-caph
to be able to incorporate your changes sooner.
Environment:

cluster-api-provider-hetzner version: v1.1.1 (This new version works with provisioning too)
Kubernetes version: (use kubectl version) 1.23.3
OS (e.g. from /etc/os-release): fedora-35

@FischerLGLN Thank you for your issue. Only to clarify: You mean an additional loadbalancer to use ingress-nginx?
Right now the created loadbalancer is necessary because the ccm is not available at cluster creation time. It's also only there to serve the kube-apiserver and has only the control-plane nodes as a target. Therefore every additional loadbalancer to consume in a k8s service is managed by the cloud-controller-manager .

@batistein Thanks for the quick response. Yes, the first control plane loadbalancer forwards from 443 to 6443, therefore blocking port 443. That's why I need another one for ingress-nginx or let it's 443 service listen on another port.
Following your link, is this the reason for deciding on Cilium?

The CNI plugin you use needs to support this k8s native functionality (Cilium does it, I don't know about Calico & WeaveNet), so basically you use the Hetzner Cloud Networks as the underlying networking stack.

Calico with eBPF works fine too, at least if not using cloud-controller-manager.
helm repo add projectcalico https://projectcalico.docs.tigera.io/charts
helm install calico projectcalico/tigera-operator --version v3.22.0

If I use cloud-controller-manager in contrast to terraform, I get the benefit that changes in Hetzner Console also affect the underlying Kubernetes, right?

@FischerLGLN you could change the port to anything you want by changing in HetznerCluster spec.controlPlaneEndpoint.port to what you want. It's only important to know that you cannot update this port in a running cluster. Also FYI you could use the host for specifing a dns name which needs to point to the created loadbalancer.
There is no decision to use only cilium you could use whatever CNI you want. Cilium in my experience is only the best option at the moment as you could also run it kube-proxy free and use only eBPF and no iptables. But of course that's only my opinion.
To use or not to use cloud controller manager is nothing we could really decide as this is mandatory for running kubernetes on hcloud.

@batistein ah okay, so I would have to power down the node and make the service-changes then.
About the dns name, I did something like that on openstack with k3s using tls-san on the master-node pointing to my ports 80/443 loadbalancer.
Yes, Cilium has the best performance (with a higher load).
Okay great, I am closing this issue now.
Thank you for the technical exchange!

Hi, I tried it the next day and autoprovisioning of the loadbalancer for the ingress-nginx worked!
After installing ccm in private network mode, I had to annotate the nginx loadbalancer
to provide a cloud loadbalancer for example in Falkenstein.
helm repo add ingress-nginx https://kubernetes.github.io/ingress-nginx
helm repo update

helm upgrade --install ingress-nginx ingress-nginx \
  --repo https://kubernetes.github.io/ingress-nginx \
  --namespace ingress-nginx --create-namespace --set 'controller.service.annotations.load-balancer\.hetzner\.cloud/location=fsn1'

source: gharchive/issue

authors: FischerLGLN batistein

repo: syself/cluster-api-provider-hetzner

license_type: permissive

license_source: github-api


text:
PIP6048MT QPIGS timeout even with data coming in

Hello! I am seeing QPIGS response but it's not decoded and it says timeout
[11:24:54][D][uart_debug:158]: >>> "QPIRI\xF8T\r"
[11:24:54][D][pipsolar:838]: Sending polling command : QPIRI with length 5
[11:24:55][D][uart_debug:158]: <<< "(220.0 27.2 220.0 50.0 27.2 6000 6000 48.0 45.0 45.0 53.2 53.2 3 040 010 1 0 2 1 01 0 0 49.0 0 1\xBA\xAB\r"
[11:24:55][D][pipsolar:772]: checking crc on incoming message
[11:24:55][D][pipsolar:775]: CRC OK
[11:24:55][D][pipsolar:429]: Decode QPIRI
[11:24:55][D][sensor:127]: 'pip6048mt_grid_rating_voltage': Sending state 220.00000 V with 1 decimals of accuracy
[11:24:55][D][sensor:127]: 'pip6048mt_grid_rating_current': Sending state 27.20000 A with 1 decimals of accuracy
[11:24:55][D][uart_debug:158]: >>> "QPIGS\xB7\xA9\r"
[11:24:55][D][pipsolar:838]: Sending polling command : QPIGS with length 5
[11:24:56][D][uart_debug:158]: <<< "(218.1 49.9 218.1 49.9 0327 0295 005 360 51.20 000 100 0037 00.0 000.0 00.00 00000 00010000 00 00 00002 011 0 00 0000\xD2w\r"
[11:25:00][D][pipsolar:755]: timeout command to poll: QPIGS

And it just repeats like this
Is my QPIGS response unusual? What can I do with this?
Thank you
Here's esp settings related to pipsolar
logger:
  hardware_uart: UART1
  level: DEBUG
  # Don't write log messages to UART0 (GPIO1/GPIO3) if the inverter is connected to GPIO1/GPIO3
  baud_rate: 0

uart:
  - id: rs232_inverter
    tx_pin: GPIO1
    rx_pin: GPIO3
    # most devices use 2400 as baud_rate
    baud_rate: 2400
    debug:
      direction: BOTH
      dummy_receiver: false
      after:
        delimiter: "\r"
      sequence:
        - lambda: UARTDebug::log_string(direction, bytes);

pipsolar:
  - uart_id: rs232_inverter
    id: pip6048mt

sensor:
  - platform: pipsolar
    pipsolar_id: pip6048mt
    grid_rating_voltage:
      id: pip6048mt_grid_rating_voltage
      name: pip6048mt_grid_rating_voltage
    grid_rating_current:
      id: pip6048mt_grid_rating_current
      name: pip6048mt_grid_rating_current
    ac_output_apparent_power:
      id: pip6048mt_ac_output_apparent_power
      name: pip6048mt_ac_output_apparent_power
    ac_output_active_power:
      id: pip6048mt_ac_output_active_power
      name: pip6048mt_ac_output_active_power```

Using 2424mse1 branch didn't resolve the issue

I made a PR https://github.com/syssi/esphome-pipsolar/pull/52 with the fix

repo: syssi/esphome-pipsolar


text:
Emscripten module compatibility

Builder makes the emscripten shell think it's running in node. It then tries to require node modules like fs.
Related discussion here. Possible solution here.

@Garciat it sounds like the wrapper assumes it is in Node if it is using CommonJS with process defined.
You can alter the way that SystemJS interprets the module by forcing it to be loaded as a global or amd format via meta configuration, which may then work better for building the wrapper. See https://github.com/systemjs/systemjs/blob/master/docs/module-formats.md for more info on format handling in SystemJS.

@guybedford I'll take a look; thanks :+1:

Yup. That did the trick.
For future reference:
new Builder({
    ...

    meta: {
        'myapp/emscripten_module': {
            format: 'global'
        }
    }
})

Yup. That did the trick.
For future reference:
new Builder({
    ...

    meta: {
        'myapp/emscripten_module': {
            format: 'global'
        }
    }
})

authors: Garciat guybedford

repo: systemjs/builder

license: mit

license_source: bigquery


text:
babelOptions ignored in esm compiler

babelOptions defined in jspm.conf.js or by direct calling SystemJS.conf() or System.conf() are not passed to the babel transpiler in https://github.com/systemjs/builder/blob/master/compilers/esm.js#L59. Isn't it needed at this place? This causes warnings of the babel transpiler for large files, because compact mode can't be enabled  : https://github.com/babel/babel/blob/master/packages/babel-generator/src/index.js#L81.

This is a different transpilation which only converts ES modules into System.register, separate to the other Babel transforms.
An option to pass compact here could be worth providing though.

Why is Babel called twice? Babel could do all transpilation in one step for a file or I am wrong!? Please, could you shortly explain in which steps the builder transpiles the source code files?
Why is it hard to achieve to set the compact option for the transform operation? The options object is present on the builder instance or isn't it?
Thanks for answering in advance

Are you trying to turn compact on or off?

Yes, by setting in jspm.conf.js and by .babelrc, but the call at line esm.js#59 doesn't pass the compact option. I have debugged it by creating a gulp task and call the Builder directly.

Specifically I was wondering what value you wanted for the compact option, to understand the use case better.

Sorry, I want to disable the warning by using compact=true, which is logged for compact="auto" (default value) in line index.js#L81 for large files.

I'd be open to setting a hard default of compact: false if you think that could work.

Yes, this should work.
For understanding systemjs and systemjs/builder in more detail, do you have a short description, documentation for the internal architecture? It would be helpful for using systemjs in the correct intended way. Especially for Babel. I saw you are working on docs, could it be part of it?
Thanks

I'd be open to setting a hard default of compact: false if you think that could work.

I'd love to have a compact: false hard default as well. Not only to remove the annoying [BABEL] Note: The code generator has deoptimised the styling of "..." as it exceeds the max of "100KB". warnings, but also because it makes debugging such modules such harder due to the deoptimised styling.

Sure, added in https://github.com/systemjs/builder/commit/8a73596a26a63343bb9d1ff3893e9577914fb9ec.

Released in 0.15.33.

authors: guybedford laurentgoudet malaupa


text:
Enhanced button interaction

Gave some cool interactions to the button ranges.

Hm. I would like to avoid to have any additional controls, as i would like to use controls that fit my application style.

closing as stale

source: gharchive/pull-request

authors: UziTech hosuaby sudhinm

license: MIT


text:
How to validate on update

I'd like to reuse validation functions which are run on document creation to also be used for updates but can't seem to find anything which will do this.
What I currently have is:
Model.updateOne(
  { _id: Types.ObjectId(id) },
  {
    name
  }
).then(data => {
   ...
}).catch(err => {
  // handle validation error
})

Is there a way to run an object through validation before updating? I can't seem to find a method using @pre("update")

since #353 you can use @pre(/^update.*/, () => {}) (RegExp)
so this could be closed
@Ben305

authors: alex-deas hasezoey

repo: szokodiakos/typegoose


text:
[Feature]: Ask for state

Requested feature
Asking for a state of a switch I get "not sopported"
Can this be implemented?
Documentation & Issues

[X] I have reviewed the list of currently supported entities and their limitations.
[X] I have searched the issues for a similar requests.
[X] I have checked if my controller is known to support the requested device type.

What exactly do you mean? In a first place this question needs to be asked to the ecosystem you use ... because the "not supported "comes from them - or is there any traffic/commands seen in the log of the bridge?

Sorry for the very bad explanation. I have asked for the same problem somewhere else, but cannot remember where. So I will explain it again here.
I can ask Aleaxa for "current temperature", that works fine. But asking für "humidity" I get the answer "not supported" allthough the hunmidity value is displayed in the Alexa app and  as stated in the documentation, "humidity" shall be supported. From the diskussion in the other thread I was told, that "humidity" works with Google Home. Thus I think something is missing with Alexa.
If I try to asks i.e. "dew point", the answer is "not available" which seems to be correct since it si not implemented yet.
With "log of the bridge" do you mean the protocol of the hub add-on? There is nothing printed when I ask anything, even with log level debug or silly. Where do I have to look?

Can you try creating a template sensor for humidity in home assistant which copies the temperature value from the climate.
Then you can expose this sensor to Alexa. Does it still say that humidity is not supported?

Sorry, I'm not yet that familar with template sensors.
Here is, what I've done.
Created a helper for sensor template
In template options I'm getting an error
Sensor None has device class 'temperature', state class 'measurement' unit '°C' and suggested precision 'None' thus indicating it has a numeric value; however, it has the non-numeric value: 'sensor.basement_sensor_module_bme280_temperature' (<class 'str'>)
It seems, the temperature value comes as a string from MQTT. In use Tasmota on my devices.

You can create a template sensor using the helpers:

sorry. mixed it up, but similar for humidity.

Thx, I've created such a helper and added the according label for the entity to be exposed to the matter hub.
But in the hub this entity is not shown there. I've rstarted the add-on and emproved it with another entity (not template entity) , which is exposed.

although the humidity value is displayed in the Alexa app

Where is the sensor instantiated?  Is it a native humidity sensor in HA or is it a native Amazon Air Quality Monitor sensor in Alexa?

The sensor is an I2c-Sensor on my Tasmota-Device.
The sensor entity is automatically added from Tasmota auto discovery.
May be there is the reason.
What is necessary that the entity is recognized as humidity?

The sensor entity is automatically added from Tasmota auto discovery.

Is that auto discovery in HA?


text:
3.6 Compatibility

In the README, it says compatibility with puppet < 3.5.
Is this module known to not work with Puppet? Why not? What kind of work would have to be done?

@maxbucknell This actually works with all Puppet versions since 2.7, closing this.

@tPl0ch Will you update the README to indicate this compatibility? I came upon this issue with the same question.

authors: maxbucknell scottsb tPl0ch


text:
Updating Root Class for 'Documentation' Thumbnail

@d45

Thanks, @greg-fix. We fixed this a while back when we added more tiles.

repo: tableau/extensions-api


text:
Internal Server Error - Gem Rack problem

Whenever I start the server with
java -Dfile.encoding=utf-8 -Xms256M -Xmx1024M -jar tabula.jar
It returns the following error to me:

I'm looking in to the error myself, but I just wanted to report the bug...

Closed by #458, thanks!

authors: jazzido pedro-stanaka

repo: tabulapdf/tabula


text:
Gemfileのrubyバージョンに合わせる

Gemfileにrubyバージョンの指定が記載されてるなら合わせた方が良いかなと思いました

ありがとうございます＠

authors: soramugi tadyjp

repo: tadyjp/rendezvous


text:
fix(protocol): assembly Error fix

Error:
Compiler run failed:
Error (4619): Function "mcopy" not found.
   --> contracts/automata-attestation/utils/BytesUtils.sol:273:13:
    |
273 |             mcopy(dest, src, len)
    |             ^^^^^

We can solve this using :

 function memcpy(uint256 dest, uint256 src, uint256 len) private pure {
        assembly {
            for {
                let i := 0
            } lt(i, len) {
                i := add(i, 32)
            } {
                mstore(add(dest, i), mload(add(src, i)))
            }
        }
    }

This loop copies 32 bytes at a time until the specified length is reached. Note that this implementation assumes that the length is a multiple of 32.

I don't have to error. Are you using the right compiler version?

Yes the right complier version is being used

authors: cryptoryda dantaik

repo: taikoxyz/taiko-mono


text:
feat: enhanced log format

Summary:
/claim #1270
/fixes #1270
Issue Reference(s):

Build & Testing:

[ ] I ran cargo test successfully.
[ ] I have run ./lint.sh --mode=fix to fix all linting issues raised by ./lint.sh --mode=check.

Checklist:

[ ] I have added relevant unit & integration tests.
[ ] I have updated the documentation accordingly.
[ ] I have performed a self-review of my code.
[ ] PR follows the naming convention of <type>(<optional scope>): <title>

In the screenshot, there is an arbitrary space before ]
- [INFO ] # Actual
+ [INFO] # Expected

@tusharmath Updated ss:

repo: tailcallhq/tailcall


text:
update else if to switch

update else if to switch

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

建议把 writer 的一并修改，以保持代码风格的统一。

LGTM.

repo: tair-opensource/RedisShake


text:
PAT を使用して README を Push する

Close #195
https://github.com/geolonia-bot のパーソナルアクセストークンを使用して READMEを git push するように修正しました。
パーソナルアクセストークンの発行と、geolonia-bot ユーザーの招待を承諾頂いた後に README の push テストをしようと思います。

@keichan34
ありがとうございます。以下のように修正しました。

paths-ignore: README.mdを使用して GitHub Action から README 更新時に、ステータスチェックを発火させないように修正
EndBug/add-and-commit@v7 を使用して push するよう修正
以下の理由から push 時ではなく、checkout 時にパーソナルアクセストークンを使用するように修正

EndBug/add-and-commit@v7の仕様
push時にGITHUB_TOKEN環境変数で渡すのでは上手く渡せなかったため（token で渡せば良かった?）

修正内容のコードを反映したテストリポジトリでの、PR のURL も共有します。
https://github.com/naogify/opendata/pull/19

@keichan34
こちらREADME も push するように修正しました。サンプルのPRは以下になります。
◼新規データの追加
https://github.com/naogify/opendata/pull/53
◼既存データの更新
https://github.com/naogify/opendata/pull/52
◼データ以外の更新
https://github.com/naogify/opendata/pull/54

repo: takamatsu-city/opendata


text:
为何cilent.gl内容为空？

如题
console.log(bot.gl);

的输出为
Map(0) {}

是我的使用方法有问题吗
求解答

你没登录吧

authors: gbCzz takayama-lily

repo: takayama-lily/node-onebot


text:
Training helen landmark indexing

Hi i have trained a model with the helen dataset. Works great btw! I just wonder how to fix the landmark indexing. It is bit chaotic, consitent chaotic, but still:)  ->

This strange indexing is coming from dataset.
You must modify dataset if you dislike dislike it.
But FaceRecognitionDotNet return the group of location per face parts.
Please check https://github.com/takuya-takeuchi/FaceRecognitionDotNet/blob/1d99e43591f6996910ab1a2abc0facbdd1ee24f4/src/FaceRecognitionDotNet/FaceRecognition.cs#L339

So i was looking at this for two days now and dont get the logic. Could you please elaborate why these indexes are so strange? The index code says they are mapping is for a 194 landmarks helen trained model? No? When you say "You must modify dataset if you dislike it.", what do you mean?
I am bit lost. If you have a moment please try to clarify the situation and outline what to do. I am happy to work this but very confused right now. I am not familiar with ML and maybe overthinking this. Please give some hints. Thank you.

I just wonder how to fix the landmark indexing.
At first, I thought you dislike discontinuous index (like 0, 1, 106, 117..). Therefore, I said 'You must modify dataset if you dislike it.'.

However, I checked the dataset again and I found that face parts point order is not strange.

So training program may have any issue but it looks like working well.

At first, I thought you dislike discontinuous index (like 0, 1, 106, 117..). Therefore, I said 'You must modify dataset if you dislike it.'.

Yes exactly, i dont like the order. Still dont understand how to modify the dataset. Feels like i am missing a concept here or confuse wording. do you mean the index mapping you linked to in the code? Yes I wonder why you do the mapping in the code like this.
Should not all the parts have consecutive indexes like chin 0-100, left eye 101-120 and so on. (numbers just estimated). The only part that differs would be the mouth where two parts (upper and lower lip) share some indexes. It seems pretty much like constructing polygons from vertex indexes. I am familiar with this concept.

However, I checked the dataset again and I found that face parts point order is not strange.

So training program may have any issue but it looks like working well.

I do not understand what you mean here. So yes i see your screenshot where the indexing seems ok in the beginning of chin part (0,1,2,3..) Why does mine differ (0, 1, 106, 117..)? I was using the vanilla helentraining example you provide. Still confused sorry :)

The above image is created from original dataset image rather than result of inference.
So I face same issue you faced.
This image is result of inference from my helen dataset model.
And target image (helen\helen_1\1115234911_1.jpg) equals to the above image.

Therefore, this trange index order is not generated randomly but I don't know why.

Ok i see. just misunderstanding:) Is it not just the index mapping in PredictorModel.Helen?
When I look at the predictor models in the code i see PredictorModel.Large is pretty logical and clear. PredictorModel.Helen on the other side is confusing.
Why is the chin part not just:
 { FacePart.Chin,         Enumerable.Range(0,100).Select(i => landmarkTuple[i]) },
Did not count the chin points, 100 is just for example.
Also in PredictorModel.Helen you do not use .ToArray()
See PredictorModel.Large and  PredictorModel.Small uses  .ToArray()  at the end of the statement.
{ FacePart.Chin,         Enumerable.Range(0,17).Select(i => landmarkTuple[i]).ToArray() },

I think your provided image (on first comment) is generated by HelenTraining demo command.
In this demo command, does NOT use FaceRecognition.FaceLandmark method to draw face part number like your image.
This code is the part of HelenTraining demo command process.
                    using (var predictor = ShapePredictor.Deserialize(modelFile))
                    using (var image = FaceRecognition.LoadImageFile(imageFile))
                    using (var mat = Dlib.LoadImageAsMatrix<RgbPixel>(imageFile))
                    using (var bitmap = (Bitmap)System.Drawing.Image.FromFile(imageFile))
                    using (var white = new Bitmap(bitmap.Width, bitmap.Height))
                    using (var g = Graphics.FromImage(bitmap))
                    using (var gw = Graphics.FromImage(white))
                    {
                        var loc = _FaceRecognition.FaceLocations(image).FirstOrDefault();
                        if (loc == null)
                        {
                            Console.WriteLine("No face is detected");
                            return 0;
                        }

                        var b = new DlibDotNet.Rectangle(loc.Left, loc.Top, loc.Right, loc.Bottom);
                        var detection = predictor.Detect(mat, b);

                        using (var p = new Pen(Color.Red, bitmap.Width / 200f))
                        {
                            g.DrawRectangle(p, loc.Left, b.Top, b.Width, b.Height);
                            gw.Clear(Color.White);
                            gw.DrawRectangle(p, loc.Left, b.Top, b.Width, b.Height);
                        }

                        for (int i = 0, parts = (int)detection.Parts; i < parts; i++)
                        {
                            var part = detection.GetPart((uint)i);
                            g.FillEllipse(Brushes.GreenYellow, part.X, part.Y, 15, 15);
                            gw.DrawString($"{i}", SystemFonts.DefaultFont, Brushes.Black, part.X, part.Y);
                        }

                        bitmap.Save("demo.jpg", ImageFormat.Jpeg);
                        white.Save("white.jpg", ImageFormat.Jpeg);

The part number of your image is drawn from gw object.
Please look at detection object which comes from predictor.Detect rather than FaceRecogniton object.
predictor is generated from Deserialzie method of DlibDotNet and source is trained model file.
Yes, this strange index comes from raw result of dlib. Not comes from FaceRecognition.FaceLandmark you pointed out on the avove your comment.

Memo
Training parameter may have difference between python anc c++.

https://github.com/davisking/dlib/blob/master/tools/python/src/shape_predictor.h
https://github.com/davisking/dlib/blob/master/dlib/image_processing/shape_predictor_trainer_abstract.h

Should we check default parameter?

did you had a chance to look into it? i am still lost. it is hard for me to understand what is going on and where to look for a fix.

I referred this blog.
https://qiita.com/kekeho/items/0b2d4ed5192a4c90a0ac
This blog uses python but it works fine.
So it may help us.

The example from the blog has the same issue. There is a "fix" script in the comments that remaps the indexes. That is also what i had already in mind but it feels pretty dirty.
The last comment gave me bit hope though. It states that the issue can be resolved by padding the name attribute with zeros (trailing zeros).
I tried this and have generated xml data like this:
<part x="565" y="758" name="000" /><part x="564" y="781" name="001" /> and so on..
Following this i trained again and run the HelenTraining demo code but no luck :(
The issue persists  :(

name attribute could be first item.
https://github.com/davisking/dlib/blob/fc6992ac0422acdaba77cdb07678605ca60f6321/dlib/data_io/image_dataset_metadata.cpp#L105
and patrs is std::map and it could be sorted by key.
https://github.com/davisking/dlib/blob/fc6992ac0422acdaba77cdb07678605ca60f6321/dlib/data_io/image_dataset_metadata.h#L70
so I thought your fix should resolve but isuue remain.

@tgd-git
I added 0 padding to name attribute and it works fine.
And I used latest DlibDotNet but it should affect nothing.
- parts.Add(new Part { X = tmp[0], Y = tmp[1], Name = $"{i - 1}" });
+ parts.Add(new Part { X = tmp[0], Y = tmp[1], Name = $"{i - 1:D3}" });

dotnet run -c Release -- demo --model helen\helen-dataset.dat --directory models --image helen\helen_1\100040721_2.jpg

The last comment gave me bit hope though. It states that the issue can be resolved by padding the name attribute with zeros (leading zeros).

I don't understand why your modification does not work.
I modified source code and did generate, train and demo command.

Well it works here too, just tried again. My bad. It seems i have mixed up the model files when i tried yesterday (have trained the correct new one but used the old one when i run the demo) super facepalm! :)
Anyway, very happy we figured it out and it works now. Big thanks for your support!

Good.
OK, I will publish new nuget package after testing.

I released FaceRecignitionDotNet 1.2.3.14.
Have a try

authors: takuya-takeuchi tgd-git

repo: takuya-takeuchi/FaceRecognitionDotNet


text:
default /admin route error if dashboard page renamed

I renamed a the dashboard page to info. I get an error could not render "dashboard.html".

With update c277edb, the work around  is to override the page/2 action in your page controller and change the default like this:
defmodule MyApp.Web.TalonPageController do
  # ...
  def page(conn, params) do
    page = Map.get(params, "page", "info") # default will be the info page.
    render(conn, "#{page}.html")
  end
end

@dsnider I did some investigation into our options for handling the default /admin route. I was not able to find the topic I saw in the past, nor could I find out how to set the params inside a match.
I believe we could do this with a plug, but I'm not sure that's the best option.
I believe the best approach would be to have a controller in Talon (not in the project space to handle this specific case. That controller action could look at possible configuration (don't know where to put that) and if not found, then search in the following order. first page, first resource, some text indicating that no pages/resource have been configured.
If a page or resource is found, the action can just call the action on the appropriate controller after setting up the params correctly.

Bummer. I tried for a while to get that to work to no avail. It would be ideal to have this handled there.
What I was doing previously was routing to :dashboard action on page controller. Perhaps :default or :root would have been a better action name. That same approach could be a work around above -- instead of overriding page, add a :default or :root action then route to that and prime the :page param there.
I like the idea of a policy for looking up a default page. I'm not sure if it should a resource should be a default candidate, though. That might be confusing? Not sure.  Also, is it considered bad form in Phoenix to call the action of another controller directly?
Adding a DefaultController or RootController would work, but I'd prefer to have an easy way to override the policy. If we only create in Talon space, changing the policy wouldn't be as obvious.
Perhaps PageController could handle this similar to what I was doing before? Add a :default or :root action and route "/" to that action. The default policy looks for the first defined page or generates some placeholder. This gives the user an easy hook to override in TalonPageController. We could even generate a boiler plate example of such an override that points to a resource.

The problem is that a project may not have a page controller. It may not even have a resource controller. I think it would be nice to still be able to render a page with instructions on adding a page or resource.
Your right, calling an action from a controller in Talon will not work. Not because its bad form, but we would be bypassing the plugs for the controller.
We could use the talon_routes macro to generate the route based on the pages/resources configuration. And the user can override this by adding their own "/admin" route.

@smpallen99 does PR #73 address your original problem of changing the dashboard to info? After doing the appropriate renames, it appears to work for me. See below.

We could use the talon_routes macro to generate the route based on the pages/resources configuration. And the user can override this by adding their own "/admin" route.

Are you saying to remove  get "/", TalonPageController, :index from our Talon Router and put the onus on the user?

Yes Dan. I tried it this morning and worked fine. Also nice that I only had to rename the template directory, and not the template itself.

Okay, I'm closing this but see #79.

repo: talonframework/talon


text:
add package and dependencies property for cargo.toml

Add two property "workspace.dependencies" and "workspace.package".
The description is got from "https://github.com/rust-lang/cargo/blob/211fd7eac105f0960433a935ce17b8d787233692/src/doc/src/reference/workspaces.md?plain=1", and replace \n and \", kind of stupid.

I found this: https://github.com/SchemaStore/schemastore/blob/master/src/schemas/json/cargo.json
Obviously it's a fork of this file, maybe we could take something back?

Thanks for your PR! However this file is not used anymore and only kept for documentation on the website. Taplo now uses JSON Schema Store as you referenced in your second post. I'm closing the PR as WAI (working as intended).

repo: tamasfe/taplo


text:
New arXiv paper(s) about privacy-preserving explainable AI

Towards a Game-theoretic Understanding of Explanation-based Membership Inference Attacks
https://arxiv.org/abs/2404.07139

The Effect of Data Poisoning on Counterfactual Explanations
https://arxiv.org/abs/2402.08290

repo: tamlhp/awesome-privex


text:
Optional alpha parameter for draw groups

This PR adds a new alpha parameter inside several draw group contexts. It allows the scene author to set only the alpha channel of a color, independently of the RGB channels.
Use cases where this is helpful include:

Modifying the alpha for named CSS colors
Modifying the alpha channel in a sub-layer, which can simplify complex layer trees or help with cases where you may be importing/overriding another style, or applying "themes" that change the underlying base colors
Using a feature property to set the color, but then modifying only the alpha (note, this was not easily achievable before in cases where a feature property might contain a hex or CSS named color), e.g. use transit line colors encoded in tiles, but draw lines at 75% opacity

Syntax

Applies to the following styles in draw groups, where the alpha parameter, if present, will override the alpha channel set by the corresponding color parameter:

polygons:

polygon fill color: color
example:

translucent_polygons:
  color: red
  alpha: 0.5 # red polygon with 50% opacity

lines:

line fill color: color
outline color (inside outline block): color
example:

 overlay_lines:
   color: function() { return feature.colour_name; }
   alpha: 0.75 # color by a feature property but set 75% opacity

points:

point fill color: color
outline color (inside outline block): color
font fill/stroke for attached labels as described below, inside a text block
example:

# points with a 25% opacity yellow fill, and a 50% opacity blue outline
points:
  color: yellow
  alpha: 0.25
  outline:
    color: blue
    alpha: 0.5
    width: 4px

text

font fill color (inside font block): fill
font stroke color (inside font.stroke block): color
example:

text:
  font:
    fill: black
    alpha: 0.5 # black fill with 50 opacity%
    stroke: { color: red, alpha: 0.25 } # red stroke with 25% opacity

alpha values can be set by:

Single value: alpha: 0.5
Zoom interpolated values: alpha: [[14, 0.5], [16, 1]] (fade in opacity from z14-16)
JS function: alpha: function(){ return feature.height/200; } (set building opacity by height)

In cases where a color value is required, the alpha parameter has no effect if no color is specified. In cases where a default color applies, the alpha parameter will modify the default color if no color is specified.
The alpha parameter inherits through sub-layers like any other draw parameter, and does not need to be defined at the same depth as a color it modifies; it will modify the nearest ancestor layer where color is defined.depth1:
  draw:
    points: { color: red, alpha: 0.5} # these features render w/color [1, 0, 0, 0.5]

  depth2:
    draw:
      points: { alpha: 0.25 } # these features render w/color [1, 0, 0, 0.25]

As with other parameters, it is not additive or compounding across layers: in the example, any features rendered at depth2 will have 25% alpha (no interaction with the 50% value from the parent layer).
If a sub-layer sets alpha: null, it un-sets any value set by an ancestor layer. The color's alpha channel returns to its original, unmodified value.depth1:
  draw:
    points: { color: red, alpha: 0.5} # these features render w/color [1, 0, 0, 0.5]

  depth2:
    draw:
      points: { alpha: null } # these features render w/full opacity, color [1, 0, 0, 1]

NOTE: for polygons and lines, alpha channel is only applicable for appropriate blend modes (translucent, overlay, etc.), and is not intended to be used with the default opaque blending.

It's possible the alpha support for font fill and stroke is overkill, though it led to me having some fun with fonts... :D

cc @matteblair @meetar @sensescape @burritojustice @nvkelso @tallytalwar for comment.

@bcamper Looks great from here! Couple of questions about the PR description:

In cases where a color value is required, the alpha parameter has no effect if no color is specified.
This is because nothing will draw, correct? So this line is clarifying that there won't be some kind of default color applied in order to apply an alpha to it.

If a sub-layer sets alpha: null, it un-sets any value set by an ancestor layer. The color's alpha channel returns to its original, unmodified value.
Are there cases where the "original unmodifed value" could be something other than 1.0?

@meetar:

In cases where a color value is required, the alpha parameter has no effect if no color is specified.

This is because nothing will draw, correct? So this line is clarifying that there won't be some kind of default color applied in order to apply an alpha to it.

Yep, that's right, feel free to help clarify the language if you have suggestions.

If a sub-layer sets alpha: null, it un-sets any value set by an ancestor layer. The color's alpha channel returns to its original, unmodified value.

Are there cases where the "original unmodifed value" could be something other than 1.0?

For sure! Any time color sets an alpha already, like this:
depth1:
  draw:
    points:
      color: [1, 0, 0, 0.25] # renders at 25% opacity

  depth2:
    draw:
      points:
        alpha: 0.5 # overrides color, renders at 50% opacity

    depth3:
      draw:
        points:
          alpha: null # back to the original 25% opacity

I should have put in an example where it is very explicitly overriding, even at one level, like:
  draw:
    points:
      color: [1, 0, 0, 0.25]
      alpha: 0.5 # overrides color, features will render w/50% opacity

Basically, whenever alpha is present, it overrides the color alpha. All the other behavior, including the alpha: null "un-set", falls out of the regular draw group and import merging (because an explicitly set null gets merged on top of others, like any other value).

Again, 👏 on the great description @bcamper. Sorry couldn't jump on this before. But looks good to me too.

authors: bcamper meetar tallytalwar

repo: tangrams/tangram


text:
Incompatible with optimistdigital / nova-sortable

Hi @tanmuhittin, first of all, thanks for your great package!
I'm trying to use nova-left-resource-index with nova-sortable without success.
Thanks in advance!

Me to

Me to

authors: newtongamajr yarbala


text:
[2.24.0] cacheTime: Infinity in useQuery() doesn't work properly

Hi,
I'm using Next.js and try to upgrade v2.24.0, cacheTime: Infinity doesn't seem to work properly.
const cache = new QueryCache();

const client = new QueryClient({
  cache,
  defaultOptions: {
    queries: {
    // Empty here
    }
  }
});

MyApp.getInitialProps = async () => {
  await client.prefetchQuery(
          'posts',
          () => {
            return Promise.resolve("my sample data");
          },
          {
            cacheTime: Infinity,
          },
   );
}

Somewhere
const posts = client.getQueryData('posts');

To Reproduce
https://codesandbox.io/s/intelligent-edison-9ddd1?file=/pages/_app.js
Steps to reproduce the behavior:

Click About link
Click Home link
Way 5 minutes
Switch About and Home
Again step 4
Data will be lost

Additional context
Maybe the problem only happens when defaultOptions.queries is empty.

Think what is happening here is that the Infinity value gets lost while serializing to JSON. Maybe we should add some support for these kind of values, like serialize to 2147483648 and then deserialize to Infinity again.

Isn't it more common to use e.g. -1 as Infinity in these types of cases?

But v2.23 work fine 😺
p/s: What performant if Number.MAX_SAFE_INTEGER instead of Infinity

Maybe -1 would indeed be better as the value should never be negative. Think v2.23 has the same issue, but in that version it falls back to the defaultConfig on the queryCache, while it doesn't in v2.24.

Infinite cache times should be serialized correctly in v2.24.1

Also added support for providing default options when hydrating :) Closing this issue

Hey @boschni
Maybe the 3.2.0 version and above. The issue seems to have come back again.
Reproduction (v3.4.0) https://codesandbox.io/s/infallible-meadow-7e8y1?file=/pages/_app.js

Hi @nghiepit! The cache time is not hydrated anymore, this allows server and client to use different cache times. Would it be an option to set an infinite cache time in the client?

Yeah, I want to cache my data infinite. And I don't want to re-fetch these data again in the client.

@boschni
Yeah, I want to cache my data infinite. And I don't want to re-fetch these data again in the client.

What if you set:
const client = new QueryClient({
  defaultOptions: {
    queries: {
      cacheTime: Infinity
    }
  }
});

No, Just specific data want to do apply infinite cache.

With staleTime you can define when something needs to be refetched. Would that be useful in your case?

Actually, I am also confusedstaleTime about usage 😭

Tks @boschni staleTime resolved my issue.

authors: Svish boschni nghiepit nghieptiki

repo: tannerlinsley/react-query


text:
error in useGroupBy in ^7.0.0-rc.6 Version

I am making the application which shows the data using useGroupBy and useExpanded and the data changes as user click the option to show result by month or year. After changing this option the table is not performing grouping and its shows all info in expanded. I think so there is a bug in this version ^7.0.0-rc.6 because it was working with ^7.0.0-rc.1

https://github.com/tannerlinsley/react-table/commit/9de699bfd3a12bc8884ec467f72bf93e29e68ff6#commitcomment-36361269

I believe this should be fixed in the latest version. If not, please comment with more info and we'll reopen.

@tannerlinsley sure thank you so much I really appreciated for your help

@tannerlinsley still the issue is not fixed in the new version

Weird. Would you be able to make a new code sandbox that shows this issue? That will help me the debug better

@tannerlinsley sure I will try my best to make later this week. Thank you so much for your help I really appreciated it.

repo: tannerlinsley/react-table


text:
TaosResult.row_count  seems to always be 0.

不管结果集中是否有数据，TaosResult.row_count 一直是 0。TaosResult.field_count 正常。
版本 2.2.1

taos/result.py shows TaosResult.row_count was assigned in TaosResult.fetch_all(), it would be good if row_count is available before calling fetch_all().

Thanks for the feedback. We'll take a look.

taos/result.py shows TaosResult.row_count was assigned in TaosResult.fetch_all(), it would be good if row_count is available before calling fetch_all().

It's  not possible for now due to the design of  the client library.

repo: taosdata/taos-connector-python


text:
Tic Tac Toe update

Added colors and cleaning the screen after each round in the tic tac toe game.

Congratulations for your first pull request merged on GitHub! 🚀 You can check out this for more issues to work on.

authors: Albisett tapasweni-pathak

repo: tapasweni-pathak/Games


text:
task/TUI-5 Production Webpack

Overview:
Production webpack. Run npm run build. Output static files will be stored in ./build, with asset root set to /
Related Github Issues:

TUI-5

Summary of Changes:

Configure webpack.prod.js
Package-lock updated

Testing Steps:

Delete all node_modules
Delete client/build
npm install
npm run build
In the ./build directory, start a local server with python3 -m http.server
Browse to localhost:8000

UI Photos:
Notes:

LGTM - Builds without any issues.

authors: Strmiska jchuahtacc

repo: tapis-project/tapis-ui


text:
feat: Remove rcfile from --dump-config

The --dump-config command also dumped the rcfile command also which would not make sense to have in the .taprc file, wouldn't it? It would create a kind of recursion or twilight zone?
Instead we print the path to the .taprc now as first line of the dump.
This also fixes the dump-config tests for Windows.
Since we now print the path to the .taprc file on the console, on Windows this path contained backslashes.
They are sanitized in the clean function.

Any thoughts on that @isaacs?

Rebasing this gave me like 30 failing tests now. Please let me know if you consider merging this PR (its already 2 months old without any comment) or I can save my time to investigate those failings.

Sorry for the delay.

The --dump-config command also dumped the rcfile command also which would not make sense to have in the .taprc file, wouldn't it? It would create a kind of recursion or twilight zone?

So this made sense to me at first, but what if you're running tap --dump-config specifically to see what rcfile you're using?  It seems a bit weird to dump tap --dump-config directly into an rcfile without at least checking to make sure you'er not just saving some defaults, no?

It's OK. I've moved to jest for all of my tests in the meantime.

authors: isaacs pke

repo: tapjs/node-tap

license: isc


text:
Do not patch the global child_process module

Hi,
I'm currently looking at providing a Node API for c8, a code coverage tool using V8's Profiler.
The current code uses spawn-wrap. Since spawn-wrap modifies the global child_process module, it is not safe to use it in a library: concurrent code trying to spawn processes will have unexpected results. This prevents running multiple coverages in parallel, or coverage and some other consumer tasks, inside the same Node process.
The current workaround would be to run each instance of c8 in its own process (independent child_process). This is very heavy-handed: it introduces friction and hurts composability. It means that the API must communicate with a subprocess so only serializable messages can be sent.
I propose to do something similar to graceful-fs@4. The version 3 modified the global fs module while version 4 only returned a wrapper.
Here is what the updated API would look like:
// Default to safe version (breaking change)
module.exports = safeWrap;
// Alias so the API can be a simple namespace
module.exports.wrap = safeWrap;
// Keep the old behavior available to ease transition, eventually mark as deprecated?
module.exports.wrapGlobal = wrap;
// Helper function to know if the global child_process is currently wrapped
module.exports.isGlobalWrapped = ...;

safeWrap(options) {
  const spawn = ...;
  const spawnSync = ...;
  // Start with a subset of the `child_process` API,
  // eventually extend it to return a full `child_process`-like object.
  return {spawn, spawnSync};
}

// We could also imagine a function like "wrapify` similar to "gracefulify"
// You can pass it a `child_process`-like object and it would mutate it
// by adding the wrappers in-place.

As stated in the example, this would introduce a breaking change but I believe that it would bring better behavior. The old behavior would still be accessible so transition would be easy.
The breaking change would also be the occasion to require Node 4+: there are other comments/issues mentioning problems with older Node versions. It would also simplify the current feature-detection mechanisms. This is not my main point though, I'm just proposing it by the way
What is needed is a way to spawn concurrent process-trees that do not interfere with each other, without isolating each root in its own sub-process.

By thinking more about the use cases of nyc and c8, I was thinking that a better API would be to use an event emitter to handle spawned subprocesses rather than patching the child_process module. (https://github.com/tapjs/spawn-wrap/issues/47#issuecomment-411664150)
This could be achieved with some light IPC between the root process and its descendants.

I did some refactoring this week-end to reorganize the code from a single module to smaller chunks. It fixed some small issues, but especially allowed me to get a clear picture of how the module works by untangling some parts (especially the setup/shim creation from from the internals patching).
Adding support for local wrappers should be possible soon. The only thing missing is to have mungers working on the cp.spawn and cp.spawnSync arguments, not the internal spawn options. I initially tried to reuse them by pulling a bit of code from the Node lib, but there are just too much internal dependencies to copy here if we want to reuse the patch for the internal spawn functions. Working at the high-level functions means that we need to support the complex signature of these functions but it allows to wrap custom child_process implementations later one.
The next feature is term of difficulty would be to run the main module and wrapper in their own processes. This would fix the issue where the wrapper's flags are leaking into the original main (for example --require foo/register or when a process.exit in the original main prevents the wrapper from completing.
Finally, the event-emitter based API is still a goal for me. This is the best API responding to the problem solved by this lib. It's also the hardest feature to implement. It will require to add some IPC (as mentioned) and a class acting as a ChildProcess proxy. The wrapper would spawn the original main and forward events and calls between the spawn process and the root.

repo: tapjs/spawn-wrap


text:
Lorri starts nix-builds in a loop

I've started using lorri from tip of master because of the SSL issues in earlier builds and some other fixes. Since then I've seen my cpu usage spike a lot. Afaict it is lorri, launching nix-builds over and over again. This happens very often, probably several times an hour. I end up restarting lorri which gets rid of those builds (for a while), here's an excerpt from the systemd journal:
-- Logs begin at Sat 2019-04-27 23:44:07 CEST. --
Oct 16 14:01:47 europa lorri[923]:     BuildResults {
Oct 16 14:01:47 europa lorri[923]:         output_paths: OutputPaths {
Oct 16 14:01:47 europa lorri[923]:             shell_gc_root: RootPath(
Oct 16 14:01:47 europa lorri[923]:                 "/home/john/.cache/lorri/gc_roots/3f193d3e7cddce96a26099d2979cb202/gc_root/shell_gc_root"
Oct 16 14:01:47 europa lorri[923]:             )
Oct 16 14:01:47 europa lorri[923]:         }
Oct 16 14:01:47 europa lorri[923]:     }
Oct 16 14:01:47 europa lorri[923]: )
Oct 16 14:01:47 europa lorri[923]: Started
Oct 16 14:01:47 europa nix-daemon[8151]: accepted connection from pid 15039, user john (trusted)
Oct 16 14:01:48 europa lorri[923]: Completed(
Oct 16 14:01:48 europa lorri[923]:     BuildResults {
Oct 16 14:01:48 europa lorri[923]:         output_paths: OutputPaths {
Oct 16 14:01:48 europa lorri[923]:             shell_gc_root: RootPath(
Oct 16 14:01:48 europa lorri[923]:                 "/home/john/.cache/lorri/gc_roots/3f193d3e7cddce96a26099d2979cb202/gc_root/shell_gc_root"
Oct 16 14:01:48 europa lorri[923]:             )
Oct 16 14:01:48 europa lorri[923]:         }
Oct 16 14:01:48 europa lorri[923]:     }
Oct 16 14:01:48 europa lorri[923]: )
Oct 16 14:01:48 europa lorri[923]: Started
Oct 16 14:01:48 europa nix-daemon[8151]: accepted connection from pid 15052, user john (trusted)
Oct 16 14:01:49 europa lorri[923]: Completed(
Oct 16 14:01:49 europa lorri[923]:     BuildResults {
Oct 16 14:01:49 europa lorri[923]:         output_paths: OutputPaths {
Oct 16 14:01:49 europa lorri[923]:             shell_gc_root: RootPath(
Oct 16 14:01:49 europa lorri[923]:                 "/home/john/.cache/lorri/gc_roots/3f193d3e7cddce96a26099d2979cb202/gc_root/shell_gc_root"
Oct 16 14:01:49 europa lorri[923]:             )
Oct 16 14:01:49 europa lorri[923]:         }
Oct 16 14:01:49 europa lorri[923]:     }
Oct 16 14:01:49 europa lorri[923]: )
Oct 16 14:01:49 europa lorri[923]: Started
Oct 16 14:01:49 europa nix-daemon[8151]: accepted connection from pid 15065, user john (trusted)
Oct 16 14:01:49 europa lorri[923]: Completed(
Oct 16 14:01:49 europa lorri[923]:     BuildResults {
Oct 16 14:01:49 europa lorri[923]:         output_paths: OutputPaths {
Oct 16 14:01:49 europa lorri[923]:             shell_gc_root: RootPath(
Oct 16 14:01:49 europa lorri[923]:                 "/home/john/.cache/lorri/gc_roots/3f193d3e7cddce96a26099d2979cb202/gc_root/shell_gc_root"
Oct 16 14:01:49 europa lorri[923]:             )

I'm able to easily reproduce this by

killing lorri
cd to a direnv dir
wait for lorri to finish and direnv to source env
cd out
cd into a different direnv enable dir
lorri runs a build
lorri starts to loop running of builds of things its been told to watch

I've noticed that when the loop starts going wrong Started is logged twice
> ~> journalctl --user -fu lorri.service | grep -e 'Started\s*$' -e gc_roots
Oct 28 15:51:24: Started
Oct 28 15:51:27:                 "/home/manny/.cache/lorri/gc_roots/fdf0f8d1169cdb49581245fd32ab921a/gc_root/shell_gc_root"
Oct 28 15:51:33: Started
Oct 28 15:51:33: Started
Oct 28 15:51:34:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:35: Started
Oct 28 15:51:35:                 "/home/manny/.cache/lorri/gc_roots/fdf0f8d1169cdb49581245fd32ab921a/gc_root/shell_gc_root"
Oct 28 15:51:35: Started
Oct 28 15:51:37:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:37: Started
Oct 28 15:51:38: Started
Oct 28 15:51:38:                 "/home/manny/.cache/lorri/gc_roots/fdf0f8d1169cdb49581245fd32ab921a/gc_root/shell_gc_root"
Oct 28 15:51:38: Started
Oct 28 15:51:38:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:38: Started
Oct 28 15:51:39:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:39: Started
Oct 28 15:51:39:                 "/home/manny/.cache/lorri/gc_roots/0395f4221b81258ed77b68e21324cddc/gc_root/shell_gc_root"
Oct 28 15:51:40: Started
Oct 28 15:51:40:                 "/home/manny/.cache/lorri/gc_roots/fdf0f8d1169cdb49581245fd32ab921a/gc_root/shell_gc_root"
Oct 28 15:51:40: Started
Oct 28 15:51:40:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:40: Started
Oct 28 15:51:42:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:42: Started
Oct 28 15:51:42:                 "/home/manny/.cache/lorri/gc_roots/0395f4221b81258ed77b68e21324cddc/gc_root/shell_gc_root"
Oct 28 15:51:42: Started
Oct 28 15:51:43:                 "/home/manny/.cache/lorri/gc_roots/fdf0f8d1169cdb49581245fd32ab921a/gc_root/shell_gc_root"
Oct 28 15:51:43: Started
Oct 28 15:51:43:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:43: Started
Oct 28 15:51:44:                 "/home/manny/.cache/lorri/gc_roots/0395f4221b81258ed77b68e21324cddc/gc_root/shell_gc_root"
Oct 28 15:51:44: Started
Oct 28 15:51:44:                 "/home/manny/.cache/lorri/gc_roots/14d16d2f4ecfaaad1d2305ac8b6280b4/gc_root/shell_gc_root"
Oct 28 15:51:44: Started
Oct 28 15:51:45:                 "/home/manny/.cache/lorri/gc_roots/fdf0f8d1169cdb49581245fd32ab921a/gc_root/shell_gc_root"
Oct 28 15:51:45: Started
Oct 28 15:51:45:                 "/home/manny/.cache/lorri/gc_roots/0395f4221b81258ed77b68e21324cddc/gc_root/shell_gc_root"

Note that every time a Started is logged twice has been a result of cd'ing into a new un-watched dir after the initial directory.

I've been debugging what I am pretty sure is the same issue independently, and I believe I've found the cause. It's a combination of a few things:

Nix spams chmod on some per-user paths on each build.
Lorri only filters FS events based on path, without regard to whether or not those events actually constitute an "interesting" change that should trigger a rebuild.
I think Lorri is queuing up events that occur during builds, and then processing/draining them afterward.

The net effect is that if a build is dependent on, say, /nix/var/nix/profiles/per-user/root, a single build being triggered will result in multiple chmods being spammed against that very path, which will enter Lorri's event queue, which will sit there until Lorri finishes the build, at which point it will process them and immediately kick off another build in response, which will cause Nix to spam chmods again... repeat ad infinitum.
I'm regularly seeing this happen with only a single lorri instance, watching a single project, and it triggers a fresh nix-build every few seconds (because the build results are cached, I assume).

@Shados That seems to describe my issue quite well. I don't have to switch directory, this starts happening pretty much reliably - it's not difficult to reproduce, rather the opposite. In fact, in my case, so common that I currently don't use lorri.

This is happening to me too. Seems to be very reproducible.

It's also /nix/var/nix/profiles/per-user/root for me - I don't know why lorri thinks it needs to watch that, though.

It's also /nix/var/nix/profiles/per-user/root for me - I don't know why lorri thinks it needs to watch that, though.

If you're using <nixpkgs> and nixpkgs comes from the root user's channel, it watches /nix/var/nix/profiles/per-user/root to be able to trigger a new evaluation when your channel updates.

We don't use <nixpkgs>: the nix-instantiate call used by lorri completes with NIX_PATH unset. So I don't know where it's getting that from.

I found out why it's happening for us!
We use niv, and this line tries to eval <nixpkgs>. You still get good behaviour if it fails, which is why I could run things with NIX_PATH unset, but presumably this causes lorri to watch it.
Of course, even if you do use nixpkgs, lorri shouldn't loop, so this issue is still valid, but I'll open an issue in niv to fix this.

We use niv, and this line tries to eval <nixpkgs>. You still get good behaviour if it fails, which is why I could run things with NIX_PATH unset, but presumably this causes lorri to watch it.

Too much magic will kill you. cc @nmattia

When trying to solve my issue I tested adding a user channel so that  would not point to /nix/var/nix/profiles/per-user/root and now I don't get these rebuild loops that use up my cpu and drives me crazy. Otoh I don't believe this should be a requirement of lorri.
This "fix" also forces me to upgrade my nixpkgs separately from my NixOS install. That may not be what people want but they'd rather like them to be upgraded together (if you don't have a user channel you default to whatever the system is using).
As @Shados mentions above - it seems to be a chmod call normally that triggers a rebuild which triggers a chmod call which... etc.

This has also been mildly frustrating for me too, as I happen to work on a few projects that are reproducers of this behavior. I think the correct answer is to ignore metadata modification events for paths starting with /nix/var/nix/profiles/per-user, as these are the paths that are chmoded unconditionally.
I also noticed that updating an unrelated channel can similarly trigger a build using the same mechanism, as updating the channel link of say home-manager will cause nix to re-chmod the user's per-user profile directory.
I'll be submitting a patch to change the behavior to what I think is the correct answer shortly.

starting with /nix/var/nix/profiles/per-user, as these are the paths that are chmoded unconditionally.

Oh! That’s something lorri itself is doing. We can fix that.

@Profpatsch Could you expand on that? I'm not finding any set_permissions calls within the code.

To confirm for myself, I traced this locally, and I think the nix-daemon is doing the chmod:
$ sudo bpftrace -e tracepoint:syscalls:sys_enter_chmod { printf("%s: %s\n", comm, str(args->filename)) }

Attaching 1 probe...
nix-daemon: /nix/var/nix/profiles/per-user
nix-daemon: /nix/var/nix/gcroots/per-user
nix-daemon: /nix/var/nix/profiles/per-user/root
nix-daemon: /nix/var/nix/gcroots/per-user/root
nix-daemon: /nix/var/nix/profiles/per-user/jimmy
nix-daemon: /nix/var/nix/gcroots/per-user/jimmy

Just ran the same trace without lorri running, and building my reproducer without --add-root, and it still does those chmods at the beginning of the nix build. This implies that we can't modify lorri to prevent the nix-daemon from calling chmod, unfortunately.

Okay, then I misremembered. We only create the per-user gcroots dir when it doesn’t exist already.

authors: Profpatsch Shados grahamc johnae michaelpj mmlb theotherjimmy

repo: target/lorri


text:
Lorri broken prompt on nested shells, bash vs bashInteractive and its cohort of issues

See also https://github.com/NixOS/nixpkgs/issues/59209#issuecomment-617103619 , running shells in direnv+Lorri on NixOS runs into the usual bash vs bashInteractive issues with broken prompts.
It can be worked around by adding bashInteractive to the mkShell.

I also got this issue on NixOS
.envrc:
eval "$(lorri direnv)"
layout python2

shell.nix
let
  pkgs = import <nixpkgs> {};
in
pkgs.mkShell {
  shellHook = ''
    unset SOURCE_DATE_EPOCH
  '';
}

when I run a nested bash inside the direnv+Lorri bash, I got a broken prompt:
$ bash
complete: command not found
bind: command not found
bind: command not found
bash: set: vi: invalid option name
\[\]\[\] impure \[\]\[\]\[\]\[\]\[\] ~ \[\]\[\]\[\]\[\]\[\] \[\]\[\]\[\]\[\]\[\] … \[\]\[\]\[\]\[\]\[\] $

@deliciouslytyped  really appreciate if you could show more details about the workaround

let
  pkgs = import <nixpkgs> {};
in
pkgs.mkShell {
  shellHook = ''
    unset SOURCE_DATE_EPOCH
  '';
  buildInputs = [ pkgs.bashInteractive ];
}

should work around this.
Actually I think we should add that to the default shell.nix we generate, since it’s a known problem.

authors: Profpatsch deliciouslytyped kaleocheng


text:
Request: Steps to deploy to Heroku

Hello,
Tarlepp, you're doing a wonderful job by posting this boiler plate code. I was able to deploy the backend part to Heroku properly. But I'm not sure how the frontend can be properly deployed on Heroku. I'm relatively new to Gulp. If you can help with some steps to deploy to Heroku, that will be great.
Warm Regards!

@anupsarode Did you get Heroku deplo working? If yes, could you provide PR that contains detailed information about that?

Any updates?

@anupsarode ^up

Hello,
I got it up and running on Heroku. Following are the steps.

In the sails project, install forever module

$ sudo npm install forever --save

Create a Procfile in the projects root folder with following copy in it

web: ./node_modules/.bin/forever app.js

Create an App in Heroku Dashboard and Login to Heroku in Terminal

$ heroku login

Clone the repo to the local machine

$ heroku git:clone -a
$ cd

Deploy the changes from local machine to Heroku

$ git add .
$ git commit -am "Initial Commit"
$ git push heroku master

Test

$ heroku open

@anupsarode thanks for the info, closing this now.

authors: anupsarode tarlepp

repo: tarlepp/angular-sailsjs-boilerplate


text:
routing_missing_exception

I try to import data with command "elasticdump --input=http://ip1:9200/movie --output=http://ip2:9200/movie --type=data",  there are two types in index, one parent type and the other is child type.  I hava a exception "routing_missing_exception" .

ElasticDump version  3.3.19
Elasticsearch 2.4.0

What's the source ES version and destination ES version
Can you provide sample data ?

Closing this issue due to lack of activity.

Usually happens when the routing meta-field is missing

authors: ferronrsmith qcqAllen

repo: taskrabbit/elasticsearch-dump


text:
fix(clipboard-manager): read_image wrongly set the image rgba data with binary PNG data.

fix #1985
The dependency of image crate may be unnecessary now. I'm not sure whether it should be removed.

The dependency of image crate may be unnecessary now. I'm not sure whether it should be removed.

yeah looks like it, feel free to remove it

Could you add a change file in .changes directory? also you need to run cargo fmt

OK! I think I finished. Could you kindly approval another check workflow?

thank you

authors: RikaKagurasaka amrbashir

repo: tauri-apps/plugins-workspace


text:
[bug] Run Project Tauri + React in Windows 11, the screen display nothing

Describe the bug
I run a project using Tauri and React, I code in VSCode in normally, one day I run project and run command "npm run tauri dev", the project run the same but the screen I display nothing, I found no error both in Tauri console log and Screen console log
How can I found the cause of this issue

Reproduction
No response
Expected behavior
No response
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 129.0.2792.52
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.80.1 (3f5fd8dd4 2024-08-06)
    ✔ cargo: 1.80.1 (376290515 2024-07-16)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 18.15.0
    - npm: 9.5.0

[-] Packages
    - tauri [RUST]: 1.7.2
    - tauri-build [RUST]: 1.5.4
    - wry [RUST]: 0.24.10
    - tao [RUST]: 0.16.9
    - tauri-cli [RUST]: 1.6.0
    - @tauri-apps/api [NPM]: 1.6.0
    - @tauri-apps/cli [NPM]: 1.6.1 (outdated, latest: 1.6.2)

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: React
    - bundler: Vite

Stack trace
No response
Additional context
No response

Make sure that the next server is running on the same port configured in tauri.conf.json.
Replace your root React component in main.jsx/main.tsx with a simple <h1> hello world </h1>
Comment out your components one by one

If none of these work, please make a minimal repro and I will take a look

Navigate to the devServer url on your browser and see if it works
Make sure that the next server is running on the same port configured in tauri.conf.json.
Replace your root React component in main.jsx/main.tsx with a simple <h1> hello world </h1>
Comment out your components one by one

If none of these work, please make a minimal repro and I will take a look

I also have the same issue on tauri 2.0.0-rc.15. My server and GUI were running fine yesterday, and today I encountered this issue with no changes. I rolled back to old changes and I am still getting the error. The GUI shows on WSL just fine as well. I also followed what you have mentioned in your comment.
The root React component will show hello world when replaced, but when I go back to the main App component, it only shows this:

Thanks!

Then I'd try traversing your frontend components commenting one by one until you find the problematic one

authors: amrbashir liamfrench-lumentum tung517

repo: tauri-apps/tauri


text:
[feat] Allow experimental features in WebView

Describe the problem
I would like to enable experimental features on webkit or chromium. Is there a way to do such?
Describe the solution you'd like
Add documentation on how to enable experimental features if already possible. Otherwise expose a tauri config option to enable experimental browser features.
Alternatives considered
No response
Additional context
No response

If i remember everything correctly we have the following limitations:

macos: Doesn't support this at all
windows: Only supports chromium's command line flags. Which for now you have to set via the WEBVIEW2_ADDITIONAL_BROWSER_ARGUMENTS environment flag. Keep in mind that many of these flags only work in non-stable browser versions (webview2 uses the stable channel)
Linux: Hmm, can't remember the situation, but i think it's similar to macos.

tldr: Really nothing we can do here, so i'm going to close this issue until someone can show that i got that stuff wrong.

authors: Andful FabianLars


text:
Roadmap: Other Bindings?

Is there any issue to track the Other Bindings roadmap entry?
If not, maybe this one could be used for those of us that wish to subscribe to any updates.
Various discussions/issues regarding bindings, loading alternative runtimes with sidecars, migrating from electron/node, etc:

Question about whether tauri will support webserver
Bun?
Electron to tauri system
how to use a JavaScript module built for node.js
Node to Deno rust .js
QuickJS instead of Deno for app backend!
Node server doesn't starts on it's own
Rebuilding an Electron Desktop app with Tauri
Executing python scripts using Tauri
Question about whether tauri will support webserver
[feat] Electron to Tauri
[bug] Sidecar example fails to produce working Appimage
How to run nodejs server in build mode ?
Headless Tauri
[bug] Can't run Tauri on a different thread
How to implement another Backend Service (like C#/ .NET)

duplicate of https://github.com/tauri-apps/tauri/issues/4670

Agreed, this one is more generic

authors: Zireael07 amrbashir duurland


text:
[bug] Tauri v2.0.0-beta failed to build on Windows

Describe the bug
I recently migrated to v2, but encountered some issues. I am not sure if this issue should be raised here, but I think it may be related.
When I use github actions, it fails to build on Windows.
This may be related to my use of caching, as when I delete the cache, it can be successfully built.
But why?
This is a bit strange because there was no such issue in v1.
Reproduction
https://github.com/A-kirami/tauri-windows-build
https://github.com/A-kirami/tauri-windows-build/actions/runs/8108131093/job/22160785334
Expected behavior
It should be built successfully on Windows like v1.
Full tauri info output
[✔] Environment
    - OS: Windows 10.0.20348 X64
    ✔ WebView2: 119.0.2151.58
    ✔ MSVC: Visual Studio Enterprise 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 20.11.1
    - pnpm: 8.15.4
    - yarn: 1.22.21
    - npm: 10.2.4

[-] Packages
    - tauri [RUST]: 2.0.0-beta.8
    - tauri-build [RUST]: 2.0.0-beta.6
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.3
    - @tauri-apps/cli [NPM]: 2.0.0-beta.6

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - bundler: Vite

Stack trace
error: failed to run custom build command for `tauri-app v0.0.0 (D:\a\tauri-windows-build\tauri-windows-build\src-tauri)`

Caused by:
  process didn't exit successfully: `D:\a\tauri-windows-build\tauri-windows-build\src-tauri\target\release\build\tauri-app-24127a8263a01426\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-cfg=desktop
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_PREFIX=com_tauri
  failed to read plugin permissions: failed to read file: The system cannot find the file specified. (os error 2)
warning: build failed, waiting for other jobs to finish...
       Error failed to build app: failed to build app
 ELIFECYCLE  Command failed with exit code 1.
Error: Command failed with exit code 1: pnpm tauri build -t x86_64-pc-windows-msvc

Additional context
No response

can you try removing tauri-plugin-shell from Cargo.toml and try again?

can you try removing tauri-plugin-shell from Cargo.toml and try again?

The same result.
https://github.com/A-kirami/tauri-windows-build/actions/runs/8146043409/job/22263664310

I have no idea why this is not working, cloning the same repo and building it on my machine works just fine.
Here is a couple of things to try:

remove the use of cache in CI just to rule out that it is not a cache issue
try building without tauri-action and use pnpm tauri build -t <target> instead
if that doesn't work try without -t flag

I guess I was having the same issue, with yarn.

Compiling testeapp v0.1.0 (D:\a\tauri-ci-test\tauri-ci-test\apps\my_tauri_app\src-tauri)
error: failed to run custom build command for `testeapp v0.1.0 (D:\a\tauri-ci-test\tauri-ci-test\apps\my_tauri_app\src-tauri)`

Caused by:
  process didn't exit successfully: `D:\a\tauri-ci-test\tauri-ci-test\apps\my_tauri_app\src-tauri\target\release\build\testeapp-e05d03921a11ecee\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-cfg=desktop
  cargo:rustc-env=TAURI_ANDROID_PACKAGE_PREFIX=com_teste
  failed to read plugin permissions: failed to read file: The system cannot find the file specified. (os error 2)
warning: build failed, waiting for other jobs to finish...
       Error failed to build app: failed to build app
Error: Command failed with exit code 1: yarn tauri build

Building locally works, no cache involved.
Without cache, it builds.
With tauri-action args: -v -d also builds but doesn't solve the issue.
With tauri-action args: -t x86_64-pc-windows-msvc it builds and solved for me as I'm targeting only Windows. Thanks for it @amrbashir, while you suggested to do it without tauri-action, I utilized the action anyway.

Using the target flag is basically the same as a cache reset because the flag changes the target dir.
So the question (I raised on discord iirc?) whether a single reset is enough or if it comes back, remains. So far I've not heard from it reappearing so I assume it's just an incompatibility with files from prior beta versions maybe?

I've tried multiple times by cleaning the cache to be sure the issue was the caching. The way it was build with the -t flag it did hit cache, building time dropped 3min (not great imo). The cache hit was from a successful build without the flag.
Lastly, I did not upgraded to v2, the project was born v2. So maybe a different issue?
Note: the project is Windows only.

So if you're saying that without the -t flag it fails reliably even after clearing the cache

Yeah, but don't take this as a scientific testing, I've done many tests that I lost track. But I'm more than 80% sure, if I could gauge
The only thing that worked so far was the -t flag with "cache-all-crates: true" (just tried without it and didn't worked). Cache action is "swatinem/rust-cache@v2"
The build step doesn't download anything, it goes to compiling. Not sure how this would behave in a ideal scenario.

We're running into this issue too. It doesn't occur on macOS (the other platform we build for), but only occurs on Windows.
Our initial tests are not consistent with it being a caching issue: we've seen it succeed multiple times with tweaks that shouldn't change the Rust cache.
I'm trying out -t x86_64-pc-windows-msvc as recommended, and will test it ~3 or so times and let you know what I find.

I'm back with results, tested -t x86_64-pc-windows-msvc as recommended, and I've seen no issues in 7 re-runs of the build, without any changes to caching.
Looks like adding a target somehow makes a difference?

Unfortunately running into the same error despite defining an explicit target. Ref to failed GA run

Alright yeah, we just ran into our first CI error despite an explicit target.
Looks like the only other solution now must be something re ~= adding a retry action, because this is definitely a flaky error (happens less than 15% of the time for us).

For me, what fixed it was deleting the scr-tauri/target/debug/build folder and then running npm run tauri dev again. Once I did that I also noticed that my antivirus put some of the files in quarantine, so I had to put that folder on the whitelist.

is this error maybe an issue of softlinks? How does tauri read the permissions file in windows

Same using Swatinem/rust-cache@v2, I solved it by clearing the cache

Same, fixed by deleting all cache from https://github.com/<User>/<Repo>/actions/caches

For me, what fixed it was deleting the scr-tauri/target/debug/build folder and then running npm run tauri dev again. Once I did that I also noticed that my antivirus put some of the files in quarantine, so I had to put that folder on the whitelist.

Works, thanks!

Just hit this on Ubuntu 24 while migrating a Tauri v1 app to v2 beta and this also worked for me:

For me, what fixed it was deleting the scr-tauri/target/debug/build folder

On Windows, while getting the exact same error, the fix for me was uninstalling the 64x-bit version of Rust and installing the 32x-bit version instead. I'm not sure why that fixed it though.

Just encountered this on Ubuntu 22 on an app I just started building using tauri 2 rc 11. It was working, closed it. went to restart it a few minutes later (no changes made) and it wouldn't restart until I deleted the debug/build folder.

authors: A-kirami BranikSWG FabianLars ImUrX S1lander TreltaSev amrbashir happybeing lars-berger mamboer skyf0l thewh1teagle vasfvitor venkr


text:
[bug] Issue with configuring

Describe the bug
There seems to be a issue with configuring that i cant seem to find a fix for, when i use "devPath" in the tauri.conf.json under the build json object, i get his error
this issue happens when i use cargo tauri dev
"unknown field devPath, expected one of runner, dev-url, devUrl, frontend-dist, frontendDist, before-dev-command, beforeDevCommand, before-build-command, beforeBuildCommand, before-bundle-command, beforeBundleCommand, features
found an unknown configuration field. This usually means that you are using a CLI version that is newer than tauri-build and is incompatible. Please try updating the Rust crates by running cargo update in the Tauri app folder.`"
but if i use "devUrl" instead i get this error
 Error 'tauri.conf.json' error on 'build': Additional properties are not allowed ('devUrl' was unexpected)
I even tried to use cargo update, but it did nothing to solve the problem, so i am very confused on what i am supposed to be doing?
Reproduction
No response
Expected behavior
No response
Full tauri info output
[✘] Environment
    - OS: Windows 10.0.19045 X64
    ✔ WebView2: 123.0.2420.81
    ✘ Couldn't detect any Visual Studio or VS Build Tools instance with MSVC and SDK components. Download from https://aka.ms/vs/17/release/vs_BuildTools.exe
    ✔ rustc: 1.77.1 (7cf61ebde 2024-03-27)
    ✔ cargo: 1.77.1 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.11.1
    - yarn: 1.22.22
    - npm: 10.2.4

[-] Packages
    - tauri [RUST]: 2.0.0-beta.14
    - tauri-build [RUST]: 2.0.0-beta.11
    - wry [RUST]: 0.39.0
    - tao [RUST]: 0.27.0
    - tauri-cli [RUST]: 1.5.11
    - @tauri-apps/api [NPM]: 2.0.0-beta.4
    - @tauri-apps/cli [NPM]: 1.5.11

[-] App
    - build-type: build
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:3000/
    - framework: React (Next.js)
    - bundler: Webpack

Stack trace
Running BeforeDevCommand (`npm run dev`)

> project1@0.1.0 dev
> next dev

   ▲ Next.js 14.1.4
   - Local:        http://localhost:3000

        Info Watching C:\Users\a\Desktop\projects\project1\src-tauri for changes...
   Compiling app v0.1.0 (C:\Users\a\Desktop\projects\project1\src-tauri)
   Compiling solana-client v1.18.10
error: failed to run custom build command for `app v0.1.0 (C:\Users\a\Desktop\projects\project1\src-tauri)`

Caused by:
  process didn't exit successfully: `C:\Users\a\Desktop\projects\project1\src-tauri\target\debug\build\app-d8fbcf461ce5af45\build-script-build` (exit code: 1)
  --- stdout
  cargo:rerun-if-env-changed=TAURI_CONFIG
  cargo:rerun-if-changed=tauri.conf.json
  cargo:rustc-cfg=desktop
  unknown field `devPath`, expected one of `runner`, `dev-url`, `devUrl`, `frontend-dist`, `frontendDist`, `before-dev-command`, `beforeDevCommand`, `before-build-command`, `beforeBuildCommand`, `before-bundle-command`, `beforeBundleCommand`, `features`
  found an unknown configuration field. This usually means that you are using a CLI version that is newer than `tauri-build` and is incompatible. Please try updating the Rust crates by running `cargo update` in the Tauri app folder.
warning: build failed, waiting for other jobs to finish...
 ✓ Ready in 1867ms===================> ] 812/814:

Additional context
No response

Your tauri cli version is still on v1. Update that to v2-beta too and it should work.

Just for anyone else getting this as I did the problem appears to be with the docs at the moment - if @latest is used without the -- --beta then the V1 CLI will be installed, new installs/create are easier but upgrades are too easy at the moment to get mixed versions. Also at the moment it is not clear as to what NPM installs are required or are just alternative ways of doing stuff. At the moment I find that to do a dot upgrade of the beta I need to start fresh and copy over files, etc.

authors: Blatman FabianLars skateboard


text:
Error asking for user input with newer builds of plugin

Performing a go get github.com/tazjin/terraform-provider-keycloak in a clean gopath today results in a binary that doesn't work. When running terraform plan we get the following output.
Error asking for user input: 1 error(s) occurred:

* module.REDACTED.provider.keycloak: dial unix /var/folders/_d/hlc2psr11dx044w67ddwt8yc0000gn/T/plugin249198428|netrpc: connect: no such file or directory

Providing the KEYCLOAK_CLIENT_SECRET env var doesn't appear to avoid this error.
I'm guessing that the problem is probably upstream in terraform but still, if not publishing binary releases this project should do whatever is necessary to achieve a reproducible build.

FYI, my working $GOPATH/src/github.com/hashicorp/terraform  e50a57bcb7f3e7a0469f5b9b030df9074bb10bfa
My failing version is at 5c8ff928babf15ed929a691a5dd425f08e5d9c1a

Hey,
there is now a repeatable and reproducible build procedure (see recent commits to master and docs update).
I've made a signed binary release of a release candidate for the first version: v0.1-rc1
This version is pinned against Terraform v0.10.0, it may work with newer versions, too, once they are released (I'd assume minor versions at least).
While testing this on the most recent Keycloak version most things worked fine, but realm creation seems to have some strange side effect. I'll investigate that before making a "stable" release.

Thanks, I just tested the rc build now using the configuration steps in the updated README and all looks good.
I've not verified the realm creation issue, will ask someone to verify that.

authors: sharebear tazjin

repo: tazjin/terraform-provider-keycloak


text:
Ensure that conditional arguments are parsed valid

While working on a sample benchmarking app, I noticed that the following
was invalid:
{%each databases as database name%}{{database}}: {{name}}{%endeach%}

Using the the object:
{
  "database1": "online"
}

I was unable to get the template to render correctly.
After inspecting the template.tree object, I was able to discover that
the tokenizer had correctly found two cases of ASSIGNMENT the as in
database.
I updated the AST generation code to account for actual assignment and
properly adjust depending on what's passed.

Unclear on the language of "two cases of ASSIGNMENT the as in database" -- feel like there's an article missing. Is the issue that "as" is a substring of Database?

Yup, the tokenizer can't differentiate and probably shouldn't.  This logic seems to make most sense in the tree builder.

I'm not sure I agree (or possibly don't follow the rationale). as (spaces) vs [^\s]as[^\s] seem like very different types of token, to me -- but I also don't know much about how the tokenizer works, so I may be missing a deeper reason that this needs to be handled by a conditional instead of not being parsed as a non-identifier token in the first place

@kadamwhite here's the grammar that the tokenizer uses to parse 'as' as ASSIGN https://github.com/tbranyen/combyne/blob/master/lib/grammar.js#L41
Since it parses for all of them, even within other words, it's up to the tree builder to understand how to string them together.  The tokenizer's job shouldn't be to try and understand context of where it's used.

authors: kadamwhite tbranyen

repo: tbranyen/combyne


text:
Superscript text representing exponents is not copy-paste safe

Elements such as <sup> in data copied from spec content are replaced with their textContent when pasting as plain text, which can result in semantically inappropriate transformations such as (plucking real-word cases from Number.prototype.toFixed) "If x ≥ 1021" → "If x ≥ 1021" and "n / 10f - x" → "n / 10f - x".
This is a common need when writing test262 tests (cf. https://github.com/tc39/test262/blob/main/CONTRIBUTING.md#info ), so we should try to improve the experience similarly to what was done for step labels in #290.

What's the thing you think it should copy as? For digits I can map to the Unicode subscripts/superscripts, but obviously that doesn't generalize.

I'm thinking up-arrow notation for elements that can't be translated directly. PR incoming.


text:
Fix translation "An email has been sent"

https://github.com/tchapgouv/matrix-react-sdk/pull/412
Fix https://github.com/tchapgouv/tchap-web/issues/274

Tested on review app :

repo: tchapgouv/tchap-web


text:
Directly opening Harlequin keybindings results in "too many redirects"

If I click the link in the readme, or go directly to https://harlequin.sh/docs/bindings, Chrome shows me a:

However, if I navigate to https://harlequin.sh and navigate to the bindings, no issue.
I haven't repro'd on other devices, so if you can't repro, feel free to close 👍

Getting the same. Thanks. Super weird...

authors: MartinBernstorff tconbeer

repo: tconbeer/harlequin


text:
Documentation translation

@tdenniston I can translate the documentation into Russian. Create a new page on the Wiki I did not get.
I think you need to create a folder in the repository and load transfers to her?

@eg0r You're a contributor, so you should be able to create a new wiki page. Is there a "new page" button? Did you get an error message?

The button is there, but when you click on this address: https://github.com/tdenniston/bish/wiki/_new throws the main wiki.

I created a page for you to edit: https://github.com/tdenniston/bish/wiki/Home-(RUS). I don't know why you can't create pages yourself.

I do not know what the problem is, but I can not make any changes.
Tried through cloning wiki, also comes out.
egor@book:~/Tests/Bish/t/bish.wiki > git push
Username for 'https://github.com': eg0r
Password for 'https://eg0r@github.com':
remote: Permission to tdenniston/bish.wiki.git denied to eg0r.
fatal: unable to access 'https://github.com/tdenniston/bish.wiki.git/': The requested URL returned error: 403

Try it now. I had accidentally set wiki editing to private.

Now there is no problem :smile:

repo: tdenniston/bish


text:
tdex market fixedfee --base_fee 0 --quote_fee 0 ignores the 0 values

The UpdateMarketFixedFee seems to discard 0 values as if the protobuf request is empty. Those should be instead used as valid values

Ah! This is tricky:

originally, there was only a fixed fee for both assets
then, we introduced base and quote fixed fees. With this change, the 0 value is used to actually ignore the change to let the user be able to update only one between the base and quote fees. For instance,  to update the quote fee one would call market.ChangeFixedFees(0, 100). The fixed fees of the market cannot be zeroed with this design though.

I would add a new special value -1 to replace the 0 special case where one wants to update only one of the 2 fees and leaving the other one as it is.

I think is fine to say that when updating only one side, we simply overwrite the other with current value
usually clients do;

GetMarketInfo
Fill the inouts with current value
Update Fee with values changed and old one fetched

Fine tho to have this special case, most of the time not needed (we will overwrite from clients all the times unchanged values)

authors: altafan tiero

repo: tdex-network/tdex-daemon


text:
GIF compression

InlineQueryResultGif and sendDocument both compress GIF passed with URL. Can this annoying behavior be disabled any way?

No. All animations are intended to be played in MP4 format, which can provide the same or better quality with much smaller file size.

No. All animations are intended to be played in MP4 format, which can provide the same or better quality with much smaller file size.

Provide the compression option then where user can pick the quality like in android client. Or turn this compression off since either of clients degrades quality during GIF to MP4 conversion.

authors: Sarisan levlam

repo: tdlib/telegram-bot-api


text:
Update index.md

As suggested by Quentin - I have added doi links (some of the doi's weren't linked as an https// link).  I have fixed these where possible and added other links into the references where they exist.
Also added a link to the GitHub

Will check them
Thanks
On 21/08/2018 3:04 PM, Quentin Groom wrote:

@qgroom commented on this pull request.
Thanks for putting these links in.
There is a broken link though
http://community.gbif.org/pg/groups/21292/gbiftdwg-biodiversity-data-quality-interest-group/
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/tdwg/website/pull/79#pullrequestreview-147905622,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AVx405i6ioO0IHEy77Pc4Lz0ZMnDLt8Pks5uS5TogaJpZM4WE-D1.

--
Arthur Chapman
(Australian Biodiversity Information Services)
PO Box 35
Ballan  Vic 3342
Australia
+61 (0)400 400 326

repo: tdwg/website


text:
Making this thing work

So far this library has a pretty good PoC built, but there are a few unsolved problems which will hinder it's functionality in the future.
These are:

Handling the implementation of serial comms with various HALs/platforms.
Asynchronous AT commands that may return responses out of order.

And these are closely tied since the traits we rely on to solve these problems have a big effect on what we end up building.
At this stage I think we should look at what other projects are using to do asynchrony based on the embedded_hal traits. From my brief analysis it looks like we will need to implement some kind of future that can also handle out of order responses from a shared fixed-size buffer under the hood.

Looks like atat is the solution here. It may have some issues relying on embassy_time currently, however we could fork and fix this so it supports rtic_monotonics.

repo: team-arrow-racing/wurth-calypso-rs


text:
🔀 :: swagger 설정

close #141

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

반영이후에는 Re-Request 해주세요 :)

반영이후에는 Re-Request 해주세요 :)

넹넹

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃

저거 pn표기법 코멘트좀 그만달으레이 이메일 터진디

P1: 꼭 반영해주세요 (Request changes)
P2: 적극적으로 고려해주세요 (Request changes)
P3: 웬만하면 반영해 주세요 (Comment)
P4: 반영해도 좋고 넘어가도 좋습니다 (Approve)
P5: 그냥 사소한 의견입니다 (Approve)
질문은 그냥 코멘트로 😃


text:
xcrun: error: invalid active developer path

Tea is failing to sync pantries with the following error:
[2023-04-25 01:23:17.194] [error] Error: Command failed: cd '/Users/redacted/.tea/tea.xyz/gui' && ./tea -S
tea: inspecting pantries…
^[[G^[[1A^[[0Jtea: fetching pantries…

xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun at: /Library/Developer/CommandLineTools/usr/bin/xcrun

panic: spilt tea. we're sorry and we'll fix it… but you have to report the bug!

    https://github.com/teaxyz/cli/issues/new?title=panic%3Acmd+failed%3A+1%3A+%2Fusr%2Fbin%2Fgit+clone+--bare+--depth%3D1+https%3A%2F%2Fgithub.com%2Fteaxyz%2Fpantry+%2FUsers%2Fredacted%2F.tea%2Ftea.xyz%2Fvar%2Fpantries%2Fteaxyz%2Fpantry

----------------------------------------------------->> attachment begin
Error: cmd failed: 1: /usr/bin/git clone --bare --depth=1 https://github.com/teaxyz/pantry /Users/redacted/.tea/tea.xyz/var/pantries/teaxyz/pantry
    at useRun (file:///Users/builder/actions-runner/_work/cli/cli/src/hooks/useRun.ts:39:34)
    at async clone (file:///Users/builder/actions-runner/_work/cli/cli/src/hooks/useSync.ts:101:9)
    at async file:///Users/builder/actions-runner/_work/cli/cli/src/hooks/useSync.ts:80:17

Notable missing detail in the report is the absense of Xcode or Xcode CLT.

k lol it's a broken xcode command line tools installation. We can detect this and then use our own git.
I think what I'm going to do is always http fetch the pantry and then convert to a git install installing our own git as necessary

Fixed in #555

authors: ABevier mxcl

repo: teaxyz/cli


text:
Add HTTPOnly and SameSite attribute to Cookie

The Cookie struct does not accommodate HTTPOnly and SameSite fields, described in the spec.
This makes it impossible to specify the HTTPOnly and SameSite field of a cookie. This field can be specified in the Set-Cookie HTTP header, so the Cookie struct should also support it.

A similar issue filed for Selenium WebDriver https://github.com/SeleniumHQ/selenium/issues/7798

What all needs to be done here?
Can we just update the Cookie struct to contain an extra field with the correct JSON field name?

authors: gjyalpha nveeser

repo: tebeka/selenium