Two way audio only works off Wifi (Reolink POE Doorbell)

I have been struggling to get my two way audio to work on my new doorbell. I have frigate configured with a minimal setup to get started.
Frigate is installed on docker in my unraid machine and HA is on my dell mini pc. Frigate has no errors and seems to be working fine.
I can get the two way audio to work when my phone is off wifi and doesn't work when connected. It was to my surprise since I figured I would have the opposite issue of it not working away from home.
The frigate card has what I think is a broken microphone symbol on wifi and goes red and works off of wifi.

Here is my frigate yaml and card configuration. I'd appreciate any insight, thanks in advance.
mqtt:
  enabled: true
  host: <IP_ADDRESS>
  port: 1883
  topic_prefix: frigate
  client_id: frigate
  user: frigate
  password: password
  stats_interval: 60

go2rtc:
  streams:
    doorbell:
      - rtsp://admin:password@<IP_ADDRESS>:554/h264Preview_01_main
      - ffmpeg:doorbell#audio=opus#audio=volume#audio=aac
    doorbell_sub:
      - rtsp://admin:password@<IP_ADDRESS>:554/h264Preview_01_sub
      - ffmpeg:doorbell_sub#audio=opus#audio=volume
  webrtc:
    candidates:
      - <IP_ADDRESS>:8555
      - stun:8555

  ## THIS PREVENTS THE AUDIO COMING OUT FROM THE DOORBELL SOUNDING MUFFLED
  ffmpeg:
    bin: ffmpeg
    volume: "-af \"volume=30dB\""

cameras:
  doorbell:
    ffmpeg:
      output_args:
        record: preset-record-generic-audio-copy
      inputs:
        - path: rtsp://<IP_ADDRESS>:8554/doorbell_sub
          input_args: preset-rtsp-restream
          roles:
            - detect
        - path: rtsp://<IP_ADDRESS>:8554/doorbell
          input_args: preset-rtsp-restream
          roles:
            - record
    live:
      stream_name: doorbell_sub

    detect:
      enabled: false
      width: 640
      height: 480
      fps: 5
    record:
      enabled: false
      retain:
        days: 2
        #mode: active_objects
      events:
        retain:
          default: 5
          mode: motion
        pre_capture: 3
        post_capture: 10

type: custom:frigate-card
cameras:
  - live_provider: go2rtc
    frigate: {}
    go2rtc:
      modes:
        - webrtc
    camera_entity: camera.doorbell
menu:
  style: overlay
  buttons:
    microphone:
      enabled: true
      alignment: opposing
      type: toggle
    frigate:
      enabled: false
    cameras:
      enabled: false
    substreams:
      enabled: false
    live:
      enabled: false
    clips:
      enabled: false
    snapshots:
      enabled: false
    download:
      enabled: false
    camera_ui:
      enabled: false
    fullscreen:
      enabled: false
    timeline:
      enabled: false
    media_player:
      enabled: true
    mute:
      enabled: true
live:
  microphone:
    always_connected: false

this is most likely because you connect locally to HA without SSL / https so microphone permission is not granted in that case

this is most likely because you connect locally to HA without SSL / https so microphone permission is not granted in that case

Hmm, I wonder how others resolved that. I have a domain with a local only .home.domain.com with cert set up but it doesn't seem to work. I don't really want to go off wifi to use the 2 way audio since it's lags enough locally.

Got it working, my local only cert was working. Just needed to clear the cashe on my companion app. Now I have https and two way.


Transfer learning

Hi,
Do you plan to release transfer learning options to specify which layers should be trained?
Also, have you tried this network on different objects besides portraits? If yes, did you managed to get comparable results?

Hi, thanks for your attention.
For your questions:
Q1: Do you plan to release transfer learning options to specify which layers should be trained?
Does "transfer learning" mean the SOC strategy in our paper? If so, we will provide training code for the SOC stage.
Q2: Also, have you tried this network on different objects besides portraits? If yes, did you managed to get comparable results?
We didn't try it. As far as I know, the only open-source matting dataset that consists of different objects is Adobe Matting Dataset. However, this dataset is too small to train a trimap-free matting model.
If you focus on a specific object, e.g., cars, and you have a labeled dataset, I believe you can get results comparable to our portrait matting scheme.

I've tried the network on random images and it seems to work quite well. Best results can be achieved if the subject has a certain distance to the background. My hypothesis is that the network might be conditioned to cut out objects which are not in focus. For example, in many images, the background is out of focus.

@99991
Wowoo... This is a very interesting finding. It means that the model has learned the pattern of bokeh.
I agree with you. If the background is not in focus, i.e., bokeh, the network will find the objects that are in focus, i.e., the saliency objects. If the background is also in focus, the network will try to find the portraits.

Thanks for the answers! @ZHKKKe @99991
Q1: Does "transfer learning" mean the SOC strategy in our paper?
I wasn't thinking about your SOC approach here. Rather about will your training code provide an option to load a pre-trained model and then fine-tune specific layers of the network while freezing others?
Q3: Do you know what is training time on certain hardware for your model? Eather train from scratch or by doing transfer learning if applicable.
Btw, really great results guys on this one! I can't wait to see how this network will perform on different types of objects and backgrounds 😄
Also, great results @99991. Before asking this question, I also tested the model on different objects without a "bokeh" background but rather full image focus. As @ZHKKKe said, the results weren't pretty good as the network cut out the whole background certain parts of the desired object too.

@NVukobrat
Q1: Does "transfer learning" mean the SOC strategy in our paper?
We will provide the training process, including the loading function of the pre-trained model. However, since there are too many layers in the model, we will not add options to freeze certain layer parameters. Therefore, it is necessary for code users to add extra functions to achieve this (I believe this is not difficult).
Q3: Do you know what is training time on certain hardware for your model? Eather train from scratch or by doing transfer learning if applicable.
Our supervised training set contains about 100k samples (3k foregrounds + background replacement). It will take 2-3 days in two GTX 1080Ti GPUs. Our SOC strategy uses about 50k unlabeled images. It will take 1-2 days in a single GTX 1080Ti GPU.

@ZHKKKe Does the dataset will be public?

@newjavaer
Nope. I am sorry that we cannot release the training set due to license issue.

Thanks again @ZHKKKe for your answers!
Q4: Do you have any timeline for when can we expect the training script?
Q5: Also, can you give us insights into which dataset structure training script will support? For example, should data be split into different directories in some way, should labels be in COCO or some other format... Do you have more info on this one?

@NVukobrat
Q4: Do you have any timeline for when can we expect the training script?
We will release the training code next month.
Q5: Also, can you give us insights into which dataset structure training script will support? For example, should data be split into different directories in some way, should labels be in COCO or some other format... Do you have more info on this one?
We will provide a superclass (template) for the code of dataset. You can inherit from it and implement your own dataset.
We may provide a default dataset class for Adobe Image Matting Dataset.

Great! Thanks for the help @ZHKKKe!


Support configurable start time - emailable report

The EmailableReport2 class provides test start time values which
are in millisecond value from the epoch (01/01/1970 00:00:00):

sample value<PHONE_NUMBER>103

GMT : January 11, 2021 Monday 10: 08: 35.103

see test-output/emailable-report.html for start time report usage
see https://www.epochconverter.com/clock

This value is not very human readable, and this change adds a protected
method which can be overridden in sub classes to provide a more human
readable version of the test start time (e.g. 2021-01-01 12:34:56)
Fixes #2459.
Did you remember to?

[ ] Add test case(s)

I could not find any existing test cases to update, please let me know if I should add/update any in this PR @krmahadevan

[x] Update CHANGES.txt

@krmahadevan / @juherr may I ask when this feature/fix for this issue will be released?
In other words, when is the next release of testng due, so that I can start using the new feature I added in this PR in my other projects which implement/run testng tests?

@bazzani - It should be released this weekend.


Couchbase Lite Android 2.0.0-DB018 / delete() and close() fail after a bulk storage with inBatch()

Let me start this issue by indicating that I'm new to both couchbase and couchbase lite. What I would like to do is delete all documents in the database. I'd appreciate some method like database.clear() or database.deleteAllDocuments(). But these methods don't exist.
So as a workaround, I tried to drop the database. I found 2 methods that could do the job close() and delete(), but their respective documentation aren't very clear on their differences. I assumed then that :

close() should be used for releasing a session on the database
delete() actually deletes the data by deleting the file on the disk

Hence I tried to call these methods in different ways. Some of them work, but I have a scenario that doesn't work, and I can't get to figure out why.
I do the following :

I create a db instance, that a I delete and recreate right away to "clear" it.
I then add some bulk data using inBatch()  (50000 objects) then attempt to close the db
And that's pretty much it.
What actually happens at runtime :
On the first execution, creation, deletion and recreation works but the call to close() throws a CouchbaseLiteException Failed in closing database transaction not closed
On the second run, the call to delete() throws a Failed in CouchbaseLiteException batch request database busy/locked

I thought that the second exception on delete() was a consequence of the first exception on close(), but it isn't the case: if I remove the call to close() I still get the same exception on delete().
I want to add that I don't understand the message Failed in closing database transaction not closed since it is stated in the documentation that transactions don't exist on Couchbase lite 2.0 :

Couchbase Lite does not offer transactional guarantees, and that the purpose of the method (inBatch(), ndlr) is to optimize batch operations rather than to enable ACID transactions

Can you help ? That is by fixing this bug, or better by providing a deleteAllDocuments() method on the Database class :p
Below is the code and the details of both exceptions.
An intent service to bulk store data
package org.nla.testcouch2.couch;

import android.app.IntentService;
import android.content.Intent;
import android.support.annotation.Nullable;
import android.util.Log;

import com.couchbase.lite.CouchbaseLiteException;
import com.couchbase.lite.Database;
import com.couchbase.lite.DatabaseConfiguration;
import com.couchbase.lite.Document;

import java.util.TimerTask;

import org.nla.testcouch2.App;
import org.nla.testcouch2.Constants;
import org.nla.testcouch2.Person;

public class StoreToCouchbaseIntentService extends IntentService {
    public static final String action = "org.nla.testcouch2.couch.StoreToCouchbaseIntentService";
    private Database database = null;

    public StoreToCouchbaseIntentService() {
        super("StoreToCouchbaseIntentService");
    }

    @Override
    protected void onHandleIntent(@Nullable Intent intent) {
        try {
            database = new Database("application", new DatabaseConfiguration(getApplicationContext()));
            database.delete();
            database = new Database("application", new DatabaseConfiguration(getApplicationContext()));

            long tic = System.currentTimeMillis();
            Log.d("mobiledatabaseperftests", "Starting storage to couch");

            database.inBatch(new TimerTask() {
                @Override
                public void run() {
                    for (Person person : App.app().getPersons()) {
                        Document newPerson = new Document();
                        newPerson.setString(Constants.TYPE, Constants.TYPE_PERSON);
                        newPerson.setInt(Constants.AGE, person.getAge());
                        newPerson.setString(Constants.UUID, person.getGuid());
                        newPerson.setString(Constants.COMPANY, person.getCompany());
                        newPerson.setString(Constants.EMAIL, person.getEmail());
                        newPerson.setString(Constants.EYE_COLOR, person.getEyeColor());
                        newPerson.setString(Constants.PHONE, person.getPhone());
                        newPerson.setString(Constants.PICTURE, person.getPicture());
                        newPerson.setString(Constants.NAME, person.getName());
                        try {
                            database.save(newPerson);
                        } catch (CouchbaseLiteException e) {
                            Log.e("mobiledatabaseperftests", "Failed in storing document " + e.getMessage(), e);
                        }
                    }
                    Log.d("mobiledatabaseperftests", "Batch storage over");
                    try {
                        database.close();
                    } catch (CouchbaseLiteException e) {
                        Log.e("mobiledatabaseperftests", "Failed in closing database " + e.getMessage(), e);
                    }
                    long duration = System.currentTimeMillis() - tic;
                    onBatchTerminated(duration);
                }
            });
        } catch (CouchbaseLiteException e) {
            Log.e("mobiledatabaseperftests", "Failed in  batch request " + e.getMessage(), e);
        }
    }

    private void onBatchTerminated(long duration) {
        Intent broadcastOfflineIntent = new Intent();
        broadcastOfflineIntent.setAction(action);
        broadcastOfflineIntent.addCategory(Intent.CATEGORY_DEFAULT);
        broadcastOfflineIntent.putExtra(Constants.keySuccess, true);
        broadcastOfflineIntent.putExtra(Constants.keyDuration, duration);
        Log.d("mobiledatabaseperftests", "Stored to couchbase offline: " + duration);
        sendBroadcast(broadcastOfflineIntent);
    }
}

Failed in  batch request database busy/locked
Failed in  batch request database busy/locked
CouchbaseLiteException{domain=1, code=24, msg=database busy/locked}
   at com.couchbase.lite.internal.bridge.LiteCoreBridge.convertException(LiteCoreBridge.java:22)
   at com.couchbase.lite.Database.deleteC4DB(Database.java:894)
   at com.couchbase.lite.Database.delete(Database.java:442)
   at org.nla.testcouch2.couch.StoreToCouchbaseIntentService.onHandleIntent(StoreToCouchbaseIntentService.java:33)
   at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
   at android.os.Handler.dispatchMessage(Handler.java:105)
   at android.os.Looper.loop(Looper.java:164)
   at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: LiteCoreException{domain=1, code=24, msg=database busy/locked}
   at com.couchbase.litecore.C4Database.delete(Native Method)
   at com.couchbase.litecore.C4Database.delete(C4Database.java:56)
   at com.couchbase.lite.Database.deleteC4DB(Database.java:892)
   at com.couchbase.lite.Database.delete(Database.java:442)
   at org.nla.testcouch2.couch.StoreToCouchbaseIntentService.onHandleIntent(StoreToCouchbaseIntentService.java:33)
   at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
   at android.os.Handler.dispatchMessage(Handler.java:105)
   at android.os.Looper.loop(Looper.java:164)
   at android.os.HandlerThread.run(HandlerThread.java:65)

Failed in closing database transaction not closed
Failed in closing database transaction not closed
CouchbaseLiteException{domain=1, code=26, msg=transaction not closed}
   at com.couchbase.lite.internal.bridge.LiteCoreBridge.convertException(LiteCoreBridge.java:22)
   at com.couchbase.lite.Database.closeC4DB(Database.java:886)
   at com.couchbase.lite.Database.close(Database.java:424)
   at org.nla.testcouch2.couch.StoreToCouchbaseIntentService$1.run(StoreToCouchbaseIntentService.java:61)
   at com.couchbase.lite.Database.inBatch(Database.java:306)
   at org.nla.testcouch2.couch.StoreToCouchbaseIntentService.onHandleIntent(StoreToCouchbaseIntentService.java:39)
   at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
   at android.os.Handler.dispatchMessage(Handler.java:105)
   at android.os.Looper.loop(Looper.java:164)
   at android.os.HandlerThread.run(HandlerThread.java:65)
Caused by: LiteCoreException{domain=1, code=26, msg=transaction not closed}
   at com.couchbase.litecore.C4Database.close(Native Method)
   at com.couchbase.litecore.C4Database.close(C4Database.java:52)
   at com.couchbase.lite.Database.closeC4DB(Database.java:884)
   at com.couchbase.lite.Database.close(Database.java:424)
   at org.nla.testcouch2.couch.StoreToCouchbaseIntentService$1.run(StoreToCouchbaseIntentService.java:61)
   at com.couchbase.lite.Database.inBatch(Database.java:306)
   at org.nla.testcouch2.couch.StoreToCouchbaseIntentService.onHandleIntent(StoreToCouchbaseIntentService.java:39)
   at android.app.IntentService$ServiceHandler.handleMessage(IntentService.java:68)
   at android.os.Handler.dispatchMessage(Handler.java:105)
   at android.os.Looper.loop(Looper.java:164)
   at android.os.HandlerThread.run(HandlerThread.java:65)

@daffycricket
During I am reading the code snippet, I found Database.close() method is called in Database.inBatch() method. I guess it could cause unexpected error.
InBatch() method uses SQLite's transaction to improve the performance. If Database is closed in the transaction, inBatch() can not call endTransaction(boolean commit).

Hi @daffycricket
I wrote the unit test, see below codes. It is unable to reproduce the Exception.
NOTE: In case calling Database.close() in inBatch() method, the close() method fails with throwing Exception.
    @Test
    public void testDeleteAndOpenDB() throws CouchbaseLiteException {
        DatabaseConfiguration config = new DatabaseConfiguration(this.context);
        config.setDirectory(dir);

        // open "application" database
        final Database database1 = new Database("application", config);

        // delete "application" database
        database1.delete();

        // open "application" database again
        final Database database2 = new Database("application", config);

        database2.inBatch(new Runnable() {
            @Override
            public void run() {
                // just create some documents
                for(int i = 0; i < 10; i++){
                    Document doc = new Document();
                    doc.setInt("index", i);
                    try {
                        database2.save(doc);
                    } catch (CouchbaseLiteException e) {
                        Log.e(TAG, "Failed in storing document " + e.getMessage(), e);
                    }
                }
            }
        });

        database2.close();
    }

Hi @daffycricket ,
1st Exception could be caused by calling delete() method during other thread(s) was accessing the database. From the code snippet, I am not sure what caused this.
2nd Exception is clearly caused by calling close() method in inBatch(). DB close operation is not allowed during the middle of the transaction.
I believe both exceptions are expected behavior. So I will close this ticket. If you have further questions or issues, please reopen this ticket or file new ticket?
Thanks!


Fixing gPTP sample app documentation

This also add instructions how to run zephyr networking with native_posix board.

Updated according to comments.

Codecov Report

Merging #11833 into master will decrease coverage by 0.13%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11833      +/-   ##
==========================================
- Coverage   51.43%    51.3%   -0.14%
==========================================
  Files         231      231
  Lines       28751    28752       +1
  Branches     7152     7156       +4
==========================================
- Hits        14789    14751      -38
- Misses      11144    11188      +44
+ Partials     2818     2813       -5

Impacted Files
Coverage Δ

subsys/shell/shell_dummy.c
37.14% <0%> (-8.58%)
:arrow_down:

subsys/shell/shell.c
31.36% <0%> (-3.76%)
:arrow_down:

subsys/net/ip/udp.c
64.58% <0%> (-2.09%)
:arrow_down:

subsys/net/ip/ipv4.c
62.19% <0%> (-1.91%)
:arrow_down:

subsys/net/ip/connection.c
74.6% <0%> (-0.66%)
:arrow_down:

subsys/net/ip/tcp.c
56.98% <0%> (-0.4%)
:arrow_down:

subsys/net/ip/icmpv6.c
30.48% <0%> (-0.35%)
:arrow_down:

kernel/mutex.c
97.05% <0%> (ø)
:arrow_up:

subsys/net/ip/utils.c
79.37% <0%> (+1.41%)
:arrow_up:

Continue to review full report at Codecov.

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

I take that as a response to my confession that I never ran a networking with native_posix in one of the tickets lately

No, this is not related to your confession. There was some misinformation in gptp docs where it told to do testing against qemu and slip which in fact does not work properly any more and native_posix should be used instead.


dart2js: constant-update-2018: timeout for language_2/canonicalization_hashing_shallow_collision_array_test

This test times out (if left to run it takes ~15 minutes.)
tools/test.py -m release -c dart2js -r d8\
   --dart2js-options --enable-experiment=constant-update-2018 \
  language_2/canonicalization_hashing_shallow_collision_array_test

Deserializing the type inference results takes too long.
abstract class AbstractDataSource extends DataSourceMixin
    implements DataSource {
  ...
  ir.TreeNode _readTreeNode(_MemberData memberData) {
    _TreeNodeKind kind = _readEnumInternal(_TreeNodeKind.values);
    switch (kind) {
      ...
      case _TreeNodeKind.constant:
        // TODO(johnniwinther): Support serialization within a member context
        // and use this to temporarily cache constant node indices.
        ir.ConstantExpression expression = _readTreeNode(memberData);
        _ConstantNodeIndexerVisitor indexer = new _ConstantNodeIndexerVisitor();
        expression.constant.accept(indexer);
        ir.Constant constant = indexer.getConstant(_readIntInternal());
        return new ConstantReference(expression, constant);

[ ] One problem with this test is that there are type inference results for each of the sub-constants [1], [2] etc in the big constant:

const [[1], [2], [3], ...]

The huge top-level constant is re-indexed to call indexer.getConstant for each sub-constant.

[x] Another problem is that _ConstantNodeIndexerVisitor is not DAG-aware. This causes language_2/canonicalization_hashing_memoize_array_test to run out of memory.

/cc @johnniwinther - where is the right place to put a shared _ConstantNodeIndexerVisitor?

Second issue fixed by https://dart-review.googlesource.com/c/sdk/+/110186

The dart2js bots show errors on this test after const_update_2018 flag was turned on by default and the results have been approved to turn the bots green

dart2js-rti-linux-x64-d8
dart2js-strong-hostasserts-linux-ia32-d8
dart2js-minified-strong-linux-x64-d8
dart2js-strong-linux-x64-chrome
dart2js-csp-minified-linux-x64-chrome
dart2js-strong-linux-x64-firefox


Error when downloading large files: Least unacked too small

When downloading a large file via the network, the download sometimes abort after ~1min with the following error:
Closing session with error: InvalidStopWaitingData: Least unacked too small.

@lucas-clemente: Can you send me the debug output?

Can't reproduce it with the debug log on :/
The relevant Chrome code is (quic_connection.cc QuicConnection::ValidateStopWaitingFrame):
  if (stop_waiting.least_unacked <
      received_packet_manager_.peer_least_packet_awaiting_ack()) {
    DLOG(ERROR) << ENDPOINT << "Peer's sent low least_unacked: "
                << stop_waiting.least_unacked << " vs "
                << received_packet_manager_.peer_least_packet_awaiting_ack();
    // We never process old ack frames, so this number should only increase.
    return "Least unacked too small.";
  }

Does that help?

I already found that, but I'd need to know what the exact numbers were (in the StopWaitingFrame that we sent and in the ACKs we received).

With all of the recent changes I was unable to reproduce this issue while downloading ~4GB of data via the internet.


Updated README to list tokens used by this repo

#537  👈
main

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

Join @CatChen and the rest of your teammates on  Graphite


Where are the screenshots?

This article absolutely needs accompanying screenshots to assist users as they work through the detailed processes within the document.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: b707d763-4c82-0d68-9cc7-35fb66935d25
Version Independent ID: 4da67e73-1af9-ed9d-f367-4048ce5897fd
Content: Manage the search schema in SharePoint - SharePoint in Microsoft 365
Content Source: SharePoint/SharePointOnline/manage-search-schema.md
Service: sharepoint-online
GitHub Login: @SerdarSoysal
Microsoft Alias: serdars

Thanks for the feedback. It's been forwarded to the documentation team.


yarn run blendid -- init error code 1

When i try to run blendid for the first time i got this error:
λ yarn run blendid -- init
yarn run v0.27.5
$ "C:\Users\Corvi\Sedona\node_modules\.bin\blendid" "init"
'C:\Users\Corvi\Sedona\node_modules\.bin\blendid" "init' is not recognized as an internal or external command,
operable program or batch file.
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

yarn/gulp installed globally
node version 6.11.0
tried different pc - same.

I get the same error with yarn run blendid -- build

Also this is on windows 10, when i use bash from ubuntu subsystem all work fine.

Node: v8.2.1
Yarn: v0.27.5
Windows 7
Same issue.

Same issue.
But this one works well: ./node_modules/.bin/blendid.cmd -- build

I don't get an error but none of the commands passed to blendid work (-- init or --build) it runs the default server every time
Win7
node 6.10.1
yarn 0.27.5

Node: v8.2.1
Yarn: v0.27.5
gulp: v3.9.1
Windows 10

BTW it can be yarn or gulp bug, after we put command yarn run blendid -- init it converts it to "C:\blahblah\node_modules\.bin\blendid" "init", windows try to run "init" as separate command and cant find it.
If yarn convert it to "C:\blahblah\node_modules\.bin\blendid init" or "C:\blahblah\node_modules\.bin\blendid" init all will be fine.

Just for now we can modify recomendations from readme, and use this Yarn scripts.
Add them to package.json
"scripts": {
    "start": "yarn run blendid",
    "build": "./node_modules/.bin/blendid build"
  }

After this, you can run yarn start to start blendid dev enviroment, yarn run build to build project.


Fixes window.ipfs is added after page load

fixes #362
also fixes whitelist by default from review feedback
see https://github.com/ipfs-shipyard/ipfs-companion/issues/362#issuecomment-362231167 for discussion

Tried it out, worked beautifully! Nice to see a IPFS app whose size is only 2.2K 👯

@lidel good to merge now?

eek, wtf?! I'm guessing that's because we're adding window.Ipfs as well. I think we could get rid of half of that by removing dist/contentScripts/ipfs-proxy/page.js after dist/contentScripts/ipfs-proxy/content.js is generated (page.js is inlined into content.js so isn't actually used). Would that be acceptable or should we remove window.Ipfs altogether?

I am afraid removing page.js is not enough:  content.js itself is >4MiB.
We need to remove window.Ipfs for now, or find a way to go under linter limit.

I can bring content.js down to 2MB if I uglifyify page.js (this includes window.Ipfs) - is that cool?

Yes, we can minimize the output as long we have reproducible builds (#306).

@lidel what did you do to fix the yarn issue?

@alanshaw  removing the node_modules folder and running yarn again seemed to work around the issue (I did it on a linux box, if that matters. idea from: https://github.com/yarnpkg/yarn/issues/2083#issuecomment-2724246770)

🙄 that's what I did...

Did you run via npm run yarn-build  to guarantee correct yarn is used?
Perhaps you have an older version installed globally. 🤔

I did yes. I'm not sure how we can avoid this when our dependencies have github dependencies e.g.
https://github.com/libp2p/js-libp2p-crypto/blob/71339e08e75f6c92485e22a95caf96164cbb1cad/package.json#L45

@lidel I'm not sure your commit in https://github.com/ipfs-shipyard/ipfs-companion/commit/1a968eef41afd634622d7cd920bcdcf8a74d5e75 fixed the build - I still see lots of github: dependencies in that file.

@alanshaw I've just added git to the image for now and it fixed the build.
(CI is being reworked in #372, but i did not want to port that PR here, just fixed alpine image so I can merge this PR)


fix(forms): update lang fr

:tada: This PR is included in version 1.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Doesn't work on web - Flutter 3.3.7

Hi there!
This package example doesn't work fully on the web. I've tried the same code on android and works flawlessly, but when I run it on the web, the result page is empty. I've even tried to save uint8list data to a file, but with no success. My guess would be, that the saveEditing function doesn't work properly for the web.

Using Flutter v3.3.7
Google Chrome latest stable version (v107.0.5304.87)

Hi, thanks for finding bug. right now I am occupied in other work. once I will get some time will fix it. I will be happy if you generate PR.

As other users figured out..  flutter run -d chrome --web-renderer canvaskit --dart-define=BROWSER_IMAGE_DECODING_ENABLED=false --release does the trick for now, but this workaround only works for release mode.


Tokenizers decode

Description
Expose tokenizers decode method https://github.com/deepjavalibrary/djl/issues/1829

Codecov Report

Merging #1843 (bec8cbb) into master (bb5073f) will decrease coverage by 2.36%.
The diff coverage is 64.61%.

@@             Coverage Diff              @@
##             master    #1843      +/-   ##
============================================
- Coverage     72.08%   69.72%   -2.37%
- Complexity     5126     5525     +399
============================================
  Files           473      526      +53
  Lines         21970    24446    +2476
  Branches       2351     2665     +314
============================================
+ Hits          15838    17044    +1206
- Misses         4925     6090    +1165
- Partials       1207     1312     +105

Impacted Files
Coverage Δ

api/src/main/java/ai/djl/modality/cv/Image.java
69.23% <ø> (-4.11%)
:arrow_down:

...rc/main/java/ai/djl/modality/cv/MultiBoxPrior.java
76.00% <ø> (ø)

...rc/main/java/ai/djl/modality/cv/output/Joints.java
71.42% <ø> (ø)

.../main/java/ai/djl/modality/cv/output/Landmark.java
100.00% <ø> (ø)

...main/java/ai/djl/modality/cv/output/Rectangle.java
72.41% <0.00%> (ø)

...i/djl/modality/cv/translator/BigGANTranslator.java
21.42% <0.00%> (-5.24%)
:arrow_down:

...odality/cv/translator/BigGANTranslatorFactory.java
33.33% <0.00%> (+8.33%)
:arrow_up:

...nslator/InstanceSegmentationTranslatorFactory.java
14.28% <0.00%> (-3.90%)
:arrow_down:

.../cv/translator/SemanticSegmentationTranslator.java
0.00% <0.00%> (ø)

.../cv/translator/StyleTransferTranslatorFactory.java
40.00% <ø> (ø)

... and 420 more

Continue to review full report at Codecov.

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


Added CSS Grid support

Layered on CSS Grid support for browsers that support it (uses feature queries). Middleman's version of autoprefixer needed to be updated as the old version outputted -ms- prefixed grid by default. This has now been turned off in 2.8.0 by default as it breaks the layout in Edge 15 - IE10.
New layout setup has been tested in:

IE9
IE10
IE11
Edge 14
Edge 15
Edge 16 (full grid support)
Chrome
Firefox
Safari 5.1 (windows)
Safari 10.1.x (OSX)
Safari iOS

NOTE: There are a few smaller layout issues that have been noted that are currently broken in the live version and therefore still broken in this version. This will be raised as separate tickets.

Is gds-way based on the tech docs template? Should we update that instead?

@nickcolley yes and yes 👍

@philandstuff / @nickcolley happy to do that too, whatever is required to move forwards. Where's the tech docs template?

@nickcolley / @pgchamberlin / @philandstuff This PR is now closed as a PR has now been raised on the tech docs repo


AGIC keeps saying backend pool is unhealthy even if pods are up and running

Describe the bug
AKS went down and after performing some node replace operations, the nodes\\pods came up fine by AGS is still reporting backend pool errors and not forwarding any requests to backend. Appgateway and AKS are within same vNET.
To Reproduce
AGIC backend health reporting errors

Pod is showing 200 for the probe url

probe setup:

Nothing changed from AKS or AppGateway side.. AKS nodes went down and came back up after some time but backend pool keep showing as unhealthy..
Ingress logs:

@akshaysngupta
this is a prod issue.. any quick response is appreciated.
Ingress Controller details

Output of kubectl describe pod <ingress controller> . The  pod name can be obtained by running helm list.
Output of `kubectl logs .
Any Azure support tickets associated with this issue.
120082524000376
120082424006138
120082424004967
.
--

Hi @nreddipalle , would you be able to share with us a sanitized version of your Ingress(yaml content)?

@3quanfeng how can I retrieve it?

kubectl get ingress -n your_namespace -o yaml
Is the issue consistent?

Yes. Currently it still exists and no communication is going on between AG and AKS.. backend health keeps showing as unhealthy even when I am able to browse fine from one of the pod internally.
`bash-5.0$ curl newsite.senseilabs.com/manifest.json

522 Origin Connection Time-out

522 Origin Connection Time-out
cloudflare-nginx

bash-5.0$ curl <IP_ADDRESS>:85/manifest.json
{"build-date":"2020-08-18T03:49:52.4376324Z","vcs-sha":"88d101138e6e9cc859cb8018c0e8993a6d3f801a","vcs-tag":"(no branch)","previous-vcs-sha":null}bash-5.0$`

here is the ingress yaml:
apiVersion: v1
items:
- apiVersion: extensions/v1beta1
  kind: Ingress
  metadata:
    annotations:
      appgw.ingress.kubernetes.io/appgw-ssl-certificate: senseilabsappservcert
      appgw.ingress.kubernetes.io/connection-draining: "true"
      appgw.ingress.kubernetes.io/connection-draining-timeout: "300"
      appgw.ingress.kubernetes.io/cookie-based-affinity: "true"
      appgw.ingress.kubernetes.io/request-timeout: "300"
      appgw.ingress.kubernetes.io/ssl-redirect: "true"
      kubectl.kubernetes.io/last-applied-configuration: |
        {"apiVersion":"networking.k8s.io/v1beta1","kind":"Ingress","metadata":{"annotations":{"appgw.ingress.kubernetes.io/appgw-ssl-certificate":"appservcert","appgw.ingress.kubernetes.io/connection-draining":"true","appgw.ingress.kubernetes.io/connection-draining-timeout":"300","appgw.ingress.kubernetes.io/cookie-based-affinity":"true","appgw.ingress.kubernetes.io/request-timeout":"300","appgw.ingress.kubernetes.io/ssl-redirect":"true","kubernetes.io/ingress.class":"azure/application-gateway"},"labels":{"app.kubernetes.io/instance":"newsite-prod","app.kubernetes.io/managed-by":"Tiller","app.kubernetes.io/name":"sensei-newsite","helm.sh/chart":"20200702-13137"},"name":"sensei-newsite","namespace":"newsite"},"spec":{"rules":[{"host":"newsite.senseilabs.com","http":{"paths":[{"backend":{"serviceName":"sensei-newsite","servicePort":85},"path":"/"},{"backend":{"serviceName":"sensei-newsite-conductor","servicePort":85},"path":"/conductor/*"},{"backend":{"serviceName":"sensei-newsite-conductor","servicePort":85},"path":"/api/conductor/*"},{"backend":{"serviceName":"sensei-newsite-academy","servicePort":85},"path":"/academy/*"},{"backend":{"serviceName":"sensei-newsite-academy","servicePort":85},"path":"/api/academy/*"}]}}]}}
      kubernetes.io/ingress.class: azure/application-gateway
    creationTimestamp: "2020-06-04T21:18:09Z"
    generation: 11
    labels:
      app.kubernetes.io/instance: newsite-prod
      app.kubernetes.io/managed-by: Tiller
      app.kubernetes.io/name: sensei-newsite
      helm.sh/chart: senseios-20200817-22843
    name: sensei-newsite
    namespace: newsite
    resourceVersion: "15224933"
    selfLink: /apis/extensions/v1beta1/namespaces/newsite/ingresses/sensei-newsite
    uid: 3a627ed3-543a-42e0-b913-136f2a605b7e
  spec:
    rules:
    - host: newsite.senseilabs.com
      http:
        paths:
        - backend:
            serviceName: sensei-newsite
            servicePort: 85
          path: /
  status:
    loadBalancer:
      ingress:
      - ip:
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

FYI.. this was working perfectly fine for the past couple of months... today due to a node issue AKS went down and once it came back up fine, AG still showing backend as unhealthy and not serving traffic..

Thanks, could you please help share the sanitized version if your ingress?
you can find all the ingress you defined within your namespace by running:
kubectl get ingress -n your_namespace
one more thing is since you replaced your AKS nodes, do you have any node affinity or node selector defined in your pod yaml or deployment yaml? are all of your service pods running fine(check by kubectl get pods -n your_namespace) after your replace aks nodes?

Our node selector is mainly for OS which is windows and spot instances. Yes all the service pods are running fine.. we have a failover to switch to ngnix and some sites that switched to ngnix are loading fine.. but some sites we left on AGIC for further troubleshooting and still not up yet..

Hi @nreddipalle , since new nodes added, could you try to update the annotation into "false"?
appgw.ingress.kubernetes.io/cookie-based-affinity: "true"
You can enable the affinity cookie later once the probe works

No difference. still same errors.

any update on this??

@nreddipalle looks like something broken in network connectivity b/w AppGW and Pod.
As a test, can you see if you are able to reach your Pods from the outside cluster, maybe using a VM ?

Thanks @akshaysngupta. YES. It looks like some network connectivity issue between App GW and Pod. We are able to fallback to use ngnix controller meanwhile... We tried tel-netting from a VM which is in same subnet and unable to telnet to pod port... so something weird going on between node-pod connectivity.. by doing a network trace, AG is sending requests to node but node is not responding back.... working with microsoft support for further troubleshooting.

This is confirmed to be network subnet-subnet communication issue. Before closing of this issue, I am noticing few errors which I would like to understand whether to ignore or not.
Seeing the below warning in ingress pod logs
1 redirects.go:44] Created redirection configuration sslr-fl-deca3d57d408a18bc8a79cd269957987 for ([newsite.senseilabs.com    ],443); not yet linked to a routing rule
App Gateway Listeners Tab:

The site(s) are loading fine.. Does the listener(s) suppose to configure as multisite instead of basic site??

@nreddipalle

The log line is just for information purpose. I think we can improve the logging in that area.
The second one is known issue with portal. We have a new feature rolling out for HTTP Listeners property in AppGW which we have started using in AGIC. Portal changes are going to arrive soon.

Thanks @akshaysngupta .


{% nevercache %} template tags are corrupt when both compression and caching are used

When both Mezzanine's mezzanine.core.middleware.UpdateCacheMiddleware /     mezzanine.core.middleware.FetchFromCacheMiddleware and Djangos own django.middleware.gzip.GZipMiddleware are enabled and DEBUG = False parts of a template can become corrupt and unreadable.
This is mostly apparent in templates using the {% nevercache %} template tag but I have also had times when an entire template has become corrupt.
Minimal working example: https://github.com/petedermott/mezzanine-cache-compression-bug

I think the previous comment contains a reasonable work around for those that require compression and caching middleware.


geom_bar() not changing fill color like it's supposed to

I'm trying to follow the demo here:  http://blog.yhat.com/posts/aggregating-and-plotting-time-series-in-python.html  and am unable to reproduce the figure

mine looks like this:

I'm using Win 8 with Python 2.7, the latest ggplot master from github (0.6.6 I think, but pip is telling me it's 0.6.5), pandas 0.16.2, numpy 1.8.1, and matplotlib 1.4.3.  I think I've correctly reproduced the code from the demo:
import numpy as np
import pandas as pd
import matplotlib.pylab as plt
from ggplot import *
def floor_decade(date_value):
"Takes a date. Returns the decade."
return (date_value.year // 10) * 10
meat2 = meat.dropna(thresh=800, axis=1) # drop columns that have fewer than 800 observations
ts = meat2.set_index(['date'])
by_decade = ts.groupby(floor_decade).sum()
by_decade.index.name = 'year'
by_decade = by_decade.reset_index()
p1 = ggplot(by_decade, aes('year', weight='beef')) +
geom_bar() +
scale_y_continuous(labels='comma') +
ggtitle('Head of Cattle Slaughtered by Decade')
p1.draw()
plt.show()
by_decade_long = pd.melt(by_decade, id_vars="year")
p2 = ggplot(aes(x='year', weight='value', colour='variable'), data=by_decade_long) +
geom_bar() +
ggtitle("Meat Production by Decade")
p2.draw()
plt.show()

I had the same problem, but it seems to work when using fill instead of colour:
p2 = ggplot(aes(x='year', weight='value', fill='variable'), data=by_decade_long) + \
    geom_bar() + \
    ggtitle("Meat Production by Decade")

@j-bennet is correct. color is the outline, fill is the meat of the bar chart


Helpful UI Tweaks and Very Minor Fixes

Final Product

Fixes:

fixed nullreferencexception when checking compression type for data textures
fixed a typo at the top of the ui => "video memeory" -> "video memory" (idk if MEMEory was intentional but there it is ;)

Feature Additions:

added an option to view materials using a specific texture

added a link to the texture compression documentation when clicking on compression type

added a message informing the user if a texture is used in a material swap and/or if it is not compressable (adds an info icon with subtext)

added confirm dialog to compresson change

added a progress bar to the calculation function - noticed that on lower end systems with large models, unity would hitch for a while, making some think unity had crashed

UI Changes:

changed some widths and heights of the gui
changed some spacing in messages for easier reading on smaller monitors
moved around some scroll views to make large amounts of information easier to navigate for the end user
moved the vram size text to the left of its texture object for easier readability (from feedback)

Those are beautiful UX improvements. Chefs kiss!


Add column by fetching URL redirection destination

A common use case on my end is to update an old URI or URL and while it's possible to do so with the Jython extension it would be very nice to have it as accessible through core. Example task: http://libris.kb.se/resource/auth/158606 -> https://id.kb.se/term/sao/R%C3%B6kstenen
Proposed solution
Add a transform method for "Add column by fetching URL redirection destination" which would behave similarly to the existing "Add column by fetching URL" but utilize HTTP HEAD requests and only return the final URL.
Alternatives considered
Three solutions currently being used: 1. fetching the content and parsing it for potential destination URLs 2. Fetching it with Jython 3. Scripting the fetching outside of OpenRefine
Alternatives for moving away from the above: implementing this but as an extension.

Working on this

I am not sure about introducing a dedicated operation for this: it could rather be an option in the existing dialogue for the URL fetching operation. Or a grel function.

Got it , going for an option in the existing dialogue for the url

It might be worth considering extending this to support all header fields, not just Location: so that users can access any of them that they find interesting.

Any progress on this? I really need this to be able to follow redirects.


kubectl update pods --patch doesn't work

I followed these intructions to update a pod,
$ kubectl create -f examples/limitrange/valid-pod
$ kubectl update pods valid-pod --patch='{ "apiVersion": "v1beta3", "spec": { "containers": [{ "resources": { "limits": { "cpu": 0.5 }}}]}}'

And the result I got was:
Error from server: Pod "valid-pod" is invalid: [spec.containers[0].name: required value, spec.containers[0].image: required value, spec: invalid value '{Volumes:[{Name:default-token-0xcta VolumeSource:{HostPath:<nil> EmptyDir:<nil> GCEPersistentDisk:<nil> AWSElasticBlockStore:<nil> GitRepo:<nil> Secret:<*>(0xc2109667f0){SecretName:default-token-0xcta} NFS:<nil> ISCSI:<nil> Glusterfs:<nil> PersistentVolumeClaimVolumeSource:<nil>}}] Containers:[{Name: Image: Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:map[cpu:500m] Requests:<nil>} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc20b298cc0){Capabilities:<*>(0xc20e5646f0){Add:<nil> Drop:<nil>} Privileged:<*>(0xc21096679c)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> ServiceAccount:default Host:kubernetes-minion-91q0 HostNetwork:false}': may not update fields other than container.image]

Respecting this error message, I tried to patch the container.image, but I got the same error.
The v1beta1 version of the command listed in the intructions didn't work either, it got
Error: json: cannot unmarshal array into Go value of type v1beta1.ContainerManifest

I think that's because the v1beta1 patch in the command does not conform to the schema.
#6855 #8087
@bgrant0607 @nikhiljindal

Currently only image is allowed to be update.

Those instructions were written speculatively, assuming that we would eventually permit cpu to be updated, but we still don't. The example should be converted to image.
And I think you need kind: Pod in the patch json.
This is where --dry-run would be useful, to dump the patched json.

Thanks. Same error message when I tried to patch the image:
$ kubectl update pods www --patch='{ "apiVersion": "v1beta3", "kind": "Pod", "spec": { "containers": [{ "iamge": "redis" }]}}'

Error from server: Pod "www" is invalid: [spec.containers[0].name: required value, spec.containers[0].image: required value, spec: invalid value '{Volumes:[{Name:default-token-ls6k1 VolumeSource:{HostPath:<nil> EmptyDir:<nil> GCEPersistentDisk:<nil> AWSElasticBlockStore:<nil> GitRepo:<nil> Secret:<*>(0xc208901a20){SecretName:default-token-ls6k1} NFS:<nil> ISCSI:<nil> Glusterfs:<nil> PersistentVolumeClaimVolumeSource:<nil>}}] Containers:[{Name: Image: Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:<nil> Requests:<nil>} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc20820f240){Capabilities:<*>(0xc208a75ce0){Add:<nil> Drop:<nil>} Privileged:<*>(0xc208901a70)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> ServiceAccount:default Host:kubernetes-minion-sjb0 HostNetwork:false}': may not update fields other than container.image]

kubectl update does not support --dry-run, I tried change --v, but that does not output the patched json.
If there is no quick answer to this issue, I will visit it again after I have updated other docs to v1beta3.

you have a typo above: s/iamge/image

@dchen1107 Sorry about the copy/paste error. After fixing the typo I got a similar error message.
Error from server: Pod "www" is invalid: [spec.containers[0].name: required value, spec: invalid value '{Volumes:[{Name:default-token-ls6k1 VolumeSource:{HostPath:<nil> EmptyDir:<nil> GCEPersistentDisk:<nil> AWSElasticBlockStore:<nil> GitRepo:<nil> Secret:<*>(0xc20874fe10){SecretName:default-token-ls6k1} NFS:<nil> ISCSI:<nil> Glusterfs:<nil> PersistentVolumeClaimVolumeSource:<nil>}}] Containers:[{Name: Image:redis Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:<nil> Requests:<nil>} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc20911e500){Capabilities:<*>(0xc208cfcf60){Add:<nil> Drop:<nil>} Privileged:<*>(0xc20874fde5)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> ServiceAccount:default Host:kubernetes-minion-sjb0 HostNetwork:false}': may not update fields other than container.image]

It looks like the kubctl is not doing a patch, but rather make a new object and only fill in the fields that are supplied in the patch, like what @nikhiljindal pointed out in #6855.

Just for the record, kubectl update --patch works for nodes, i.e.,
kubectl update nodes $NODE_NAME --patch='{"apiVersion": "v1beta3", "unschedulable": true}'

I will take a look.

The message says the container name is required, which is accurate. Have you tried to provide one?

Tried two patches with container's name specified, still no luck,
1.
$ kubectl update --validate pods www --patch='{ "apiVersion": "v1beta3", "kind": "Pod", "spec": { "containers": [{ "name": "www", "image": "redis" }]}}'

Error from server: Pod "www" is invalid: spec: invalid value '{Volumes:[{Name:default-token-9uw0i VolumeSource:{HostPath:<nil> EmptyDir:<nil> GCEPersistentDisk:<nil> AWSElasticBlockStore:<nil> GitRepo:<nil> Secret:<*>(0xc20e10d350){SecretName:default-token-9uw0i} NFS:<nil> ISCSI:<nil> Glusterfs:<nil> PersistentVolumeClaimVolumeSource:<nil>}}] Containers:[{Name:www Image:redis Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:<nil> Requests:<nil>} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc20a4fd080){Capabilities:<*>(0xc20c17dcb0){Add:<nil> Drop:<nil>} Privileged:<*>(0xc20e10d325)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> ActiveDeadlineSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> ServiceAccount:default Host:kubernetes-minion-qbwc HostNetwork:false}': may not update fields other than container.image

$ kubectl update --validate pods www --patch='{ "apiVersion": "v1beta3", "kind": "Pod", "spec": { "containers[0].name": "www", "containers[0].iamge": "redis"}}'

www

The response seems correct, but the image is still nginx.

This is same discussion as https://github.com/GoogleCloudPlatform/kubernetes/issues/7884.
'www' is the pod name and not the container name. Container name in examples/limitrange/valid-pod.json is "kubernetes-serve-hostname"

Thanks @nikhiljindal. I did use the wrong container name. But I got the same error after I update the container's name. For the record, these are the final commands and responses:
$ kubectl update --validate pods www --patch='{ "apiVersion": "v1beta3", "kind": "Pod", "spec": { "containers": [{ "name": "nginx", "image": "redis" }]}}'

Error from server: Pod "www" is invalid: spec: invalid value '{Volumes:[{Name:default-token-9uw0i VolumeSource:{HostPath:<nil> EmptyDir:<nil> GCEPersistentDisk:<nil> AWSElasticBlockStore:<nil> GitRepo:<nil> Secret:<*>(0xc2100c06e0){SecretName:default-token-9uw0i} NFS:<nil> ISCSI:<nil> Glusterfs:<nil> PersistentVolumeClaimVolumeSource:<nil>}}] Containers:[{Name:nginx Image:redis Command:<nil> Args:<nil> WorkingDir: Ports:<nil> Env:<nil> Resources:{Limits:<nil> Requests:<nil>} VolumeMounts:<nil> LivenessProbe:<nil> ReadinessProbe:<nil> Lifecycle:<nil> TerminationMessagePath:/dev/termination-log ImagePullPolicy:IfNotPresent SecurityContext:<*>(0xc2124350a0){Capabilities:<*>(0xc212dfa030){Add:<nil> Drop:<nil>} Privileged:<*>(0xc2100c0675)false SELinuxOptions:<nil> RunAsUser:<nil>}}] RestartPolicy:Always TerminationGracePeriodSeconds:<nil> ActiveDeadlineSeconds:<nil> DNSPolicy:ClusterFirst NodeSelector:<nil> ServiceAccount:default Host:kubernetes-minion-qbwc HostNetwork:false}': may not update fields other than container.image

And I think @nikhiljindal may be right,  it has something todo with the patch behaviors",  I will dig more tomorrow.

The merge function is here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubectl/cmd/util/helpers.go#L285
Now that we support patch in the server, this should really just be sending one of the flavors of patches without decoding/re-encoding.
@smarterclayton Do you mind if we disable update --patch for now?

Nope.
----- Original Message -----

The merge function is here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubectl/cmd/util/helpers.go#L285
Now that we support patch in the server, this should really just be sending
one of the flavors of patches without decoding/re-encoding.
@smarterclayton Do you mind if we disable update --patch for now?

Reply to this email directly or view it on GitHub:
https://github.com/GoogleCloudPlatform/kubernetes/issues/8449#issuecomment-103905111

Ok, great. Let's just make --patch not visible for now, and leave an issue open to fix it later.

I had been busy with our merge freeze issue since yesterday. On this issue now.

@jlowdermilk Could you please take a look at this?

Sure, I can take a look.

@caesarxuchao thanks for that link, very helpful. Turns out that kubectl update --patch is using the default json mergepatch, instead of strategic-merge-patch, which has the behavior we want. Assuming the implementation in pkg/util/strategicpatch works as advertised, this should be pretty easy to fix.

We have PATCH in the API. We should use that eventually. I was thinking we'd rip out this flag for now, instead of fixing it.

I have the fix with strategicmerge mostly working, but I can also just disable it. Depends on whether we want to have kubect update --patch for v1. #8983 just turns it off if we want quick fix.

So how do I add nodespec.unschedulable = true? Before I did:
kubectl update nodes $node --patch='{"apiVersion": "v1beta3", "spec": {"unschedulable": true}}'
Now I tried:
# echo '{
    "apiVersion": "v1",
    "kind": "Node",
    "metadata": {
        "name": "<IP_ADDRESS>",
        "uid": "ab97e1a9-13a0-11e5-b8c6-5254000ef5e9"
    },
    "spec": {
        "externalID": "<IP_ADDRESS>"
    }
}' | kubectl update -f -
Error from server: minion "<IP_ADDRESS>" cannot be updated: the resource was updated to 44058

This is fixed.


import bootstrap css

@nchanged I'm not sure what i'm missing i've done this time and time before but i'm at wits end.
In electron i'm just trying to use the css from bootstrap.
I've tried both the distributed scss (with proper plugin of course) and css and still keep getting the same result.

its coming from this...

and my two bundle configurations
  // bundle the electron main code
  const mainBundle = fuse
    .bundle("main")
    .target("server")
    .instructions("> [main/main.ts]")
  // inject in some configuration
  // and watch unless we're bundling for production
  if (!isProduction) {
    mainBundle.watch()
  }

  // bundle the electron renderer code
  const rendererBundle = fuse
    .bundle("renderer")
    .target('electron')
    .instructions("> [renderer/main.tsx] + fuse-box-css")
    .plugin(
      CSSPlugin(),
      CopyPlugin({ useDefault: false, files: ASSETS, dest: "assets", resolve: "assets/" }))

Edit: One thing i forgot to mention is if i change the arithmetic to include all, the bootstrap works but then electron doesnt load proper. If you try to use ipc or any other electron api it crashes out and says that electron failed to install correctly

Try adding plugins to FuseBox.init
And secondly you can't combine the CSSplugin and the CopyPlugin use either or.

no change...

Here is the repo. It uses mongodb by the way.
https://github.com/Kaffiend/fusebox-electron-react-typescript-mongo

That's what i originally had, still same result.

@Kaffiend remove all the opts from the CSSPlugin, it will be removed soon.

Tried that as well. Same result. I am clearing the .fusebox directory every
test too.
On Sun, Sep 23, 2018, 12:44 PM nchanged<EMAIL_ADDRESS>wrote:

@Kaffiend https://github.com/Kaffiend remove all the opts from the
CSSPlugin, it will be removed soon.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/fuse-box/fuse-box/issues/1388#issuecomment-423829881,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AHdrNSVqr1SMTUsSCjNNN-mc49qhiZ83ks5ud7pjgaJpZM4W1FLS
.

@Kaffiend I launched it, it can't find index.html
Some instructions on how to repro the issue?

@nchanged Is the index.html in the out dir? i just cloned a fresh one and it started fine with a repro

I have the same issue. I tried a minimal project, the index.ts is also empty. Installed bootstrap via NPM:
const { FuseBox, CSSPlugin, CSSResourcePlugin } = require("fuse-box");
const fuse = FuseBox.init({
  homeDir: "src",
  target: "browser@es6",
  output: "dist/$name.js",
  plugins: [
      [
          CSSResourcePlugin({
              dist: 'dist/resources',
              resolve: f => `dist/resources/${f}`
          }),
          CSSPlugin()
      ]
  ]
});

fuse
  .bundle("app")
  .instructions(" > index.ts")
fuse.run();

this is the output:
--- FuseBox 3.5.0 ---
  → Typescript config file:  \src\tsconfig.json
  → Typescript script target: ES6

--------------------------
Bundle "app"

    index.js
└──  (1 files,  287 Bytes) default
size: 287 Bytes in 120ms

@Kaffiend due to the limit amount of time at hand, I would like just to clone and see the problem. Please, prepare the repository so I won't need to fiddle around about the launch

closing it due to inactivity


Cannot GET /

Hi All,
Was having some issues installing codebox (hash didn't match, some issues with Ace not having the proper files, etc..) that I was eventually able to resolve.
However, now Codebox runs successfully, but I can not connect.
I am running it as root (this is a dev machine for random things) as below:

~/workspace# codebox run ./workspace
[log][web] disable auth for /static
[log][project] project is ready
[log][settings] Settings load for 032AD769
[log][rpc] register service /users
[log][rpc] add method list to /users
[log][rpc] register service /box
[log][rpc] add method changes to /box
[log][web] disable auth for /rpc/box/changes
[log][rpc] add method ping to /box
[log][web] disable auth for /rpc/box/ping
[log][rpc] add method status to /box
[log][web] disable auth for /rpc/box/status
[log][rpc] register service shells
[log][rpc] add method destroy to shells
[log][rpc] add method list to shells
[log][rpc] add method resize to shells
[log][rpc] add method status to shells
[log][rpc] register service debug
[log][rpc] add method backtrace to debug
[log][rpc] add method breakpoint_add to debug
[log][rpc] add method breakpoint_clear to debug
[log][rpc] add method breakpoints to debug
[log][rpc] add method close to debug
[log][rpc] add method cont to debug
[log][rpc] add method eval to debug
[log][rpc] add method init to debug
[log][rpc] add method locals to debug
[log][rpc] add method next to debug
[log][rpc] add method restart to debug
[log][rpc] add method start to debug
[log][rpc] add method stop to debug
[log][rpc] register service search
[log][rpc] add method code to search
[log][rpc] add method files to search
[log][rpc] register service deploy
[log][rpc] add method run to deploy
[log][rpc] add method solutions to deploy
[log][rpc] register service proc
[log][rpc] add method http to proc
[log][rpc] register service project
[log][rpc] add method detect to project
[log][rpc] add method supported to project
[log][rpc] add method useSample to project
[log][rpc] register service /run
[log][rpc] add method file to /run
[log][rpc] add method list to /run
[log][rpc] add method ports to /run
[log][rpc] add method project to /run
[log][rpc] register service /codecomplete
[log][rpc] add method get to /codecomplete
[log][reporting] events reporting with timeout of 180000 ms
[log][addons] Adding default addon cb.debug
[log][addons] Adding default addon cb.deploy
[log][addons] Adding default addon cb.files.editor
[log][addons] Adding default addon cb.files.image
[log][addons] Adding default addon cb.git
[log][addons] Adding default addon cb.help
[log][addons] Adding default addon cb.offline
[log][addons] Adding default addon cb.panel.files
[log][addons] Adding default addon cb.panel.outline
[log][addons] Adding default addon cb.project
[log][addons] Adding default addon cb.settings
[log][addons] Adding default addon cb.terminal
[log][addons] Adding default addon cb.theme.dark
[log][addons] start addon /root/.codebox/addons/cb.git
[log][rpc] register service git
[log][rpc] add method branch_create to git
[log][rpc] add method branch_delete to git
[log][rpc] add method branches to git
[log][rpc] add method checkout to git
[log][rpc] add method clone to git
[log][rpc] add method commit to git
[log][rpc] add method commits to git
[log][rpc] add method commits_pending to git
[log][rpc] add method diff to git
[log][rpc] add method init to git
[log][rpc] add method pull to git
[log][rpc] add method push to git
[log][rpc] add method status to git
[log][rpc] add method sync to git
[log][addons] Addons are ready
[log][web] disable auth for /manifest.appcache
[log][rpc] register service /auth
[log][rpc] add method join to /auth
[log][web] disable auth for /rpc/auth/join
[log][rpc] add method settings to /auth
[log][web] disable auth for /rpc/auth/settings
[log][rpc] register service /addons
[log][rpc] add method install to /addons
[log][rpc] add method list to /addons
[log][rpc] add method registry to /addons
[log][rpc] add method uninstall to /addons
[log][watch] Starting Watch

After this, I don't get anything in the console. When visiting the site VIA HTTP or doing a curl I get: "Cannot GET /"
npm -v
1.4.3
node -v
v0.10.26
Sorry if it's something totally obvious. Googling tells me it is a node thing, but I'd assume others would be having problems?
Thanks!

I think grunt was not the reason, probably it was this: https://github.com/CodeboxIDE/codebox/issues/434.


Request.cookiejar missing on 0.7.3

This script works well on 0.6.4: https://gist.github.com/1308823
But it raises the following error when I use 0.7.3, :
  File "gistfile1.py", line 15, in
  opener = urllib2.build_opener(urllib2.HTTPCookieProcessor(response.request.cookiejar))
 AttributeError: 'Request' object has no attribute 'cookiejar'

I guess the API was changed but the documentation wasn't.

Correct — a blog post and documentation update is forthcoming. CookieJars are being deprecated throughout for simpler cookie dicts.

Alright, but will it be possible to access the cookiejar object even if it is protected?
As you can see in my app, there are some scenarios that'd be interesting if I have access to the cookiejar.

Unfortunately, no. I'm moving completely off of urllib2, which is needed for cookiejars. I might try to make a helper function available for converting the header to a cookiejar for you though.

Oh, do not worry about that. I asked that just for convenience. I'll open a pull request this change bother me a lot ;)


Suppressing courtesy clef/key changes at ends of systems

In this example music:

I would like to suppress the courtesy time signature change at the end of the system after the double barline.
Should there be an attribute created for barline/measure that serves as a print suggestion to not print any courtesy clef/time/key change?  Should this be a style control in the MEI header? or should this be a external option provided to the rendering software?
This is a the end of a musical section (notice the terminal longs in that measure) which ends with a double barline.  The next measure is the start of a new section, so it is not necessary to warn the performer that a mensuration change is coming, since they are warned of the possibility by the double barline, and they have time to look ahead while holding the long note.
Should the sections of the music be encoded in
, and could that encoding imply to not add a courtesy time signature change?
These sections are similar to movements, but less so.  They are more like <subsection> rather than
.  Notice that the bar numbers do not reset to 1, for example.  Ideally these sections should end at a system break, as it does by here accidentally.

I would structure it like

Different movements should go into different <mdiv> elements.
Didn't we had a discussion about courtesy time signatures before somewhere?

Didn't we had a discussion about courtesy time signatures before somewhere?

I probably asked the same question a few years ago...

This is what @meter.showchange is intended to do; that is, display the old time signature when a new one is provided.  Unfortunately, the description of this attribute --
Determines whether a new meter signature should be displayed when the meter signature changes.
was garbled somewhere along the way.  It should read more like that of @sig.showchange; that is,
Determines whether the old time signature should be displayed at a change of time signature.

In this case I want to force a display of the meter at the start of the next section even if it is the same as the previous section, so @meter.showchange would not work in this case, since the meter could be the same across sections (but maybe it would need to be @mensur.showchange here?)
Notice the redundant clefs, which I need to work on removing:

In this case I want to suppress them (which I can easily do by not adding them to the data).  But I don't see a @clef.showchange in the staffDef attribute list:
http://music-encoding.org/guidelines/v3/elements/staffdef.html

I've always assumed, perhaps incorrectly, that a meter signature or indication of mensuration, would be displayed whenever it was encoded, even if it were the same as the previous one.

Right again, there's no @clef.showchange, but doesn't the same rule apply as to item 1?  That is, the act of encoding a clef means you want it displayed.  If you don't want to display it, don't include it.  :grinning:

Closing because it's marked "Won't Fix."


perf: decrease memory usage of RawInterface.report_idle by 224 bytes

Closes https://github.com/dlkj/usbd-human-interface-device/issues/77.
Currently heapless::FnvIndexMap<u8, u8, 32> is used to store idle times for reports, which takes 260B (out of 460B for whole RawInterface) to store at most 32 u8 values. This PR changes it to use option-block which basically is [u8; 32] with u32 bitmask of "used" slots, which takes 36B (RawInterface is now 236B). Report IDs should start from 0 and grow so the functionality with option-block should basically be equivalent to FnvIndexMap but take up less memory and be faster.
This should be sufficient for any real-world use case as I cannot imagine having more than 32 reports for a single interface (unless I misinterpret something in the HID specs). In the future it could be reduced to 8 reports (9B report_idle) as in most cases there are no more reports than that. It could e.g. be a generic parameter that defaults to 8. But the gains are smaller so I didn't implement it.
In my use case, with 3 HID interfaces this saves 672 bytes of RAM usage, while I also observed minor improvement in code size - usbd-human-interface-device takes 406 bytes less space.

I fixed rusfmt/clippy warnings and a bug - out of band index in tests due to REPORT_ID=0xAB (looks like option-block .get() doesn't do bounds checking, so I fixed usage in the code). Note: it looks like the tests don't check if get_idle reports the new value, otherwise they should fail for REPORT_ID=0xAB because it's >32.

Thanks for the PR. Will take a look at this when I have a spare moment.


Doesn't work for Cargo packages with both a library and binary crate

As stated in the title of this issue, winres fails to change the resource data of executables generated by Cargo when compiling a package that has both a library and binary crate (i.e. both a src/main.rs and src/lib.rs). No error happens whatsoever, and both the resource file and Cargo instructions output in the build script are correct, which makes this a pretty sneaky issue.
I've managed to trace the cause down to how Cargo works. Citing the documentation (emphasis mine):

The -l flag is only passed to the library target of the package, unless there is no library target, in which case it is passed to all targets. This is done because all other targets have an implicit dependency on the library target, and the given library to link should only be included once. This means that if a package has both a library and a binary target, the library has access to the symbols from the given lib, and the binary should access them through the library target's public API.

Because winres instructs the linker to link to the resource file via cargo:rustc-link-lib, the binary crate that generates the actual program is not linked against the resource file, and that essentially means that winres ends up doing nothing visible. I've confirmed that this happens when using the GNU toolchain, although for MSVC this is also done as well, so I'd expect MSVC builds to be affected too.
One obvious workaround would be getting rid of the library crate, but this is not necessarily a good practice (separating the application code from the API it uses is usually nice). Another workaround is to set up a workspace and separate the library and binary crates into different packages, but this seems like overkill to just get some metadata linked to a binary crate.
Can winres reliably link the resource file with the binary somehow, even if it shares package with a library crate? If not, can I workaround it in a better way than using workspaces? Thanks!

After some trying, I settled with rcedit and a custom PowerShell script that is invoked after cargo build, which is a better workaround for me than using workspaces. But I think that this issue is still relevant, and if it is not fixable by winres, I think this quirk should at least be documented.

winres is intended to be used by the cargo build script and therefor can only do what cargo allows. Please raise that issue with the cargo developers to allow the build script to manipulate individual targets and provide more control over the linker process (see https://github.com/rust-lang/cargo/issues/9554, but that's nightly),
or to allow more than a separate build script for each target.
Currently cargo only allows to supply some flags to the linker and this reliably only works for one target in the crate. If you have multiple artifacts the easiest workaround would be to create a crate for each of them.
I think that this is basically the same problem as with https://github.com/mxre/winres/issues/29

I did some testing and using [[bin]] nodes is simply unsupported as the build scripts output is not used to link these executables. There is nothing winres can do.
But having a crate with a [lib] node and using winres to embed resources into a .dll is supported. Just set crate-type = ["cdylib"] so the output of cargo will be a .dll and not a .rlib. Only .dll libraries can have resources.

From https://doc.rust-lang.org/cargo/reference/build-scripts.html#cargorustc-link-libkindname

The -l flag is only passed to the library target of the package, unless there is no library target, in which case it is passed to all targets. This is done because all other targets have an implicit dependency on the library target, and the given library to link should only be included once. This means that if a package has both a library and a binary target, the library has access to the symbols from the given lib, and the binary should access them through the library target's public API.

So if there is a library crate the build scripts parameter are only passed to the lib part. Since we generate a static library ourselves (one without symbols only prescribing a .rsrc section for the resulting binary) It gets optimized away in the linking step of the [[bin]] executable.
No way of fixing this because from the perspective of the cargo devs this is all intended.

It's sad to read that linking a DLL with a resources section does not work either, but I understand that this crate can't do anything about it. I guess I chose the best workaround for my situation then.
Anyway, what would you think about adding a small note in the crate documentation about this situation? I initially was clueless about why my Windows executables stopped having a nice icon, until I started digging and bisecting and traced it back to Cargo's design. I think such a note would save time from future crate users in my situation.

I too encountered this problem today and I'd really appreciate some warning notice being added to winres documentation. Anyways, the other thing I wanted to share is yet another workaround that worked for me and might also work for others. I added a single line to my build.rs and apparently it did the trick:
fn main() {
    let mut res = winres::WindowsResource::new();
    res.set_icon("resources/icon.ico");
    res.compile().expect("Cannot compile resource bundle.");
    println!("cargo:rustc-link-arg-bins=resource.lib"); // This line
}

What we are doing here is telling the linker to take into account one more file when linking: resource.lib. This file is produced by winres and it sits in a directory which is present in the search path, so linker doesn't have problems with finding it.


[753 ] Updated contributing.md file

title: Issue 753

Discord Username: @
What type of PR is this? (select all that apply)

[ ] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 🚧 Breaking Change
[ ] 🧑💻 Code Refactor
[x ] 📝 Documentation Update

Description
intended step 10 command in contributing.md file to align with other commands within same list as per issue TT: https://github.com/webdevcody/code-racer/issues/753
Related Tickets & Documents

Related Issue https://github.com/webdevcody/code-racer/issues/753
Closes https://github.com/webdevcody/code-racer/issues/753

QA Instructions, Screenshots, Recordings

UI accessibility concerns?

Added/updated tests?

[ ] 👍 yes
[x ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

[optional] Are there any post deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Found other commits with same changes. Closing PR.


When selecting device, it should zoom in the location automatically

Till now, its been very tiresome to view a single device.
When opening the app, it shows map in a zoomed out default position. When clicking on one of the device names - it should by default zoom in automatically to the exact location of the device.
Has this feature not been asked before?
Is this supposed to be requested on https://github.com/tananaev/traccar ?

It should be here:
https://github.com/tananaev/traccar-web


fix mod invite scope

As promised in #440  and #442

Hmm, I was planning on just merging this myself, but I made the Coveralls rating decrease. What should the betamax test for the modself scope look like? The user would have to have a pending moderator invite or contributor status to act upon.

These are much more difficult tests to write, but the approach should be the same as the test that already exists: https://github.com/praw-dev/praw/blob/master/tests/test_subreddit.py#L211
The key difference is that we need to replace the base login with the appropriate scope for pyapitestuser2, and likewise the appropriate scope necessary for pyapitestuser3. How does that sound?

Well I know what the test itself will be doing, I'm just not sure how to get the second user's praw session open. The pw authentication makes it really easy to switch between accounts, but I don't know how to get user3 authenticated without basically duplicating all of the oauth code and making a separate self.r for it.
I was wondering if you had any recommendations on how to switch accounts with oauth, or whether PRAW makes it easy to change all your tokens mid session. Is it as simple as hardcoding the separate client secrets and IDs instead of pulling them into r via praw.ini?

Yes it's as easy to change users with OAuth. You just need the appropriate refresh token and can use that with set_access_credentials if I recall correctly (on my phone).
We should only need to obtain 'other' user refresh tokens for a few scopes.

Well, after generating and promptly wasting countless OAuth keys, I finally got a working test, but I've decreased the coveralls score for decorators.py somehow...
I had to make an edit to the _modify_relationship within internal.py. When it was using scope=None, the oauth test couldn't add moderators. I suspect that the other relationship methods will have the same problem through oauth, but we can look at that later.
You'll notice that in my new test, I actually call self.test_get_access_information() to reset the user to PyAPITestUser2. I'm not sure if you frown on that kind of practice -- calling a test from within a test -- but it makes for a little bit less token-juggling if I can just use it as a login method.
Critiques?

Great work! I think there's a bit of unnecessary complication as my understanding is it should be easy to switch between users (and scopes too when necessary) by simply loading in the appropriate refresh token.
As far as the coveralls, small negative changes I wouldn't worry about. If you see a dramatic decrease that should be cause for concern.
I'm really liking what you're coming up with. I hope you're enjoying the work, and are growing a sense of ownership over some of PRAW. Thanks continuing to help make PRAW more awesome.

Should that print statement be there?

Woops.

I'm not sure why all of that is necessary [...] my understanding is it should be easy to switch between users by simply loading the appropriate refresh token

Gahhh, you're right. I had a lot of trouble getting these tests to work, and I thought that refresh tokens would only work if you were already logged in as the user they were made for. I made an OAuth app on User3's account and everything. Oauth is weird.
This does mean I can remove that test-within-a-test line, which is good.

Do you think we should continue writing tests for the specific scopes like this?

If the scope is extremely specific, then yes. "modself" and "modothers" are only for managing joins/leaves of mods/contributors, and you can't really test the leave method without first testing the join method. Some scopes definitely need to be broken up, like "subscribers" can have one test for subscriptions, and then another for multireddits. Some scopes don't really gain or lose.

I hope you're enjoying the work

Certainly, and thanks for the encouragement!


fix(dashboard): create new user

fixes: https://github.com/nhost/nhost/issues/1474

Could you please create a patch bump by running pnpm changeset in the root folder?


Model size assumes Fp16 data type

Issue
When analyzing a model MLAgility assumes that the model is using FP16 when printing the model size.
On src/mlagility/analysis/status.py  lines +115 to +116:
        # Converting number of parameters to MB assuming 2 bytes per parameter
        model_size = model_info.params * 2 / (1024 * 1024)

Possible solutions

Only show the size in MB once the model has been benchmarked (and a data type has been set)
Use the datatype of the original model and change the information shown if mlagility modifies the data type (e.g. converts to FP16).

@ramkrishna2910 @jeremyfowers


missing files count - tableview

Hiya. Thanks for making the plugin. I really appreciate it.
I am just wondering how can I see the total number of files included in the list? I have seen the tutorials/guides and they all have it. But I am not sure what did I do wrong as it did not show up. I suspect it is to do with the recent update and I am just wondering if there's any option which can let me see the total files?
Thanks!

The circled area is supposedly to have the total number of files, according to various youtube guides. Now they are gone.

You can limit the number of rows displayed on a page. And then at the top there will be a list of pages with the number of lines in it, if this number exceeds the limit of lines on the page

@Felharrim Thanks for the tip. I really appreciate it ^o^
I do use it as a workaround for now but it is perhaps not the most intuitive for long-term use/large scale database. I am just wondering if the creator would be interested in fixing it and bringing the feature back, as shown in the previous versions.

Will be fixed in the next version

thanks @mdelobelle


hey

requireStack: [ 'C:\Users\Litet\Desktop\PossumBot-master\bot.js' ] error is popping up

Can you make something which can give me the ownership of that server

@BeastGamerYT yes ofc.


Updates from rspec-dev (2022-01-26)

These are some updates, generated from rspec-dev's rake tasks.

Feel free to merge,
LoadError:
  cannot load such file -- net/smtp

I didn't get to fixing this for sub-builds.

@pirj I'll put back the skip for now, I'm looking for green builds on the core libraries on main and 3-10-maintenance to do some tidy up, patch releases and prep for a 3.11

It's fine, I believe https://github.com/rspec/rspec-rails/pull/2568 should fix it for builds with no RAILS_VERSION specified like those sub-builds.


Portfolio desktop version

Portfolio desktop version
In this branch, I added the media query to give the style to the desktop version

Added media query
Used Grid and Flexbox
Followed the Figma temple and guidelines for Desktop

Webhint is working on my local machine

Webhint is failing in GitHub Actions because of an external problem

Hello @franclobo, @AbdusSattar-70.
I kindly recommend you check the comments when I exposed WebHint is not working on GitHub actions. This is an issue affecting all the students. You can also check the GitHub actions logs to see that the problem is related to the WebHint installation process.
There are also some comments in the Slack channel about more students having the same issue.
Hope this comment is taken into account for future reviews.


AdcsAuthorityInformationAccess: Always makes a change #128, #138

Pull Request (PR) description
Removed the AllowRestartService parameter from being tested/compared.
Updated Get-CaAiaUriList to force a System.String[] to be returned regardless of single or multiple values.
This Pull Request (PR) fixes the following issues

Fixes #128
Fixes #138

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[x] Resource documentation added/updated in README.md in resource folder.
[x] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[x] Comment-based help added/updated.
[x] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

If you rebase this one I continue with this one. 🙂

I really messed up when trying to merge. I think it's all back to where it should be now.
What's going to be the optimal solution for this? The Get-CaAiaUriList should return a string or string[].

I will try to get back to this soon.


Remove TestDummyProg()

As a follow up to #23557 we shouldremove TestDummyProg(). Like @ti-mo mentioned in https://github.com/cilium/cilium/issues/20739#issuecomment-1331855419_ feature probing prog/attachtype combinations looses value if the new implementation uses bpf_link.
Instead of probing for a succeeding PROG_ATTACH we should just ask for forgiveness with the new logic in pkg/socketlb and bail out or flip flags in cases of failure.

cc @ti-mo

Proposal for this in https://github.com/cilium/cilium/pull/25355.


The file watcher should not run during APPSODY_PREP

Currently we launch the watcher async right after we launch the RUN command which in turn does APPSODY_PREP.
We should pull out APPSODY_PREP so it runs sync prior to any of this.  OR we should update the run commands logic to spin the func for watching after APPSODY_PREP runs,

@neeraj-laad can you think of any reason we would need the file watcher (and thus on-change actions) running during APPSODY_PREP?
Making the change to not run file watching during APPSODY_PREP start up is a simple matter.
BTW: There was also another issue where Henry Nash suggested running APPSODY_PREP prior every ON_CHANGE action, but I think the performance of that would be very bad.

@kewegner We do not need to run the watcher during the prep or install steps.


README.md: fix typo

Introduced in d1ed748fa45cea3f070698d9b50b45c1ecfd0267.

@FractalFir have you seen this too? https://github.com/FractalFir/rustc_codegen_clr/commit/d1ed748fa45cea3f070698d9b50b45c1ecfd0267#r142021693

I have seen it, but was a bit busy at the time, so I decided to add it to my TODO list.


Failed to copy, Operation not permitted

ADB push error
I cant push the sources,drivers,dism failed to copy Operation not permitted
What should i do to fix this problem?

i have this problem too


Could not resolve, missing default export errors in some packages

Hi, i got stuck when using this plugin to use packages with wasm files and vite.
Don't know if the issue is in this plugin or in the package i use.
Here is a repo to reproduce the issue: https://github.com/mima0815/vitewasm with the package: @swagger-api/apidom-parser-adapter-openapi-json-3-0
if i import this https://github.com/mima0815/vitewasm/blob/main/src/components/HelloWorld.vue#L3 and use it here: https://github.com/mima0815/vitewasm/blob/main/src/components/HelloWorld.vue#L10
i get the following errors when building or using the vitejs dev mode:
✘ [ERROR] Could not resolve "env"

    vite-plugin-wasm-namespace:/Users/mima0815/dev/mima0815/vitewasm/2/node_modules/@swagger-api/apidom-parser-adapter-json/wasm/tree-sitter-json.wasm:43:183:
      43 │ ..._base as __vite__wasmImport_0_1, memory as __vite__wasmImport_0_2, __indirect_function_table as __vite__wasmImport_0_3 } from "env";
         ╵                                                                                ~~~~~

  You can mark the path "env" as external to exclude it from the bundle, which will remove this
  error.

✘ [ERROR] Could not resolve "env"

    vite-plugin-wasm-namespace:/Users/mima0815/dev/mima0815/vitewasm/2/node_modules/web-tree-sitter/tree-sitter.wasm:43:579:
      43 │ ...se as __vite__wasmImport_0_10, memory as __vite__wasmImport_0_11, __indirect_function_table as __vite__wasmImport_0_12 } from "env";
         ╵                                                                                ~~~~~

  You can mark the path "env" as external to exclude it from the bundle, which will remove this
  error.

✘ [ERROR] Could not resolve "wasi_snapshot_preview1"

    vite-plugin-wasm-namespace:/Users/mima0815/dev/mima0815/vitewasm/2/node_modules/web-tree-sitter/tree-sitter.wasm:44:122:
      44 │ ...te as __vite__wasmImport_1_0, fd_close as __vite__wasmImport_1_1, fd_seek as __vite__wasmImport_1_2 } from "wasi_snapshot_preview1";
         ╵                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~

  You can mark the path "wasi_snapshot_preview1" as external to exclude it from the bundle, which
  will remove this error.

✘ [ERROR] Could not resolve "GOT.mem"

    vite-plugin-wasm-namespace:/Users/mima0815/dev/mima0815/vitewasm/2/node_modules/web-tree-sitter/tree-sitter.wasm:45:54:
      45 │ import { __heap_base as __vite__wasmImport_2_0 } from "GOT.mem";
         ╵                                                       ~~~~~~~~~

  You can mark the path "GOT.mem" as external to exclude it from the bundle, which will remove this
  error.

adding this to the vite.config.json, removes the errors:
  build: {
    rollupOptions:{
      external:['env','wasi_snapshot_preview1','GOT.mem']
    }
  },

but then it fails later with an missing default export:
"default" is not exported by "node_modules/web-tree-sitter/tree-sitter.wasm", imported by<EMAIL_ADDRESS>file: /Users/mima0815/dev/mima0815/vitewasm/2/node_modules/@swagger-api/apidom-parser-adapter-json/es/lexical-analysis/browser-patch.js:4:7
2: import { isString, isFunction } from 'ramda-adjunct';
3: // @ts-ignore
4: import treeSitterWasm from 'web-tree-sitter/tree-sitter.wasm';
          ^
5:
6: // patch fetch() to let emscripten load the WASM file
error during build:
RollupError: "default" is not exported by "node_modules/web-tree-sitter/tree-sitter.wasm", imported by<EMAIL_ADDRESS>    at error (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:2124:30)
    at Module.error (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:13463:16)
    at Module.traceVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:13884:29)
    at ModuleScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:12429:39)
    at TrackingScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:6965:38)
    at BlockScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:6965:38)
    at ReturnValueScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:6965:38)
    at ChildScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:6965:38)
    at TrackingScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:6965:38)
    at BlockScope.findVariable (file:///Users/mima0815/dev/mima0815/vitewasm/2/node_modules/rollup/dist/es/shared/node-entry.js:6965:38)
error Command failed with exit code 1.

The packages are in use and are able to be loaded e.g. here: https://editor-next.swagger.io/
I never worked with wasm dependencies before, could it be that those packages are not compatible with vite+this plugin? or do i need to configure Vite in some way?
Could be a similar issue like here: https://github.com/Menci/vite-plugin-wasm/issues/31

The WASM file you attempted to import tree-sitter-json.wasm is NOT an ESM WebAssembly file. It has an import named env but not a real package to import. Handling it with this plugin is like there's a JS file writing import env from "env";.
$ node --experimental-wasm-modules
Welcome to Node.js v18.11.0.
Type ".help" for more information.
> await<EMAIL_ADDRESS>(node:67004) ExperimentalWarning: Importing WebAssembly modules is an experimental feature. This feature could change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
Uncaught:
Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'env' imported from<EMAIL_ADDRESS>    at __node_internal_captureLargerStackTrace (node:internal/errors:484:5)
    at new NodeError (node:internal/errors:393:5)
    at packageResolve (node:internal/modules/esm/resolve:860:9)
    at moduleResolve (node:internal/modules/esm/resolve:909:20)
    at defaultResolve (node:internal/modules/esm/resolve:1124:11)
    at nextResolve (node:internal/modules/esm/loader:163:28)
    at ESMLoader.resolve (node:internal/modules/esm/loader:841:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:424:18) {
  code: 'ERR_MODULE_NOT_FOUND'
}


Fix url_redirect issue on net-glb module

https://github.com/GoogleCloudPlatform/cloud-foundation-fabric/issues/1202


Update format.yml

[中文版模板 / Chinese template]
🤔 This is a ...

[ ] New feature
[ ] Bug fix
[ ] Site / documentation update
[ ] Demo update
[ ] Component style update
[ ] TypeScript definition update
[ ] Bundle size optimization
[ ] Performance optimization
[ ] Refactoring
[ ] Code style optimization
[ ] Test Case
[ ] Branch merge
[ ] Other (about what?)

🔗 Related issue link

💡 Background and solution

📝 Changelog

Language
Changelog

🇺🇸 English

🇨🇳 Chinese

☑ Self Check before Merge
⚠ Please check all items below before review. ⚠

[ ] Doc is updated/provided or not needed
[ ] Demo is updated/provided or not needed
[ ] Changelog is provided or not needed

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@0802136). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master      #6   +/-   ##
========================================
  Coverage          ?   0.97%
========================================
  Files             ?     339
  Lines             ?   15977
  Branches          ?       0
========================================
  Hits              ?     156
  Misses            ?   15821
  Partials          ?       0

Continue to review full report at Codecov.

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


Add BurnMintERC677 in popular contracts section

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on adding a new address for a BurnMintERC677 contract to the list of supported contracts in the explore.ts file.
Detailed summary

Added "0xaF3202F6bAEbA50d37e0d4B0b870455EDF198D7c/BurnMintERC677" to the list of contracts in explore.ts.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

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

#5239  👈
#5238
main

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

Join @MananTank and the rest of your teammates on  Graphite


May occur not found, should dismiss this error type.

          May occur `not found`, should dismiss this error type.

Originally posted by @SSmallMonster in https://github.com/hwameistor/hwameistor/pull/762#discussion_r1161390887

TODO


Uniquify people (modifing is_data, and Person)

::identical(attr) and #identical return records matching all columns not removed because of RESERVED_ATTRIBUTES, and the constant from the specific class IGNORE_IDENTICAL.
-- If the instance record contains (non-ignored) columns (key) which contain (value) nil, they will have to match a nil in a persisted records for it to be returned.
--#identical will not return the instance itself.
--::identical(attr) will return the record the attributes of which were used as parameter, if it has been persisted.

::similar(attr) and #similar return records matching all columns not removed because of RESERVED_ATTRIBUTES, and the constant from the specific class IGNORE_SIMILAR.
-- If the instance record contains (non-ignored) columns (key) which contain (value) nil, these columns will also be ignored, as if they has been included in IGNORE_SIMILAR.
--#similar will not return the instance itself.
--::similar(attr) will return the record the attributes of which were used as parameter, if it has been persisted. This permits a new, non-persisted,  record to be used as a prototype for the attributes, requiring only those attributes which are of interest in a particular search.

Coverage increased (+0.06%) to 66.543% when pulling 61cfb419df53f65f0b51b32982a621c49faaf142 on uniquify_people into 7b8fedf222f2554418ccee1f18fc8e5eed850365 on development.


Add Node Env status bar.

[x] Add a status bar that shows the node environment as reported by the dashboard
[x] Hide the status bar if nothing is reported
[x] Do not show module errors if we are in production mode, just report what we can

Addresses #33

DUDE THATS SO SICK